[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stable branch for documentation changes
|
From: |
Ben Abbott |
|
Subject: |
Re: Stable branch for documentation changes |
|
Date: |
Tue, 19 Apr 2011 09:14:21 -0400 |
On Apr 19, 2011, at 12:54 AM, Jordi Gutiérrez Hermoso wrote:
> On 18 April 2011 18:29, Rik <address@hidden> wrote:
>> Just a reminder that documentation changes usually belong on the stable
>> branch. I've seen two changesets (12617:fb2e14a276d2, 12610:bdf694af4aa5)
>> which are on default, but should probably be transplanted to stable.
>
> Oops, sorry, my bad for one of those. I hadn't even considered that
> documentation fixes should go on stable. I do suppose they can't
> possibly break anything critical. Do we have consensus on this? Doc
> fixes except for new features go on stable?
>
> - Jordi G. H.
jwe, mentioned the policy here
http://octave.1599824.n4.nabble.com/policy-for-pushing-changesets-td3443512.html
... and earlier on the thread below (Apr 07, 2011; 11:28am).
http://octave.1599824.n4.nabble.com/Re-Bug-tracker-and-transplants-td3421123.html
The other changeset was mine, I think.
Ben