Hi all, In preparation of the new Restlet Framework 3.0 dev cycle, some clean-up was due in our GitHub issue tracker<https://github.com/restlet/restlet-framework-java/issues> .
I have just reorganized the tags for clarity and constency based on our recent experience. We now have six aspects/dimensions for an issue: - *Distribution: *Zip | Maven | Eclipse (p2) | Windows - *Version: *2.1 | 2.2 | 3.0 - *Edition: *Android | GAE |GWT | Java SE | Java EE | OSGi - *Module: *Restlet API | Restlet Engine | Forge | Documentation - *Extension: *Atom | Crypto | ... - *State: *new | analysis | implementation | testing | escalated - *Type: *bug | feature | enhancement | task - *Priority: *critical | high | medium | low Work still has to be done to properly label existing issues, but when you enter new issues, please try to properly set the labels for each dimension. I've also cleaned up our milestones so provide the realistic set of issues that we are working on instead of the desired set. We will now use the "Priority" level to express this. Here is the current set of milestones we have: - 2.1.7 : due tomorrow - 2.2 RC1<https://github.com/restlet/restlet-framework-java/issues?milestone=6&state=open> : due tomorrow - 2.2.0 : due end of February - 3.0 M1<https://github.com/restlet/restlet-framework-java/issues?milestone=17&state=open> : due end of February - Unplanned<https://github.com/restlet/restlet-framework-java/issues?milestone=7&state=open> Best regards, Jerome -- http://restlet.org http://twitter.com/#!/jlouvel ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3072641
