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?
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>
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
