Radu Cristian Fotescu a écrit :
> I *do* understand the 'megafreeze' policy of all the distros who release
> twice a year, however, could you please explain me:
>
> 1. How is this "too many changes", as long as there is no new
> dependency, but a mere recompiling of an updated source package?
Quoting the developer: "Since 90% of the code is new any feedback will
be greatly appreciated."
This is what I call "too many changes".
> 2. Why can't this be pushed as an update, or possibly as a backport as a
> last resort? Note that this is in "universe", so Ubuntu does *not* need
> to support it.
After a release, only security or bugfix updates (Stable Release Update)
are allowed.
Nobody said it couldn't be backported: it just needs to be packaged and
uploaded for jaunty as soon as the repositories open, and then you'll be
able to request a backport (you don't even have to be a developer for that).
> 3. Why can't "per case" decisions be taken, knowing that there is so
> very unlikely to experience regressions with such a package, and it is
> *not* a "fundamental" package anyway?
Have you tested it on several configurations to say this?
Anyway, ask the Xubuntu Team Leader, motu-release and/or motu-sru if you
want a per-case decision on this.
Radu Cristian Fotescu a écrit :
> I *do* understand the 'megafreeze' policy of all the distros who release
> twice a year, however, could you please explain me:
>
> 1. How is this "too many changes", as long as there is no new
> dependency, but a mere recompiling of an updated source package?
Please read foo-projects. org/pipermail/ goodies- dev/2008- September/ 001734. html
http://
Quoting the developer: "Since 90% of the code is new any feedback will
be greatly appreciated."
This is what I call "too many changes".
> 2. Why can't this be pushed as an update, or possibly as a backport as a
> last resort? Note that this is in "universe", so Ubuntu does *not* need
> to support it.
After a release, only security or bugfix updates (Stable Release Update)
are allowed.
Nobody said it couldn't be backported: it just needs to be packaged and
uploaded for jaunty as soon as the repositories open, and then you'll be
able to request a backport (you don't even have to be a developer for that).
> 3. Why can't "per case" decisions be taken, knowing that there is so
> very unlikely to experience regressions with such a package, and it is
> *not* a "fundamental" package anyway?
Have you tested it on several configurations to say this?
Anyway, ask the Xubuntu Team Leader, motu-release and/or motu-sru if you
want a per-case decision on this.
-- /launchpad. net/~mrpouit
Lionel Le Folgoc - https:/
EEBA 555E 0CDE 92BB 3AF4 4AB3 45A0 357B 5179 5910