Thanks Guys, my idea is to wrap up any in progress work and create a branch middle of next week. It would be great In the mean time, it would be good if we all could take a quick look at JIRAs and start fixing them or marking them for 1.2 release.
Thoughts ? On Wed, Mar 5, 2008 at 4:31 AM, ant elder <[EMAIL PROTECTED]> wrote: > On Wed, Mar 5, 2008 at 11:57 AM, Simon Laws <[EMAIL PROTECTED]> > > > wrote: > > > On Wed, Mar 5, 2008 at 11:45 AM, Venkata Krishnan <[EMAIL PROTECTED]> > > wrote: > > > > > +1 for Luciano as RM. I'd be happy to help wherever required. Thanks > > for > > > volunteering, Luciano. > > > > > > - Venkat > > > > > > On Tue, Mar 4, 2008 at 11:06 PM, Luciano Resende <[EMAIL PROTECTED]> > > > wrote: > > > > > > > Time flies and is already March. I'd like to restart discussion on > > > > this thread and start building a list of things we want to do for SCA > > > > 1.2 and I'd also like to volunteer for Release Manager for SCA 1.2 > > > > release. > > > > > > > > On Thu, Feb 14, 2008 at 8:52 AM, Simon Laws <[EMAIL PROTECTED] > > > > > > > wrote: > > > > > Hi > > > > > > > > > > It's probably about time we started talking about what's going to > > be > > > in > > > > > Tuscany SCA Java release 1.2. From the past timeline I would expect > > > us > > > > to be > > > > > trying for a release mid to late March which is not very far away. > > > > > > > > > > Some of the things I'd like to see are; > > > > > > > > > > More progress on our domain level composite and generally the > > > > processing > > > > > that has to go there > > > > > There have been a lot of policy changes going on and it would be > > good > > > > to get > > > > > them in. Also linked to the item above we should look at how policy > > > > affects > > > > > domain level processing. > > > > > Don't know if it's achievable but some elements of the runtime > > story > > > we > > > > have > > > > > been talking about on the mail list for a while now > > > > > > > > > > Feel free to add topics on this thread. I've also opened up the > > > > > Java-SCA-1.2category in JIRA so start associating JIRA with it, for > > > > > example, if > > > > > > > > > > 1 - you've already marked a JIRA as fixed and its sitting at > > > > Java-SCA-Next > > > > > 2 - you are working or are going to work on the JIRA for 1.2 > > > > > 3 - you would like to see the JIRA fixed for 1.2 > > > > > > > > > > Of course everyone is invited to contribute and submit patches for > > > JIRA > > > > > whether they be for bugs or new features. Inevitably not all "wish > > > > list" > > > > > features will get done so you improve your chances of getting you > > > > favorite > > > > > feature in by submitting a patch for it. > > > > > > > > > > Regards > > > > > > > > > > Simon > > > > > > > > > > > > > > > > > > > > > -- > > > > Luciano Resende > > > > Apache Tuscany Committer > > > > > http://people.apache.org/~lresende<http://people.apache.org/%7Elresende> > > <http://people.apache.org/%7Elresende>< > > > http://people.apache.org/%7Elresende> > > > > http://lresende.blogspot.com/ > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > +1 Luciano as RM. Thanks Luciano for volunteering! So what are we actually > > looking at as a timeline? Do we think we can get an RC to vote on before > > the > > end of this month ready for a release as early as possible in April. > > > > Simon > > > > Aiming for that sounds good to me. > > And slightly off topic but in way of helping accept the "less and sooner" > approach for 1.2 how about thinking in the back of our minds of a v2.0 for > May/June that includes all the things like runtime and distribution > restructuring, SPI cleanup, and hopefully being able to include a > post-graduation dropping of the "-incubating" suffix. > > ...ant > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
