On Tue, Nov 11, 2008 at 10:11 AM, Simon Laws <[EMAIL PROTECTED]> wrote: > We've agreed that we are going to develop OASIS compliant function in trunk. > I just started a discussion on what the starting point is. But what are the > themes for trunk up to the 2.0 release? What would we hope to be announcing > in the release notes that are going to get people excited? What are this > things that are going to make the code base easier to work with? > > OASIS is clearly on the list. Ant's survey should help. But what else? > > IMO this is not really about a detailed shopping list of code changes but > more about themes (as per the thread title), i.e. more the what than the > how. >
Here's some things i think it could be good to look at: More coherent documentation. Maybe try to have a set of documentation specifically for 2.0 that covers all the major features and functions as well as introductory getting started, and how to run and environment type options to help new users. Clearly document what the official APIs and SPIs are and how we recommend people use them to be supported across releases. And don't leave all this as an after thought - don't release 2.0 till we think the doc is in an ok state. Improved JEE/Webapp support. Its a bit neglected these days in Tuscany but this seems to be how most people run Tuscany so we should make it work really well. Have it be a or participate well in a domain with complete wiring support, all the main Tuscany extensions working and tested in this environment, and support some standard Web frameworks so people can use what they know - JSP, JSF, Struts, Wicket, GWT, Flex etc, even if we don't support all of those at least show how it could be done. Policy and QoS a big part of SCA is declarative policy so we should demonstrate that with things like transactions and confidentiality support which work and consistently across Tuscany extensions and environments. Distribution users keep commenting on it and we keep talking about it. I don't think we'll find a single solution that suits every environment and makes everyone happy but i don't think what we have today (in any branch) is the complete answer yet. One thing I'd like to see is a lot less jars and an easier way to build without transitive dependencies. I also think it would be good to have a minimal runtime that can run simple things like calculator with just a single jar to make it look really easy to get started with Tuscany - and we can do this with JDK6 as it includes all the dependencies we need. Find a way to make the build easier. Not sure exactly how yet :) but its so big and hard it puts people off helping and a 45 minute build is too long. ...ant
