El mié, 21-06-2006 a las 12:27 -0400, Gregor J. Rothfuss escribió: > Thorsten Scherler wrote: > > > Regarding 3. I think we should consider a stable trunk policy because > > developing with the trunk and having regular releases gives benefits for > > new apps based on lenya. > > a stable trunk policy implies more frequent branches. i gather you took > this idea from forrest? how is it working over there?
Since some committer (me as well) prefer to develop new (or dangerous) code in plugins which can be deactivated easily we have used this policy rarely. The locationmap was incorporate into forrest with a branch. > > > We should quickly discuss this open points and then vote on this > > guideline draft that they become official. > > agreed. > > how about, for 1 & 2: > > Index: guidelines.xml > =================================================================== > --- guidelines.xml (revision 415420) > +++ guidelines.xml (working copy) > @@ -605,6 +605,15 @@ > <section id="code"> > <title>Code management</title> > > + <p>Development on the Lenya codebase happens on the trunk, unless a > vote to create a branch > + has passed. Experimental code not immediately intended for > merging into trunk may > + be commited to the sandbox. In order to prevent a code > graveyard, sandbox contents will > + be reviewed every 6 months and either merged into trunk, > promoted to their own top-level directory, > + or deleted. At any one time, the Lenya project maintains one > release branch. At appropriate > + times, the Lenya project may cut a new release branch from > trunk, and retire the previous one. > + Old release branches are kept in SVN, but are clearly marked as > unmaintained both in SVN and on the web site. > + </p> > + +1 Can you commit this change. I will wait for this commit and then start the vote thread. Thanks Gregor. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
