On Fri, Jun 24, 2011 at 5:21 PM, Kalle Korhonen <[email protected]> wrote: > On Fri, Jun 24, 2011 at 4:57 PM, Howard Lewis Ship <[email protected]> wrote: >> So my proposal: >> Tapestry release version numbers consist of three numbers and an >> optional suffix. >> Thus a complete version number might be "5.3-alpha-2". >> final releases have no suffix, thus "5.3" will be the final version >> number for the Tapestry 5.3 major release >> How does that sound? It also means that our next version number will >> be "5.3-alpha-2" ... and perhaps we should consolidate our JIRA >> version numbers. > > First of all, it's easy to freeze -SNAPSHOT - I publish frozen > snapshots (i.e. version x.x-mycompany-1) all the time to company's > internal Maven repo just so that I can take advantage of auto-built > snapshots but at the same not block releasing our own products. > > Anyway, I just don't think you are thinking through the full > implications of this (but it could be me as well who isn't :). The > version resolution will not work as well with alpha, beta etc. > suffixes and I can just see lots of third party library developers > releasing against alpha versions which may just add to the confusion. > If the concern is with stability and we want to limit the audience, > let me suggest an alternative: numeric versions only but alphas and > release candidates are only available through staging repo (which can > be longer lived than what we now typically use) and we advertise the > repo url to a bigger audience (on the user list). For suffix proposal, > I'm prepared to cast my -1 for reasons I've stated in this thread (but > as non-binding, feel free to ignore). >
I think we're coming to a collision in basic goals; I really want to focus on a way to maximize exposure of Tapestry betas and RCs prior to a final release, to help ensure that the final release really is final. A secondary goal here is to make it easier for people to "read" the version number and know the stability without referencing other sources; Will 5.3.7 be an alpha release, a beta release, or a release candidate? What about 5.3-rc-2? This is really two different discussions: how we release non-final versions, and how we number and label them. I think the Apache Powers-That-Be might like a secondary repository used for less-than-final releases, and certainly with Maven/Gradle/Ivy its easy enough for people to temporarily accesss such a repository. It could just be a matter of staging to the Apache Nexus and closing, but not ever releasing, the repository. > Kalle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
