[PATCH 1 of 6 stable] help: use strip instead of mq as in 'hg help config' example
Matt Mackall
mpm at selenic.com
Sun Dec 1 13:02:02 CST 2013
On Wed, 2013-11-27 at 10:26 -0500, Augie Fackler wrote:
> On Sat, Nov 23, 2013 at 08:02:52PM +0100, Martin Geisler wrote:
> > # HG changeset patch
> > # User Martin Geisler <martin at geisler.net>
> > # Date 1385136763 -3600
> > # Fri Nov 22 17:12:43 2013 +0100
> > # Branch stable
> > # Node ID 62bc6f9d0080426eaa7cafd4f5f051ca2efd3a13
> > # Parent 06ef32c3b4bb2974749eefa171434903fe887e46
> > help: use strip instead of mq as in 'hg help config' example
>
> Are help edits like this really right for stable?
Yes. Here is the set of things that are acceptable:
* bug fixes
* error message improvements
* doc fixes
* template fixes
* improved translations
http://mercurial.selenic.com/wiki/TimeBasedReleasePlan
The question you should ask yourself when evaluating something for
stable is "what is the ratio of end-user reward vs upgrade risk?"
The risk ratio for doc cleanups is quite good as there's very little
risk that they'll ruin a user's day after an upgrade, but there's a
decent chance they'll make a user's day better.
By comparison, the opposite is true for "trivial code cleanups": they
intentionally have no user-visible benefits but they're often not quite
as trivial as you think.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list