Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-04 Thread ant elder
Ok, I've started to use 0.90 for the name for now. Can easily change it if something better comes up. ...ant On 5/3/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote: +1 for 0.90 - Venkat On 5/2/07, ant elder <[EMAIL PROTECTED]> wrote: > > It would be good to choose a name soon so we can star

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-03 Thread Venkata Krishnan
+1 for 0.90 - Venkat On 5/2/07, ant elder <[EMAIL PROTECTED]> wrote: It would be good to choose a name soon so we can start completing all the readme's and release notes etc, there doesn't seem much consensus on beta1 so how about 0.90? That sounds closer to 1.0 than M3 or alpha and still give

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-03 Thread Simon Laws
On 5/2/07, Simon Nash <[EMAIL PROTECTED]> wrote: I thought Ant's suggestion was just 0.90 and not beta anything. I can live with this. I don't think we are ready yet to call it beta 1.0 or beta1 1.0. Simon haleh mahbod wrote: > why does it matter if we call it beta1 or beta .90? It is a

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-02 Thread Simon Nash
I thought Ant's suggestion was just 0.90 and not beta anything. I can live with this. I don't think we are ready yet to call it beta 1.0 or beta1 1.0. Simon haleh mahbod wrote: why does it matter if we call it beta1 or beta .90? It is a variation of what we call beta. The fact that there i

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-02 Thread haleh mahbod
why does it matter if we call it beta1 or beta .90? It is a variation of what we call beta. The fact that there is a number after Beta is an indication that there might be revisions of Beta anyway before 1.0 release is reached. On 5/2/07, Ignacio Silva-Lepe <[EMAIL PROTECTED]> wrote: +1 on 0.9

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-02 Thread Ignacio Silva-Lepe
+1 on 0.90 On 5/2/07, ant elder <[EMAIL PROTECTED]> wrote: It would be good to choose a name soon so we can start completing all the readme's and release notes etc, there doesn't seem much consensus on beta1 so how about 0.90? That sounds closer to 1.0 than M3 or alpha and still gives space for

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-02 Thread ant elder
It would be good to choose a name soon so we can start completing all the readme's and release notes etc, there doesn't seem much consensus on beta1 so how about 0.90? That sounds closer to 1.0 than M3 or alpha and still gives space for more releases before the final 1.0. ...ant On 5/1/07, Ber

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-05-01 Thread Bert Lamb
I realize I'm a bit late to this conversation, I'm just now getting mostly unpacked from a move to Somerville, MA. I agree with Simon in that we should be careful what we call "beta". I know that we all would like to get to beta quality code and features as soon as we can, but I don't think we a

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-27 Thread ant elder
On 4/25/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: ant elder wrote: > On 4/24/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > > > So I think it comes down to whether it is more important to put >> something out by JavaOne (in which case I'd be hesitant to call it >> "beta") or whether

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-27 Thread ant elder
Both of these seem like useful suggestions. There's a scheduled IRC next Monday so lets discuss the release contents at that, in the meantime people could add their names to wiki items [1] for things that they want to get into the next release. ...ant [1] http://cwiki.apache.org/confluence/dis

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread haleh mahbod
A working release that is closer to 1.0 spec version sooner would be better than having more content and a later release. M2 is old now and has issues. Should IRC be used for a discussion on release or maybe we should update the Wiki page with (IN/Out) comment to help you? If an item has both

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread ant elder
On 4/25/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: ant elder wrote: > On 4/24/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > > > So I think it comes down to whether it is more important to put >> something out by JavaOne (in which case I'd be hesitant to call it >> "beta") or whether

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread Jean-Sebastien Delfino
ant elder wrote: On 4/24/07, Simon Nash <[EMAIL PROTECTED]> wrote: So I think it comes down to whether it is more important to put something out by JavaOne (in which case I'd be hesitant to call it "beta") or whether it is more important to attain a true "beta" level of quality even if that t

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread kelvin goodson
Ant, thanks for the pointers here. I am persisting with this, but I thought I'd just post an update as this doesn't seem to be working as it should. I have two main problems, one is when attempting to deploy the SDO tools jar by command -- see [1], the maven command removes the pom i'm trying

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread ant elder
On 4/25/07, kelvin goodson <[EMAIL PROTECTED]> wrote: I've got to the point where I have packaged up a new beta1 SDO java release candidate in the style if the last one [1], but that's only part of the process now that I have to set up a remote maven repository as a staging post for the deploye

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread kelvin goodson
I've got to the point where I have packaged up a new beta1 SDO java release candidate in the style if the last one [1], but that's only part of the process now that I have to set up a remote maven repository as a staging post for the deployed release candidate artifacts (as per the recent discuss

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-25 Thread ant elder
On 4/24/07, Simon Nash <[EMAIL PROTECTED]> wrote: So I think it comes down to whether it is more important to put something out by JavaOne (in which case I'd be hesitant to call it "beta") or whether it is more important to attain a true "beta" level of quality even if that takes a little bit

Re: Nominate Ant as the release manager was: Re: [DISCUSS] Next version - What should be in it

2007-04-24 Thread Venkata Krishnan
4, 2007 4:32 AM Subject: Re: [DISCUSS] Next version - What should be in it > How about Ant as release manager for this release? He has been very > diligent in reviewing previous Tuscany releases with many helpful > comments. He has a good understanding of the Apache requirements > and proces

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread Simon Nash
o attain a true "beta" level of quality even if that takes a little bit longer. Simon Raymond Feng wrote: +1. Thanks, Raymond - Original Message - From: "Luciano Resende" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 24, 2007 12:07 PM Subject: Re: Next release

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread Raymond Feng
+1. Thanks, Raymond - Original Message - From: "Luciano Resende" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 24, 2007 12:07 PM Subject: Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it) +1 As for DAS, as it has dependencies on SDO

Re: Nominate Ant as the release manager was: Re: [DISCUSS] Next version - What should be in it

2007-04-24 Thread Jean-Sebastien Delfino
4, 2007 4:32 AM Subject: Re: [DISCUSS] Next version - What should be in it > How about Ant as release manager for this release? He has been very > diligent in reviewing previous Tuscany releases with many helpful > comments. He has a good understanding of the Apache requirements > an

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread Luciano Resende
+1 As for DAS, as it has dependencies on SDO, I'd propose to follow the same name convention as SDO, and use beta1 as well. On 4/24/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: ant elder wrote: > What are we going to be calling this next SCA release? > > We've had M1 and M2 releases,

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread Jean-Sebastien Delfino
ant elder wrote: What are we going to be calling this next SCA release? We've had M1 and M2 releases, some alpha kernel releases, DAS are talking about an M3 release and SDO is doing an M3 release although there was some discussion about renaming that to beta1. I think milestone and alpha rele

Re: Nominate Ant as the release manager was: Re: [DISCUSS] Next version - What should be in it

2007-04-24 Thread Luciano Resende
gt; ----- Original Message ----- From: "Luciano Resende" >> <[EMAIL PROTECTED]> >> To: >> Sent: Friday, April 20, 2007 10:25 AM >> Subject: Re: [DISCUSS] Next version - What should be in it >> >> >>> +1 on focusing on the stability an

Nominate Ant as the release manager was: Re: [DISCUSS] Next version - What should be in it

2007-04-24 Thread Raymond Feng
+1. I would like to nominate Ant too. Thanks, Raymond - Original Message - From: "Simon Nash" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 24, 2007 4:32 AM Subject: Re: [DISCUSS] Next version - What should be in it How about Ant as release manager for this relea

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread Simon Laws
On 4/24/07, kelvin goodson <[EMAIL PROTECTED]> wrote: Ant, your note is well timed as I've had a couple of off-line chats with people in the last week about release naming, particularly with regard to the effect that a milestone or alpha name can have on uptake of a release. In the IRC chat o

Re: [DISCUSS] Next version - What should be in it

2007-04-24 Thread Simon Nash
to be the release manager. This way, I can learn more and get ready for the next time. Thanks, Raymond - Original Message - From: "Luciano Resende" <[EMAIL PROTECTED]> To: Sent: Friday, April 20, 2007 10:25 AM Subject: Re: [DISCUSS] Next version - What should be in i

Re: Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread kelvin goodson
Ant, your note is well timed as I've had a couple of off-line chats with people in the last week about release naming, particularly with regard to the effect that a milestone or alpha name can have on uptake of a release. In the IRC chat of 16th April [1] we reached a conclusion that given the f

Next release name? (was: Re: [DISCUSS] Next version - What should be in it)

2007-04-24 Thread ant elder
What are we going to be calling this next SCA release? We've had M1 and M2 releases, some alpha kernel releases, DAS are talking about an M3 release and SDO is doing an M3 release although there was some discussion about renaming that to beta1. I think milestone and alpha release names may discou

Re: Using Tuscany in a webapp, was: [DISCUSS] Next version - What should be in it

2007-04-23 Thread Simon Nash
I think the M2 arrangement for the construction of the WAR file was quite complex and hard to reproduce by non-maven users who didn't have the special plugin. I wrote some documentation for the web site in case anyone wanted to do this with M2 and it wasn't very easy, especially the Jave-serializ

Re: Using Tuscany in a webapp, was: [DISCUSS] Next version - What should be in it

2007-04-22 Thread Simon Laws
On 4/21/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: [snip] Luciano Resende wrote: > +1 on focusing on the stability and consumability for the core functions, > other then helping on simplifying the runtime further and work on a > Domain > concept, I also want to contribute around havin

Re: Lifecycle of runtime extensions, was: [DISCUSS] Next version - What should be in it

2007-04-21 Thread Simon Nash
The problem I have been working on is TUSCANY-1218. See the problem desription and the comments on my attached patch for more details of the problem and how my patch resolves it. I'm aware of the ModuleActivator.stop() method and I am using it in my patch for TUSCANY-1218. However, this isn't s

Using Tuscany in a webapp, was: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Jean-Sebastien Delfino
[snip] Luciano Resende wrote: +1 on focusing on the stability and consumability for the core functions, other then helping on simplifying the runtime further and work on a Domain concept, I also want to contribute around having a better integration with App Servers, basically start by bringing

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Jean-Sebastien Delfino
Simon Laws wrote: On 4/19/07, ant elder <[EMAIL PROTECTED]> wrote: On 4/19/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > Davanum Srinivas wrote: > > Folks, > > > > Let's keep the ball rolling...Can someone please come up with a master > > list of "extensions, bindings, services, sa

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Raymond Feng
. This way, I can learn more and get ready for the next time. Thanks, Raymond - Original Message - From: "Luciano Resende" <[EMAIL PROTECTED]> To: Sent: Friday, April 20, 2007 10:25 AM Subject: Re: [DISCUSS] Next version - What should be in it +1 on foc

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Simon Laws
> > - Original Message - > From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]> > To: > Sent: Wednesday, April 18, 2007 6:07 PM > Subject: Re: [DISCUSS] Next version - What should be in it > > > > Davanum Srinivas wrote: > >> Folks, >

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Luciano Resende
07 6:07 PM Subject: Re: [DISCUSS] Next version - What should be in it > Davanum Srinivas wrote: >> Folks, >> >> Let's keep the ball rolling...Can someone please come up with a master >> list of "extensions, bindings, services, samples" which can then help >

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Raymond Feng
to be the release manager? If not, I can give a try. Thanks, Raymond - Original Message - From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]> To: Sent: Wednesday, April 18, 2007 6:07 PM Subject: Re: [DISCUSS] Next version - What should be in it Davanum Sriniv

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread ant elder
On 4/19/07, Simon Laws <[EMAIL PROTECTED]> wrote: I'm not against adding new features for the release b.t.w Good point, me either. I hope my previous post didn't sound like I was against adding new features, all I was saying was that I think those other things are important to do and they're

Lifecycle of runtime extensions, was: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Jean-Sebastien Delfino
[snip] Simon Nash wrote: I agree with the comments from Ant and Simon on focusing on stability and consumability at the moment rather than adding a large amount of new function. I've been working on a complex bug fix recently (watch this space for a JIRA and patch) and I noticed that we lost som

Re: [DISCUSS] Next version - What should be in it

2007-04-20 Thread Simon Nash
I agree with the comments from Ant and Simon on focusing on stability and consumability at the moment rather than adding a large amount of new function. I've been working on a complex bug fix recently (watch this space for a JIRA and patch) and I noticed that we lost some previously working suppo

Re: [DISCUSS] Next version - What should be in it

2007-04-19 Thread Simon Laws
On 4/19/07, ant elder <[EMAIL PROTECTED]> wrote: On 4/19/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > Davanum Srinivas wrote: > > Folks, > > > > Let's keep the ball rolling...Can someone please come up with a master > > list of "extensions, bindings, services, samples" which can the

Re: [DISCUSS] Next version - What should be in it

2007-04-19 Thread ant elder
On 4/19/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: Davanum Srinivas wrote: > Folks, > > Let's keep the ball rolling...Can someone please come up with a master > list of "extensions, bindings, services, samples" which can then help > decide what's going to get into the next release. Pl

Re: [DISCUSS] Next version - What should be in it

2007-04-18 Thread Jean-Sebastien Delfino
Davanum Srinivas wrote: Folks, Let's keep the ball rolling...Can someone please come up with a master list of "extensions, bindings, services, samples" which can then help decide what's going to get into the next release. Please start a wiki page to document the master list. Once we are done doc

Re: [DISCUSS] Next version - What should be in it

2007-04-03 Thread Luciano Resende
ebastien Delfino" <[EMAIL PROTECTED]> To: Sent: Saturday, March 31, 2007 12:07 PM Subject: Re: [DISCUSS] Next version - What should be in it > Jean-Sebastien Delfino wrote: >> ant elder wrote: >>> On 3/30/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: >>&

Re: [DISCUSS] Next version - What should be in it

2007-04-02 Thread Raymond Feng
extensibility story for implementation/binding extensions Thanks, Raymond - Original Message - From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]> To: Sent: Saturday, March 31, 2007 12:07 PM Subject: Re: [DISCUSS] Next version - What should be in it Jean-Sebastien Del

Re: [DISCUSS] Next version - What should be in it

2007-04-01 Thread Jean-Sebastien Delfino
[snip] Jean-Sebastien Delfino wrote: ant elder wrote: I guess everything in contrib is not going to be in the next release unless something changes. How about also moving bpel, celtix and servicemix to contrib? Makes sense to me. I've not seen any activity in these modules recently, and the

Re: [DISCUSS] Next version - What should be in it

2007-03-31 Thread Jean-Sebastien Delfino
Jean-Sebastien Delfino wrote: ant elder wrote: On 3/30/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Folks, Let's keep the ball rolling...Can someone please come up with a master list of "extensions, bindings, services, samples" which can then help decide what's going to get into the next r

Re: [DISCUSS] Next version - What should be in it

2007-03-30 Thread Jean-Sebastien Delfino
ant elder wrote: On 3/30/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Folks, Let's keep the ball rolling...Can someone please come up with a master list of "extensions, bindings, services, samples" which can then help decide what's going to get into the next release. Please start a wiki pag

Re: [DISCUSS] Next version - What should be in it

2007-03-30 Thread ant elder
On 3/30/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Folks, Let's keep the ball rolling...Can someone please come up with a master list of "extensions, bindings, services, samples" which can then help decide what's going to get into the next release. Please start a wiki page to document the

[DISCUSS] Next version - What should be in it

2007-03-29 Thread Davanum Srinivas
Folks, Let's keep the ball rolling...Can someone please come up with a master list of "extensions, bindings, services, samples" which can then help decide what's going to get into the next release. Please start a wiki page to document the master list. Once we are done documenting the list. We can