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
That's not how I read it at all, especially now that we have Roy's updated definition of what a release is: http://www.apache.org/dev/release.html#what I don't see any reason to avoid tags and branches in labs. After all, they're useful for development, not just for flagging releases. -- Martin Cooper 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]
