I think we are in agreement. If you check the instructions for generating
an official release, the first steps are exactly what goes into a preview
release.


On Thu, Dec 19, 2013 at 11:16 AM, Kalle Korhonen <kalle.o.korho...@gmail.com
> wrote:

> Absolutely. All I was saying we need to vote on the exact bits that are to
> be officially released rather than package it up later. I don't think we
> have a suitable "buildable source" package in the wild to vote on.
>
> Kalle
>
>
> On Thu, Dec 19, 2013 at 8:44 AM, Howard Lewis Ship <hls...@gmail.com>
> wrote:
>
> > Actually, there's no reason not to run a vote on the bits "already in the
> > wild".  The only difference would be that after a succesful vote, we
> could
> > move the stuff in ~hlship/public_html/tapestry-releases to the right
> > locations, and release the artifacts to the central Maven repository.
> >
> >
> > On Wed, Dec 18, 2013 at 6:54 PM, Kalle Korhonen
> > <kalle.o.korho...@gmail.com>wrote:
> >
> > > Sure, I remember it well and I agree the light-overhead staging release
> > > process has worked well for the alphas. However, it's up to us to
> decide
> > > when to make an official Apache release though and it's official only
> > when
> > > we put the tagged source on the /dist. I think the time is now.
> Regarding
> > > naming, 5.4-beta-1 works well. If we clearly label this a beta, then
> > > there's no point adding GA for the numbered only (5.4.0) release when
> we
> > > decide to remove (to make the first release without) the beta label.
> This
> > > will also work great for version ranges. If we stick with the
> > conventional
> > > definition of a beta, we are making the software available outside the
> > > development organization. Nowadays, deploying the bits to Maven central
> > is
> > > the best way to get more exposure.
> > >
> > > Howard, I know you are allergic to any processes but it's an accepted
> > > convention that we (any ASF project) make the source available for
> review
> > > and vote on that. I'm not absolutely sure we can simply take a vote on
> > the
> > > staging release you generated as we don't have source tarball. (There's
> > >
> > >
> >
> https://repository.apache.org/content/groups/staging/org/apache/tapestry/tapestry-core/5.4-beta-1/tapestry-core-5.4-beta-1-sources.jarbut
> > > I don't think it qualifies as a buildable source). I'm sure Massimo
> > > would be more than happy to act as a release manager, or I can work
> > through
> > > it as well. There's still time to make it a nice Christmas gift to the
> > > Tapestry community!
> > >
> > > Kalle
> > >
> > >
> > > On Wed, Dec 18, 2013 at 8:54 AM, Howard Lewis Ship <hls...@gmail.com>
> > > wrote:
> > >
> > > > We had a big discussion about this stuff in the archives and I
> believe
> > > I've
> > > > been following the procedure we arrived at.
> > > >
> > > >
> > > > On Wed, Dec 18, 2013 at 3:03 AM, Thiago H de Paula Figueiredo <
> > > > thiag...@gmail.com> wrote:
> > > >
> > > > > I guess the rationale here, changing from alpha to beta, is to say
> > that
> > > > an
> > > > > alpha is a work in progress with no backward compatibility promise
> in
> > > new
> > > > > APIs, while beta is more of a release candidate and something
> > > considered
> > > > > stable. Am I right? :)
> > > > >
> > > > >
> > > > > On Wed, 18 Dec 2013 07:37:48 -0200, Massimo Lusetti <
> > > mluse...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >  I agree with Kalle.
> > > > >>
> > > > >> Actually I don't know if we have to change the naming convention
> or
> > > not
> > > > to
> > > > >> have a full release which is not really declared "stable" or
> > "general
> > > > >> availability" (GA) but I've never seen a *-beta-1 release on
> > > > >> repo1.maven.org
> > > > >>
> > > > >> Anyway a more exposure of the current "beta" will produce an even
> > more
> > > > >> stable GA release ...
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Wed, Dec 18, 2013 at 10:17 AM, Kalle Korhonen <
> > > > >> kalle.o.korho...@gmail.com
> > > > >>
> > > > >>> wrote:
> > > > >>>
> > > > >>
> > > > >>  Personally, I really think we should release/should have released
> > the
> > > > >>> beta
> > > > >>> as a proper Apache release that has been voted on and that the
> the
> > > bits
> > > > >>> would have been released through official channels (published on
> > > /dist
> > > > >>> and
> > > > >>> maven central). Now nothing really changed between alpha and beta
> > > > preview
> > > > >>> releases besides the tag.
> > > > >>>
> > > > >>> Kalle
> > > > >>>
> > > > >>>
> > > > >>> On Tue, Dec 17, 2013 at 10:41 AM, Howard Lewis Ship <
> > > hls...@gmail.com
> > > > >>> >wrote:
> > > > >>>
> > > > >>> > Following a beta release vote, I've generated the first beta
> > > preview
> > > > >>> > release of Apache Tapestry 5.4.
> > > > >>> >
> > > > >>> > The bundles version of Bootstrap has been updated to 3.0.3, and
> > > > jQuery
> > > > >>> to
> > > > >>> > 1.10.2.
> > > > >>> >
> > > > >>> > Tapestry now bundles moment.js, and adds new components
> LocalDate
> > > and
> > > > >>> > TimeInterval. LocalDate displays a date/time formatted by the
> > > client,
> > > > >>> in
> > > > >>> > the client's time zone. TimeInterval displays a time interval
> > > between
> > > > >>> two
> > > > >>> > points, such as "3 hours"; if the start or end time is omitted,
> > it
> > > > >>> > dynamically updates using the current time .. great for
> > displaying
> > > > time
> > > > >>> > until an auction ends, or time since a blog post was updated.
> > > > >>> >
> > > > >>> > There's also been some fixes for broken localized messages.
> > > > >>> >
> > > > >>> > Tapestry preview releases are  available via Maven, from the
> > Apache
> > > > >>> Staging
> > > > >>> > repository:
> > > > >>> >
> > > > >>> > https://repository.apache.org/content/groups/staging
> > > > >>> >
> > > > >>> > --
> > > > >>> > Howard M. Lewis Ship
> > > > >>> >
> > > > >>> > Creator of Apache Tapestry
> > > > >>> >
> > > > >>> > The source for Tapestry training, mentoring and support.
> Contact
> > me
> > > > to
> > > > >>> > learn how I can get you up and productive in Tapestry fast!
> > > > >>> >
> > > > >>> > (971) 678-5210
> > > > >>> > http://howardlewisship.com
> > > > >>> >
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > > > --
> > > > > Thiago H. de Paula Figueiredo
> > > > > Tapestry, Java and Hibernate consultant and developer
> > > > > http://machina.com.br
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> > > > > For additional commands, e-mail: dev-h...@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Howard M. Lewis Ship
> > > >
> > > > Creator of Apache Tapestry
> > > >
> > > > The source for Tapestry training, mentoring and support. Contact me
> to
> > > > learn how I can get you up and productive in Tapestry fast!
> > > >
> > > > (971) 678-5210
> > > > http://howardlewisship.com
> > > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

Reply via email to