Hi Rivetters
the subject of the message should be self explaining and my proposal
comes after Ronnie's question about the choice of branching instead of
tagging.
I put forward the proposal to create a 'tags' directory in the
repository where we can create tagged versions when we release (e.g.
current '2_0' in branches would become tags/2_0_0). Benefits of the
operation:
- Even though we have the tarballs, keeping tagged branches in the
repository allows for better and faster code analysis.
- We can carry on the development in trunk, copying compatible changes
to the 2_0 branch when we know it can be done, and at the same time we
can follow threads of development in 2_0 and trunk separately, still
having the milestone of the tag branch around.
- Keeping a tagged branch makes docs and informational files (INSTALL,
README, html pages, etc) of a release available through svn. This
enables us to link into the website the right version of those
documents, instead of copying. This can be done by simply creating a
directory in the our site, putting it in control of svn, and editing its
'external' property: a much faster and error proof operation when new
releases happen.
This probably sounds like too much for a project that had only a few
active committers in the last years, but given the very small cost and
difficulty of the operation and the improved project management the
would ensue, I think we should consider it carefully.
feedback is welcome.
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
