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 doing
releases in the per bundle style. So we have a smooth transition and do
not hold off releases.
Christian
On 13.07.2015 14:37, Jeremy Hughes wrote:
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 time :-)
Cheers,
Jeremy
On 2 July 2015 at 21:46, Sergey Beryozkin <[email protected]> wrote:
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 is at
https://repository.apache.org/content/repositories/orgapachearies-1027
The staging repository for blueprint-noosgi-1.1.1 and
blueprint-web-1.1.1 is at
https://repository.apache.org/content/repositories/orgapachearies-1028
The following issues have been addressed:
https://issues.apache.org/jira/browse/ARIES-1322
https://issues.apache.org/jira/browse/ARIES-1323
https://issues.apache.org/jira/browse/ARIES-1334
A servlet-based deployment of Blueprint contexts with custom namespace
handlers will work better in non OSGI environments after the release.
The vote is open for the next 72 hours, here is my +1,
Thanks, Sergey
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
