Geir Magnusson Jr. wrote:
robert burrell donkin 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.
nope, I don't agree. A release has many more implications than that. A
SVN tag is simply a marker.
so (for me) a literal reading of the 'no release' rule excludes all
tags from the apache repository
Nope, I don't agree :)
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?
I'm still anti-release, as the requirements for a release then involve
oversight by the labs' PMC etc etc, and turn this into another incubator.
My personal opinion is that if your project in the lab looks viable and
you want to begin releasing and getting users, then the Incubator is the
right place for the project.
agreed
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
