Regarding releasing Commons bundles, I share Marcel's concern that we
need to have a controlled release process so that we can have some sort
of quality assurance about what we are releasing.
However, I do agree with Carsten that it makes sense to separate Commons
off from the other sub-projects, since they really are independent and
it will help lessen the load on Karl and avoid a bottleneck situation.
We just need to create a new "Commons Release Manager" position. :-)
Regarding Alin's comments about the gap between posting a wrapper POM
file and it getting released, this is sort of off the mark. Karl is not
in charge of that...actually, no one is. Karl is in charge of official
releases, we don't have any official releases for Commons bundles yet,
that is what is being proposed here.
So, what it seems, is that Carsten is willing to help out on both counts
and that sounds great to me.
I know that Karl will be checking his email while on vacation, so we can
see if he agrees.
-> richard
original message:
-----------------------------
Hi,
I updated our commons project, main changes are:
- parent pom is now in "pom" (similar to our root pom)
- convenience pom under /commons to build the whole tree
- Only released artifacts are used (maven-bundle-plugin:1.0.0,
root-pom:1.0.0)
- information for the mvn release/gpg plugin to use mvn for release
(If this works out, we can add this info to the felix root pom later
on - adding it now would require to re-release the root pom in order to
be able to release the commons pom)
- changed the artifactid for the commons pom from "build" to
"commons-build" (more unique name)
- all versions are 1.0.0-SNAPSHOT
With these changes I would like to release the commons parent pom,
followed by the bundles and then call a vote on all these artifacts.
If noone objects (lazy consensus...) I'll go ahead in the next days.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
