Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Matthias Wessendorf
I agree with you. +1 on a new release. Minor things: -after the release, I feel we should not continue to use the 1.0.0-SNAPSHOT version number Do you agree ? -Matthias On Wed, Jan 20, 2010 at 7:48 PM, Gurkan Erdogdu gurkanerdo...@yahoo.com wrote: Hi folks, It has been lots of corrections

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Gurkan Erdogdu
I feel we should not continue to use the 1.0.0-SNAPSHOT version number Do you agree ? * In released artifacts we will use 1.0.0-M4. * After releasing M4, we still to continue to use 1.0.0-SNAPSHOT. We have not reached our 1.0.0 release yet. We will be there after M5. After releasing 1.0.0, I

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Matthias Wessendorf
2010/1/21 Gurkan Erdogdu cgurkanerdo...@gmail.com: I feel we should not continue to use the 1.0.0-SNAPSHOT version number Do you agree ? * In released artifacts we  will use 1.0.0-M4. * After releasing M4, we still to continue  to use 1.0.0-SNAPSHOT. We have not reached our 1.0.0 release yet.

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Mark Struberg
I'm not sure if we need a M5. Current code quality is already pretty fine and 1.0.0 from my understanding would mean being feature complete and (almost) passing the TCK. I would then go on and quarterly release 1.0.1, 1.0.2 as bugfix versions. So I'd say we should stick to 1.0.0-SNAPSHOT

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Gurkan Erdogdu
what about 1.0.0-M5-SNAPSHOT ? That makes it at least a little bit more obvious where the current direction is, IMO Yes, it is so reasonable. Actually M5 contains 2 bullets that we can move them to 1.0.0 release. But as a common pattern with old releases, I want to releas e artifacts as 1.0.0-M5

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Gurkan Erdogdu
As I and Matthias said, there will be no M5. After releasing (1.0.0-M4), the next release will be 1.0.0. Matthias, I think it is reasonable to remove M5 from release. Just stick with M4 and after that we can go ahead and release 1.0.0. Therefore, next release will be 1.0.0-M4 and then final

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Matthias Wessendorf
2010/1/21 Gurkan Erdogdu cgurkanerdo...@gmail.com: what about 1.0.0-M5-SNAPSHOT ? That makes it at least a little bit more obvious where the current direction is, IMO Yes, it is so reasonable. Actually M5 contains 2 bullets that we can move them to 1.0.0 release. nice, sounds good. But as a

Re: [DISCUSSION] Releasing M4

2010-01-21 Thread Matthias Wessendorf
2010/1/21 Gurkan Erdogdu cgurkanerdo...@gmail.com: As I and Matthias said, there will be no M5. After releasing (1.0.0-M4), the next release will be 1.0.0. +1 TCK work is looking very good, so 1.0.0 is a reasonable target for the release after M4. Matthias, I think it is reasonable to remove

Re: Questions on using OWB to implement JSR 299 and JSR 330 for another app server

2010-01-21 Thread David Ezzio
Hi Gurkan, Thank you for your detailed response. It was very helpful. Thanks again, David Gurkan Erdogdu wrote: Hi David; Answers are detailed under each of your question. Thanks; --Gurkan From: David Ezzio dez...@apache.org To:

Re: Interceptor API changes

2010-01-21 Thread Mark Struberg
Thank you David! Btw, Pete yesterday released the CDI TCK. I will update the TCK package to this version. LieGrue, strub --- On Thu, 1/21/10, David Blevins david.blev...@visi.com wrote: From: David Blevins david.blev...@visi.com Subject: Re: Interceptor API changes To: