Re: targetting CDI-1.1 in trunk

2014-01-27 Thread Romain Manni-Bucau
+1 on the major for each spec version (like tomcat) is fine for me and
avoid confusion with technical changes for the spec targeted spec
version (1.1, 1.2 owb versions for instance)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau



2014-01-27 Mark Struberg strub...@yahoo.de:
 Depends on the arguments. Both has pros and cons.
 If we do an api incompatible change, then classically you push the major 
 version nr according the semantic versioning rules.

 We might not often use the minor version number as we did in owb 1.0.x, 1.1.x 
 and 1.2.x. But sometimes there is a need for this.


 LieGrue,
 strub




 On Monday, 27 January 2014, 8:49, Arne Limburg 
 arne.limb...@openknowledge.de wrote:

 +1 for that


But we should discuss the version of trunk. I remember that we discussed that 
in november, too. Did we come to a conclusion?
My opinion is to give version 1.3 to trunk and let openwebbeans 2.0 implement 
CDI 2.0.


Regards,
Arne


Von: Mark Struberg strub...@yahoo.de
Antworten an: u...@openwebbeans.apache.org u...@openwebbeans.apache.org, 
Mark Struberg strub...@yahoo.de
Datum: Sonntag, 26. Januar 2014 15:11
An: openwebbeans-dev dev@openwebbeans.apache.org, openwebbeans-user 
u...@openwebbeans.apache.org
Betreff: targetting CDI-1.1 in trunk



Hi folks!

We did discuss the question where to fully implement cdi-1.1 back in November 
already.
I believe it's finally time to do it. We finally need to move this forward.

I suggest we move the current trunk to an owb_1.2.x branch and move our trunk 
to target the new CDI-1.1 MR release (as discussed in November already).
Then I'll go on and cut an owb-1.2.2 release from the branch.

LieGrue,
strub









Re: targetting CDI-1.1 in trunk

2014-01-26 Thread Eric Covener
 I suggest we move the current trunk to an owb_1.2.x branch and move our
 trunk to target the new CDI-1.1 MR release (as discussed in November
 already).
 Then I'll go on and cut an owb-1.2.2 release from the branch.

+1


Re: targetting CDI-1.1 in trunk

2014-01-26 Thread Romain Manni-Bucau
+1 while the 1.2.2 is not forgotten, thanks Mark!
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau



2014-01-26 Eric Covener cove...@gmail.com:
 I suggest we move the current trunk to an owb_1.2.x branch and move our
 trunk to target the new CDI-1.1 MR release (as discussed in November
 already).
 Then I'll go on and cut an owb-1.2.2 release from the branch.

 +1


Re: targetting CDI-1.1 in trunk

2014-01-26 Thread Arne Limburg
+1 for that

But we should discuss the version of trunk. I remember that we discussed that 
in november, too. Did we come to a conclusion?
My opinion is to give version 1.3 to trunk and let openwebbeans 2.0 implement 
CDI 2.0.

Regards,
Arne

Von: Mark Struberg strub...@yahoo.demailto:strub...@yahoo.de
Antworten an: 
u...@openwebbeans.apache.orgmailto:u...@openwebbeans.apache.org 
u...@openwebbeans.apache.orgmailto:u...@openwebbeans.apache.org, Mark 
Struberg strub...@yahoo.demailto:strub...@yahoo.de
Datum: Sonntag, 26. Januar 2014 15:11
An: openwebbeans-dev 
dev@openwebbeans.apache.orgmailto:dev@openwebbeans.apache.org, 
openwebbeans-user 
u...@openwebbeans.apache.orgmailto:u...@openwebbeans.apache.org
Betreff: targetting CDI-1.1 in trunk

Hi folks!

We did discuss the question where to fully implement cdi-1.1 back in November 
already.
I believe it's finally time to do it. We finally need to move this forward.

I suggest we move the current trunk to an owb_1.2.x branch and move our trunk 
to target the new CDI-1.1 MR release (as discussed in November already).
Then I'll go on and cut an owb-1.2.2 release from the branch.

LieGrue,
strub
https://svn.apache.org/repos/asf/openwebbeans/branches/owb_1.1.x/




Re: targetting CDI-1.1 in trunk

2014-01-26 Thread Mark Struberg
Depends on the arguments. Both has pros and cons.
If we do an api incompatible change, then classically you push the major 
version nr according the semantic versioning rules. 

We might not often use the minor version number as we did in owb 1.0.x, 1.1.x 
and 1.2.x. But sometimes there is a need for this.


LieGrue,
strub




On Monday, 27 January 2014, 8:49, Arne Limburg arne.limb...@openknowledge.de 
wrote:
 
+1 for that


But we should discuss the version of trunk. I remember that we discussed that 
in november, too. Did we come to a conclusion?
My opinion is to give version 1.3 to trunk and let openwebbeans 2.0 implement 
CDI 2.0.


Regards,
ArneĀ 


Von: Mark Struberg strub...@yahoo.de
Antworten an: u...@openwebbeans.apache.org u...@openwebbeans.apache.org, 
Mark Struberg strub...@yahoo.de
Datum: Sonntag, 26. Januar 2014 15:11
An: openwebbeans-dev dev@openwebbeans.apache.org, openwebbeans-user 
u...@openwebbeans.apache.org
Betreff: targetting CDI-1.1 in trunk



Hi folks!

We did discuss the question where to fully implement cdi-1.1 back in November 
already.
I believe it's finally time to do it. We finally need to move this forward.

I suggest we move the current trunk to an owb_1.2.x branch and move our trunk 
to target the new CDI-1.1 MR release (as discussed in November already). 
Then I'll go on and cut an owb-1.2.2 release from the branch.

LieGrue,
strub