Usually, users would use a range, so it should not matter that much I think. I've used the pom.version for 3.1.0, which an be change afterward if we want to keep at 3.1.0 for the package version for future releases.
On Tue, Jun 15, 2010 at 13:15, Felix Meschberger <[email protected]> wrote: > Hi, > > On 15.06.2010 12:58, Guillaume Nodet wrote: > > Wow, I was expecting the package to be derived from the project version. > > No, because I don't want to increase the export version on each bundle > release. The downside is, that it must not be forgotten to be increased > when there is some change in the API. > > Regards > Felix > > > I'll fix that now. > > > > Cancelling this release again. ... > > > > On Tue, Jun 15, 2010 at 12:46, Felix Meschberger <[email protected]> > wrote: > > > >> Hi, > >> > >> On 15.06.2010 11:47, Guillaume Nodet wrote: > >>> I would like to call a new vote on the following subproject releases: > >>> > >>> webconsole 3.1.0 > >> > >> Still exports web console API 3.0 ... > >> > >> Regards > >> Felix > >> > >>> bundlerepository 1.6.4 > >>> karaf 1.6.2 > >>> > >>> Staging repository: > >>> https://repository.apache.org/content/repositories/orgapachefelix-053/ > >>> > >>> You can use this UNIX script to download the release and verify the > >>> signatures: > >>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > >>> > >>> Usage: > >>> sh check_staged_release.sh 053 /tmp/felix-staging > >>> > >>> Please vote to approve this release: > >>> > >>> [ ] +1 Approve the release > >>> [ ] -1 There's a problem (please provide specific comments) > >>> > >> > > > > > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
