On 09/01/2011 11:40 AM, Daniel Villarreal wrote:
sent to Amit and Antoine...
On Thu, Sep 1, 2011 at 11:37 AM, Daniel Villarreal
<yclwebmas...@gmail.com>wrote:
So any changes, including documentation, need to be checked against
-current ?
yes.
Development work is done on -current.
Do NOT waste people's time with cosmetic errors on past releases or even
a current release, always look at what is in the tree NOW. OpenBSD
makes that available -- you can see what is in any file within an hour
or so of someone making a change (the lag isn't to annoy you, it's to
allow the data to replicate out from the master repository). Cosmetic
changes won't be pushed back to old (or even current) releases.
In the case of CHANGES to the system...same thing. work with -current,
make your diffs against -current. No features will be added to past
releases...and a diff that doesn't apply (or work!) against where the
developers are working is annoying. If it takes you three weeks to make
your change, before submitting it update all the code to -current
(AGAIN), verify your change still works, then submit the diff.
In the case of security or reliability issues...that's a different
story. If you find a functional problem against 4.9-release, they may
want to make an addition to -stable based on it. But still, the process
is fix in -current first, then push back to -stable.
Nick.
