[Grok-dev] when "trunk" becomes a distribution point: disaster?
Brandon Craig Rhodes
brandon at rhodesmill.org
Sun May 11 05:47:26 EDT 2008
I note that lots of projects, including Grok's trunk, pull
"bootstrap.py" directly from its "trunk", which is what my "buildout"
introduction web page suggests as well. Is this wise? Should it
instead have a "tags/current" or "branches/current-release" directory
that's copied to each time a new stable version comes out? It seems
that the current arrangement makes it impossible to do any development
on "trunk" like a normal project, because the "trunk" version is the
one that every needs to keep working.
Brandon Craig Rhodes brandon at rhodesmill.org http://rhodesmill.org/brandon
More information about the Grok-dev