Re: SCA 2.0, was Re: Next SCA release

2008-04-10 Thread Simon Laws
On Thu, Apr 10, 2008 at 8:12 AM, ant elder [EMAIL PROTECTED] wrote: On Wed, Apr 9, 2008 at 10:23 PM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: snip 1.3 sounds good to me. I'm assuming that we'll cut that branch out of trunk? I'm asking because I'm interested in working on

Re: SCA 2.0, was Re: Next SCA release

2008-04-10 Thread Simon Laws
On Thu, Apr 10, 2008 at 12:43 PM, Mark Combellack [EMAIL PROTECTED] wrote: -Original Message- From: ant elder [mailto:[EMAIL PROTECTED] Sent: 10 April 2008 12:26 To: [EMAIL PROTECTED] Subject: Re: SCA 2.0, was Re: Next SCA release On Thu, Apr 10, 2008 at 12:01 PM, Simon Laws

Re: SCA 2.0, was Re: Next SCA release

2008-04-10 Thread Luciano Resende
On Thu, Apr 10, 2008 at 4:43 AM, Mark Combellack [EMAIL PROTECTED] wrote: * Version 2.x will be the main focus * Most of the development effort happens on Version 2.x * We will make API changes which means that it will not be backwards compatible with version 1 * Version

Re: SCA 2.0, was Re: Next SCA release

2008-04-10 Thread Simon Nash
Comments inline. Simon Simon Laws wrote: On Thu, Apr 10, 2008 at 12:43 PM, Mark Combellack [EMAIL PROTECTED] wrote: -Original Message- From: ant elder [mailto:[EMAIL PROTECTED] Sent: 10 April 2008 12:26 To: [EMAIL PROTECTED] Subject: Re: SCA 2.0, was Re: Next SCA release On Thu

Re: SCA 2.0, was Re: Next SCA release

2008-04-09 Thread Jean-Sebastien Delfino
haleh mahbod wrote: 1 - [] Put V2 doc changes in V1 pages and mark them as such 2 - [] Create SCA Java 1.x/ SCA Java 2.x documentation pages on our current site wiki 3 - [] Create separate SCA Java 1.x/ SCA Java 2.x wiki spaces Option 2 seems reasonable. Option 3 can be considered in the