The assignment of issues to milestones seems odd, but maybe this was true before the 1.2 -> 2.0 renaming: Why are all the defects associated with 2.0M4 and not 2.0M3? I was hoping to be able to develop a Restlet 1.2-based system over the next 5-6 months and put it into production at the end of the year. Does the acknowledgment of the broader scope make the 2.0 release less likely for 2009Q4?
--tim On Wed, May 6, 2009 at 4:57 AM, Jerome Louvel <[email protected]>wrote: > Hi all, > > > > Looking at the amount of new features that we added so far since Restlet > 1.1 (with some more coming), the amount of refactoring and reorganization > done in the Restlet API (touching the core Resource API) and extension > packages and the growing number of special Restlet editions (Java SE/Java > EE, GWT, Google App Engine and soon Android), it seems appropriate to rename > the Restlet 1.2 release into Restlet 2.0. > > > > The idea is to give existing users an accurate feeling of the amount of > effort required when upgrading from Restlet 1.0 or Restlet 1.1 and for new > users to realize the amount of effort and changes done since Restlet 1.x. > > > > I hope it will make sense to you guys. We have updated our issue tracker > and our roadmap here: > > http://www.restlet.org/about/roadmap > > > > Next release will be Restlet 2.0 M3 and will replace the current Restlet > 1.2 M2 (tagged “testing”). > > > > Best regards, > Jerome Louvel > -- > Restlet ~ Founder and Lead developer ~ http://www.restlet.org > Noelios Technologies ~ Co-founder ~ http://www.noelios.com > > > > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2080650
