Keith and I went through all the existing issues and feature requests (and added a few) and divided them into two categories. Those we thought warranted consideration for 1.1 (which we assigned to the 1.1 milestone), and those which we don't mind postponing to a future release (1.2? 1.5? 2.0?).
Lacking an appropriate milestone, the latter issues are all currently assigned to "none". We should add a "v.next" or "future" milestone that we can keep rolling postponed issues into indefinitely. Can an admin add such a milestone (I'd vote for "future", but whatever) and move the "none" issues there? Jonathan Marsh - <http://www.wso2.com> http://www.wso2.com - <http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com
_______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
