On Tue, 28 Jun 2011 14:25:34 -0300, Howard Lewis Ship <[email protected]>
wrote:
As I'm interpreting it, the "previews" are not releases as they are
not distributed via the Apache Mirrors or Maven Central, and will take
a small amount of work to access (updating the list of Maven
repositories in the build script).
Thanks for the clarification. :)
So the process is that a developer will generate the preview
artifacts, and deal with committing the version number changes and
create a tag. Then a vote starts. At the end of the vote, a message
can go out on the user mailing list along the lines of:
I don't think we'll have more votes than we already do, as all artifacts,
releases or not, have been having a version number and votes.
Previewing a release is a great way to help us ensure the stability of
the final release, and learn about any upgrade problems early enough
to address them. It's a great way to contribute back to the Tapestry
community!
Agreed. :) I don't think the need to add a Maven repository for using
alpha and beta versions will be a problem for early adopters. They're
already the more knowledgeable, experimenting users.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
