No more inputs for now, I'll just redo the release according to Felix's
comments.
-arjun
On 01/17/2012 01:26 PM, Felix Meschberger wrote:
Hi
Am 17.01.2012 um 13:07 schrieb Arjun Panday:
Thanks Felix,
I'll try what you said (can't have too much practice with the release
process anyway!)
Just a couple of questions:
- can I keep the same version (since nothing has been released) or
should I increase the version (i'm a bit afraid my first release might
end up being version 12.6!)
There's a dispute on that. I think the resolution here was, do as you please. I
prefer not reusing version numbers of failed releases (version numbers are
cheap, as long as you maintain semantic versioning).
- if I keep 0.1.0 will it be a problem when I run "mvn deploy" again?
will it override the existing contents? (or is there a way to undeploy?)
You will have to remove the SVN tag anyways when failing a release.
- when you say "the DEPENDENCIES and LICENSE files are not ok", is there
something I should change or just updating the release structure should do?
The current source package contains the subprojects. As such the DEPENDENCIES,
NOTICE and LICENSE files would have to be merged from the subproject to the
root (reactor/parent) project.
Since you change that and will only release the (new) parent and the core
project, there is nothing more to be done, I would think.
Regards
Felix
I'll wait a bit before closing the vote in case there's more inputs on
what needs to be changed.
Thanks for the help.
-arjun
On 01/17/2012 12:12 PM, Felix Meschberger wrote:
Hi
Am 17.01.2012 um 11:58 schrieb Arjun Panday:
Good point,
felix/servicediagnostics/0.1.0/
should contain only the parent pom
while
felix/org.apache.felix.servicediagnostics.plugin/0.1.0/
should contain the actual plugin bundle along with the sources
Yet I have no clue why it ended up like this and what I could do to
control this..
It looks like ran the release process from the ractor pom level and that the lower
"core" level has not been executing the apache-release profile (which is why
the source release of that project is missing).
The source release package actually contains the complete servicediagnostics
folder including the core and sample, but the DEPENDENCIES and LICENSE files
are not ok.
Does it mean I must differentiate the parent vs reactor roles by
creating a specific parent pom in a new directory?
Yes, in my experience splitting the roles (having distinct parent and reactor
poms) makes lives easier.
I would propose the following :
* Cancel this vote
* Split parent POM functionality from reactor functionality
* Run release on the parent pom
* Run release on core
* close the repository
* start a new vote
Other input ?
Regards
Felix
-arjun
On 01/17/2012 11:36 AM, Felix Meschberger wrote:
Hi,
This looks basically ok.
But I am a bit worried about the directory structure:
* ..../org/apache/felix/servicediagnostics/0.1.0/
this contains the source release zips and a related POM
* ..../org/apache/felix/org.apache.felix.servicediagnostics.plugin/0.1.0/
contains the bundle and a related POM
Is this ok or wouldn't we rather want to have everything in a single location
(I prefer the second over the first) ?
Other than that it looks ok.
Regards
Felix
Am 16.01.2012 um 21:45 schrieb Arjun Panday:
Hi everyone,
It did take me a while but I finally went through my first release. At
least up to this vote!
Here's the staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-080/
I'd be surprised if there wasn't anything wrong so let me know :)
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 080 /tmp/felix-staging
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks,
-arjun
