Hi,
We had a discussion at the end of May about changing out release
process to release at the top level module only. I've just realised
this release vote was for sub-modules and that really we should have
done a full Blueprint release.
Christian, that was the intent wasn't it?
I guess next
Using the new approach the bundle and release versions are 'marketing
versions'. So it doesn't matter - except if we know users are doing
Require-Bundle, then moving to 1.5 would be preferable. Actually, I
think 1.5 would be the best number in the Blueprint case because there
isn't a major
Hi Jeremy,
yes it was the intent. It is quite some work to convert a submodule to
the new release process though. So I think the best approach is to
convert each module
at a certain point and do submodule releases from then on.
As long as a submodule is not converted I propose we continue
Well, there is also the issue of selecting the “version” to use.For
example, for this blueprint release, we have numbers like 1.3.1 and 1.1.1 and
1.4.4. Do we just up everything in blueprint to something like 1.5? Or do
we bite the bullet and just say that since we are flipping version
It would also seem, that we are going to have top level modules doing
either one of the release processes for some time.
I think it would be best, if we can get to a single release process -
but that may take some time. I think there are two things we should
vote on to make this concrete:
a)
Ok, that sounds fair. Subsystem is another one. Would you have a
chance to document how you approached converting the JPA module (ok so
I know you reimplemented at the same time :-) ... so that others can
use the same approach for other modules?
Jeremy
On 13 July 2015 at 14:04, Christian
This vote passes with 4 binding +1s.
I'll promote the artifacts
Thanks all
Sergey
On 29/06/15 16:56, Sergey Beryozkin wrote:
Hi All
This is a vote to support the release of blueprint-parser-1.3.1,
blueprint-noosgi-1.1.1, blueprint-web 1.1.1.
The staging repository for blueprint-parser-1.3.1
: Sergey Beryozkin sberyoz...@gmail.com
To: dev@aries.apache.org
Date: 06/30/2015 04:24 PM
Subject:Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1,
blueprint-web-1.1.1 releases
Building with -Pdev is OK now, sorry I did not update all the properties
immediately. As a side
Hi Sergey,
we might also look into trying to include the staging repository into
the poms when doing releases for several bundles.
I am not sure what downsides there may be but it could help
Christian
On 01.07.2015 15:15, Sergey Beryozkin wrote:
Hi Tom
I think it is onlt the 2nd time I'm
+1
David
On 29 June 2015 at 16:56, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi All
This is a vote to support the release of blueprint-parser-1.3.1,
blueprint-noosgi-1.1.1, blueprint-web 1.1.1.
The staging repository for blueprint-parser-1.3.1 is at
+1
Christian
On 29.06.2015 17:56, Sergey Beryozkin wrote:
Hi All
This is a vote to support the release of blueprint-parser-1.3.1,
blueprint-noosgi-1.1.1, blueprint-web 1.1.1.
The staging repository for blueprint-parser-1.3.1 is at
+1
Dan
On 29.06.2015 17:56, Sergey Beryozkin wrote:
Hi All
This is a vote to support the release of blueprint-parser-1.3.1,
blueprint-noosgi-1.1.1, blueprint-web 1.1.1.
The staging repository for blueprint-parser-1.3.1 is at
@aries.apache.org dev@aries.apache.org
Date: 06/30/2015 01:31 PM
Subject:Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1,
blueprint-web-1.1.1 releases
+1
David
On 29 June 2015 at 16:56, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi All
This is a vote to support the release
@aries.apache.org
Date: 06/30/2015 01:31 PM
Subject:Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1,
blueprint-web-1.1.1 releases
+1
David
On 29 June 2015 at 16:56, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi All
This is a vote to support the release of blueprint-parser
Hi All
This is a vote to support the release of blueprint-parser-1.3.1,
blueprint-noosgi-1.1.1, blueprint-web 1.1.1.
The staging repository for blueprint-parser-1.3.1 is at
https://repository.apache.org/content/repositories/orgapachearies-1027
The staging repository for
15 matches
Mail list logo
