We had a big discussion some time agao about the way to do things, and we even captured the results of the dicussion in Confluence:
http://tapestry.apache.org/version-numbers.html So for once, I feel like I'm on the right side of a "following procedures" discussion. Snapshots have their place, but the stability of a preview release has its value, despite the hoops Nexus makes you jump through. It says that this particular binary represents a consistent view, and is stable enough for evaluation and discussion; a snapshot doesn't have even that level of guarantee. I'm always up for more discussion and votes on procedure ... but I'd much rather see people putting their energy into code or documentation right now! On Sun, Jan 6, 2013 at 4:15 PM, Ulrich Stärk <[email protected]> wrote: > Can we please stop using per-preview repositories and put previews into > the snapshots repository > where they belong IMO? That would make those previews more easily > available since the repository URL > won't have to be changed between snapshots. > > Uli > > On 03.01.2013 23:01, Howard Lewis Ship wrote: > > I've created a new preview release, available from the Maven repository > at > > > > > https://repository.apache.org/content/repositories/orgapachetapestry-096/ > > > > this includes the new jQuery support I recently blogged about. > > > > Feedback desperately desired! > > > > --------------------------------------------------------------------- > 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
