-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/31/10 9:40 AM, Jeff Spaleta wrote:
On Tue, Aug 31, 2010 at 7:39 AM, Jesse Keating
<jkeating(a)j2solutions.net> wrote:
> An update that changes behavior for the end user would never be
> acceptable as an update to a stable release. Only severe exceptions
> should be made to this rule, where the time/effort to backport the
> important fixes from a new upstream release are cost prohibitive and too
> complicated to do on our own.
Uhm... there are end-user applications under active development that
see monthly-ish updates that can include UI changes and bug fixes
together. In fact UI changes could be considered bugfixes. Are you
sure there is a bright line concerning changes to end-user observable
behavior? I'm not. Bugfixes can deliberately and purposefully change
behavior that some users are used to.
I'm a package maintainer for one such application. I have yet to hear
from a single user...ever..that tracking releases from upstream has
been unwanted for this specific application regardless of the UI
tweaks that happen between upstream releases. In fact I have bug
reports to the contrary asking me to push newer versions because I
originally held back updates across a significant upstream version
boundary.
Am I going to be disallowed from tracking upstream's release schedule
for this particular application by providing monthlyish updates and
moving them through updates-testing into updates-released?
I appreciate that there are going to be exceptions to the rule. There
are going to be packages or suites of packages where the users far and
away prefer always the latest whenever possible. In the cases where
these packages are "leaf node" with little interaction across the rest
of the distro I think that's fine to have a stated exception (and
expectation) to the policy. But they should be the exceptions and not
the rules.
- --
Jesse Keating
Fedora -- FreedomĀ² is a feature!
identi.ca:
http://identi.ca/jkeating
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAkx9akMACgkQ4v2HLvE71NW9IgCfU13FFR/bkUuZO25gBz4NSqrC
PJsAnR6HwtshFaBMTrdOsidayuEcX2V7
=YK8m
-----END PGP SIGNATURE-----