+1
Whew! One down clement, two more to go...
I think we need to investigate if there is a simpler way to release
iPOJO in the future. It is a lot of work for both Clement to create the
release and for us to verify it. Clearly, the current process is not
geared toward highly modular systems with lots of artifacts.
-> richard
Clement Escoffier wrote:
Hi all,
I finally cut the third release of the iPOJO framework.
It's a two-step release. To avoid releasing too much artifacts at the
same time, I call a vote only for the core of the iPOJO framework (so
7 artifacts).
(external handlers and composite) will be release after those ones).
The RC are available here:
http://people.apache.org/~clement/releases/org/apache/felix/org.apache.felix.ipojo.metadata/
http://people.apache.org/~clement/releases/org/apache/felix/org.apache.felix.ipojo.manipulator/
http://people.apache.org/~clement/releases/org/apache/felix/org.apache.felix.ipojo.ant/
http://people.apache.org/~clement/releases/org/apache/felix/maven-ipojo-plugin/
http://people.apache.org/~clement/releases/org/apache/felix/org.apache.felix.ipojo/
http://people.apache.org/~clement/releases/org/apache/felix/org.apache.felix.ipojo.arch/
http://people.apache.org/~clement/releases/org/apache/felix/org.apache.felix.ipojo.annotations/
The KEYS for verifying the signature is also in the directories, the
MD5 and SHA1 files are maven generated (and beautified).
So please check the releases and cast your votes - the vote will be
open until the end of the week (as there are several artifacts):
[ ] +1 release all
[ ] 0 don't care
[ ] -1 do NOT release, because ....
Thanks and Regards
Clement
