Maybe helpful, just some input from one packager. To me, the patch is the way to go
Anke On Thu, Sep 6, 2012 at 12:48 PM, Rolf Eike Beer <[email protected]> wrote: > Am Mittwoch, 5. September 2012, 23:23:25 schrieb Sebastian Kügler: > > On Wednesday, September 05, 2012 16:07:30 Allen Winter wrote: > > > Hot fixes should be sent to kde-packagers as a patch, or even better > as a > > > commit number. > > > > > > Example: > > > > > > "Dear packagers, we found a bad bug in kde-foo that causes the > following > > > terrible things to happen. Please apply commit abc123 to your kde-foo > > > packages and distribute this new version to your users as soon as > > > possible." > > > > > > I don't think we want to respin tarballs for bugfixes. To my > > > recollection, > > > we never have. > > > > Right, tarballs are final. It would only introduce confusion ("which > version > > of the 4.9.1 tarball do you have?"), so we better avoid it. > > > > We can always increase the version number and release 4.9.2 tomorrow, > with > > just this one fix. Do we want to do that? > > I hope not. Many applications have a numbering scheme that follow the KDE > SC > version numbers in some way. So they would have to bump their version > numbers. > Which means we either need to create a new branch for them if they already > have post 4.9.1-changes in their KDE/4.9 branch or include their new > changes. > Which would mean we should add another stabilization phase or something. > > So, my vote is clearly release a 4.9.1a of exactly that one tarball. > > Eike > _______________________________________________ > release-team mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/release-team > >
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
