Pulseaudio version in Jessie

[Niels Thykier]

On 2014-09-15 15:02, Felipe Sateler wrote:
> Hi Niels, Release Team,
> 
> On Sat, Sep 13, 2014 at 7:13 AM, Niels Thykier <niels at thykier.net> wrote:
>> On 2014-09-05 06:32, Felipe Sateler wrote:
>>> [...]
>>
>>
>> Hi Felipe / Pulseaudio maintainers,
>>
>> I apologise for the tardiness on our part.  Thanks for bringing this
>> problem to our attention.
>>
>> If I understand you correctly then the consequence of the regression is
>> Debian loses support for the following bluethooth devices:
>>
>> [...]
> 
> I'm not sure what Health devices are. But HSP support also means most
> headphone+mic headsets.
> 

Ok, that is certainly worse than I presumed. Thanks for clarifying that.

>>
>>
>>> 1. Is such a plan (uploading the RC pre-freeze and the final release
>>> post-freeze) acceptable?
>>
>>
>> For me, such a plan /could/ be acceptable provided that:
>>
>>  * The new major version of pulseaudio is both API and ABI backwards
>>    compatible!
>>
>>    - A transition would be a deal-breaker for me at this point.
> 
> AFAICT, the ABI is maintained. I will check a bit more thoroughly and
> report back, but I think this requirement is met.
> 

Excellent, thanks. :)

>>
>>  * The current issues in the release candidates are not (new) RC bugs.
>>
>>    - Keep in mind that we may need to have pulseaudio reverted to the
>>      old version should such issues turn out to be worse than
>>      anticipated.
> 
> Of course. But we will not know the current issues in the release
> candidate until we have it.
> 

Certainly.  Thus, we should have the new version in Debian sooner rather
than later.

>>
>>  * You are aware that the Debian RT view of "necessary bug fixes" do
>>    not always coincide with upstreams view of "necessary bug fixes".
>>
>>    - During the freeze we will reviewing all changes and we reserve the
>>      right to question/reject any (part) of them.
> 
> How should I propose such changes? In order to make your work easier,
> what should I send to the release list each time I upload a package?
> 

Starting (late) October, you will need to file unblock bugs for every
change you want to have included in Jessie.  Such a bug should include a
debdiff showing the difference between testing and your desired version
(usually the one in sid).

>> [...]
>>
>>
>> Smaller changes are (often) easier to review and has a higher chance of
>> being accepted.
> 
> OK. As soon as the upstream release candidate is released I will
> upload it to experimental. At that moment I will ping you again in
> order to check you are still OK with following the above plan.
> 
> 

Gppd to hear - do you have an estimate on when the release candidate
will be ready?

> Thanks and keep up the good work
> 

Thanks and you too, :)

~Niels