[Grok-dev] when "trunk" becomes a distribution point: disaster?

Shane Hathaway shane at hathawaymix.org
Mon May 12 15:55:35 EDT 2008

Brandon Craig Rhodes wrote:
> 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.

+1.  I have already seen buildout scripts for RelStorage that rely on
the trunk.  Those dependencies limit my freedom to explore and I think I
may remove the trunk directory from Subversion.  That isn't the only
reason for me to remove the trunk, however: after working with Mercurial
for a while, branching and merging make a lot more sense to me and the
concept of a trunk no longer seems useful.


More information about the Grok-dev mailing list