Bug#617331: Pushing tzdata updates to stable in time
On Fri, 11 Mar 2011, Martin Zobel-Helas wrote:
> On Fri Mar 11, 2011 at 13:11:52 -0600, Gunnar Wolf wrote:
> > I was prodded by my Chilean friend, Germán Póo-Caamaño, to help find a
> > way to push the tzdata corrections needed for Chile's change of
> > timezone plans. Trying to do so, I found he already did everything
> > needed (#617331).
> > Chile was supposed to leave the Summer daylight savings period this
> > coming weekend, but it was pushed to April 2nd. The fixes have been
> > accepted to the package in Sid, but many users will undoubtely
> > appreciate it if it can be updated as well in stable-updates.
> > Sorry for reverberating here on list, but given the timeframe for this
> > bug to bite, I'd rather have it prominent and not hidden.
> the correct way would be to ask the release team for a release of tzdata
> on stable-updates (formerly known as volatile) and get it updated in the
> next point release as well.
I was wondering about this, actually. Right now, stable-proposed-updates
doubles as the security archive for non-free (see sun-java6). But IMO, we
_really_ would rather prefer not have people adding s-p-u to their systems
because we took too long to release (to stable or stable-updates) packages
that needed an expedited process, there is a good reason why we have s-u and
stable release checkpoints, undermining that is not to our best interest
tzdata is a good example of a main package that needs expedited release to
s-u. non-free security-related updates are another example.
Is there a special process for this? or should we just make the DDs aware of
the fact [by an email to d-d-a] that when one does a s-p-u upload which
likely needs expedited handling, they should be very clear about that fact
and email the stable release team ASAP?
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot