>> What shall we call this next release? Following on from the last >> release it would be 2.0-Beta3, another option could be 2.0. What else >> do we need to get done before we're ready for a 2.0 release? If its a >> short list of todo's should we just work on getting those done and >> going straight to 2.0 for the next release? >> > > Any comments on the release name? > > I'm back from being on holiday now and it looks like there are enough > others active to get a release vote out so I'd like to have another go > and getting a release out. Unless anyone asks otherwise I'll probably > do a bit of clean up and review this week and cut an RC next week. > > ...ant >
I've noticed some discussion on the OASIS list about the optional requirements and associated tests. Maybe Mike would be better placed to comment on any likely implications. I'd say go with 2.0-beta3 until the dust is settled in case we have to change anything. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
