it isn't only about one release. e.g. 2.1.0 was just skipped and at least a part is broken since months (see [1] and [2]). therefore i called this thread "trinidad.next" instead of "trinidad 2.1.1".
imo: the current situation isn't acceptable for users. committers who work on trinidad on a regular basis should also do releases on a regular basis. regards, gerhard [1] https://issues.apache.org/jira/browse/TRINIDAD-2422 [2] https://builds.apache.org/job/Trinidad%20Core%20Trunk%20(snapshot)/ 2013/10/18 Hazem Saleh <[email protected]> > +1 for a release too. > > > On Fri, Oct 18, 2013 at 2:12 PM, Werner Punz <[email protected]>wrote: > >> Am 17.10.13 22:47, schrieb Gerhard Petracek: >> >> hi @ all, >>> >>> we haven't seen a trinidad release for almost >20 months<. >>> it's known that other projects are based on trinidad and therefore it's >>> obvious that they have to use snapshot versions. >>> >>> imo: >>> since there are commits on a regular basis, there should be also >>> releases on a regular basis. >>> >>> regards, >>> gerhard >>> >> +1 for a release >> >> >> Werner >> >> >> > > > -- > Hazem Saleh > > Author of JavaScript Unit Testing book: > http://www.amazon.com/dp/1782160620/ > > Co-author of (The Definitive Guide to Apache MyFaces and Facelets) book: > http://www.amazon.com/-/e/B002M052KY > > DeveloperWorks Contributing Author > > https://www.ibm.com/developerworks/mydeveloperworks/blogs/hazem/entry/ibm_developerworks_contributing_author?lang=en_us > > An Apache committer, IBMer, and a technical speaker > > Twitter: http://www.twitter.com/hazems >
