5.4-alpha-x should not be a snapshot at all. It's a release. An alpha release, but a release. 5.4-SNAPSHOT should be the bleeding edge nightly builds.
On Jan 22, 2013, at 6:54 AM, Massimo Lusetti wrote: > I feel lazy but now I think I understood what Uli was talking about. > > If you look at the apache snapshot repository, for example the IoC: > https://repository.apache.org/content/groups/snapshots/org/apache/tapestry/tapestry-ioc/ > > You can see that the latest snapshot is 5.4-alpha-3-SNAPSHOT instead of > 5.4-SNAPSHOT > > I do agree that having a "frozen snapshot" like 5.4-alpha-3 is a very good > idea for the early adopters but the latest snapshot has to remain > 5.4-SNAPSHOT which is the real bleeding edge and used by T5 developers. > > So what Jenkins builds should go with 5.4-SNAPSHOT while if we want to > produce an intermediate release for early adopters we should change it to > 5.4-alpha-x or whatever applicable. > > Thoughts!? > > > On Tue, Jan 8, 2013 at 12:40 AM, Massimo Lusetti <[email protected]> wrote: > >> I do agree, having the possibility to specify a precise target as a dep >> while testing an upgrade is by far a better solution then having a moving >> target >> > > > > -- > Massimo > http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
