Changes between Version 3 and Version 4 of ReleasePractices/PostBetaMerges


Ignore:
Timestamp:
Oct 27, 2008, 1:25:03 PM (14 years ago)
Author:
Beman Dawes
Comment:

Add comment based on post from Phil Endecott

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/PostBetaMerges

    v3 v4  
    1919 * '''New features, breaking changes, major reworks, new libraries.''' These are not suitable for merging between beta and release. Wait until the next release.
    2020
     21== Comment ==
     22
     23One factor considered by release managers in approving code changes is whether the fix is for a regression relative to the last release or a fix to a long-standing problem.  From the point of view of an end-user, the difference between the new version "still not working" and "being more broken than the last" is significant. Even uncomfortably large fixes may be accepted if they are fixing regressions, while minor fixes that do not fix regressions will only be accepted if obviously harmless.
     24
    2125== Acknowledgments ==
    2226
    23 Joaquín M López Muñoz, John Maddock, and Robert Ramey made helpful suggestions during the development of this policy.
     27Joaquín M López Muñoz, John Maddock, Robert Ramey, and Phil Endecott made helpful suggestions during the development of this policy.
    2428
    2529----