Not sure if the question of svn tagging was answered here. I was definitely interpreting 'No releases' to mean 'No distributing' and not 'No tagging'. The idea of developing without being able to create tags/branches is bizarre to me.
Hen On 12/3/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
release early, release often! i understand and agree with the reasons behind the 'no releases rule' but wonder whether team labs may need to consider how they will interpret this rule and offer some documented guidelines. people disagree about what a release is IMO a release is fundamentally just a line in the sand: a tag in subversion. what matters is the source. everything else is just packaging. so (for me) a literal reading of the 'no release' rule excludes all tags from the apache repository this leads on the issue of offshore tags and releases. one approach for those who need releases would be to use subversion to create offshore tags. a more radical approach would be to cut releases offshore. given that maven requires released dependencies, i suspect that these issues are going to have to be tackled sooner or later. opinions? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
