Yep - the Felix release process outlines this deployment of a snapshot
just before doing the actual release. I think it would make sense for
Aries to follow that too:
http://felix.apache.org/documentation/development/release-management-nexus.html

David

On 30 June 2014 22:27, Daniel Kulp <[email protected]> wrote:
>
> The normal process would be to immediately upon building the “release”, do a 
> deploy of the new snapshot version and update everything that references the 
> old snapshot to the new snapshot.  Thus, things would continue to build.
>
> Dan
>
>
> On Jun 30, 2014, at 4:51 PM, Jeremy Hughes <[email protected]> wrote:
>
>> After the release candidate artifacts are posted, module poms have their
>> version bumped up. So parent is now 2.0.1-SNAPSHOT. Modules that are being
>> released at the same time were depending on 2.0.0-SNAPSHOT and moved to
>> depend on 2.0.0 as part of their own release process. Which is fine for
>> reviewing the release artifacts of all those modules together. However, the
>> part of the release process that bumps a module's version in trunk
>> subsequent to the tagging, doesn't bump the dependency versions. They
>> shouldn't: a) there's no reason to depend on snapshot b) it doesn't know
>> the module it depends on is being released at the same time and therefore
>> isn't available in a repository.
>>
>> Our process for releasing modules together that have dependencies between
>> them, is causing the trunk build to be broken while the release vote is
>> ongoing. I'm not sure what other multi-module projects do and why we're
>> different, but surely they don't all suffer from this.
>>
>> Any ideas?
>>
>>
>> On 30 June 2014 19:53, Thomas Watson <[email protected]> wrote:
>>
>>> I'm new here and this may be obvious to others.  While we are in release
>>> mode, is it expected that trunk will no longer build due to references to
>>> the unreleased 2.0.0 parent pom?  Is there a good process to follow in
>>> order to be able to build everything locally while doing other work that is
>>> not in the middle of being released?
>>>
>>> Tom
>>>
>>>
>>>
>>> [image: Inactive hide details for Guillaume Nodet ---06/30/2014 01:10:56
>>> PM---This is the first release of a set. It contains the paren]Guillaume
>>> Nodet ---06/30/2014 01:10:56 PM---This is the first release of a set. It
>>> contains the parent pom in version 2.0.0
>>>
>>> From: Guillaume Nodet <[email protected]>
>>> To: [email protected]
>>> Date: 06/30/2014 01:10 PM
>>> Subject: [VOTE] Release Apache Aries Parent 2.0.0
>>> ------------------------------
>>>
>>>
>>>
>>> This is the first release of a set.
>>> It contains the parent pom in version 2.0.0
>>>
>>> Staging repository available at
>>> https://repository.apache.org/content/repositories/orgapachearies-1002
>>>
>>> [ ] +1 Release parent 2.0.0
>>> [ ] -1 Do not
>>>
>>> Cheers,
>>> Guillaume Nodet
>>>
>>>
>
> --
> Daniel Kulp
> [email protected] - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>

Reply via email to