Snapshots while a release is in progress
Hi all, first many thanks to Holly for organizing the Aries release. This is really a lot of work and she is doinga great job making it possible. Btw. I hope aries can switch to a simpler release concept soon but this is not what I wanted to discuss. I have a concern about the old snapshots when a release takes place. Currently the snapshots are removed from the apache snapshot repo as soon as a release is started. This means that dependent projects like karaf have to adapt all the time. So for each part of aries that is released we first have to switch to the next snapshot version as the release is not yet there and then to the release version. Even this effort only helps for local builds at the moment as the new snapshots do not seem to work through Jenkins. So each developer also has to build the aries trunk all the time. So basically this means that the karaf build on Jenkins is now red for 24 days. So to improve this I propose to keep the old snapshots for some months so dependent projects have some time to adapt to a new release or snapshot. What do you think? Is this possible? Christian -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: Snapshots while a release is in progress
On Mon, Jul 23, 2012 at 11:16 AM, Christian Schneider ch...@die-schneider.net wrote: Hi all, first many thanks to Holly for organizing the Aries release. This is really a lot of work and she is doinga great job making it possible. Btw. I hope aries can switch to a simpler release concept soon but this is not what I wanted to discuss. I know I keep saying it, but I do think once the 1.0.0 bundles are released, everything will be much easier. :) In particular, we'll have far fewer snapshot dependencies in our poms, so the case where we depend on an 'old' snapshot while a release is being voted through will be rarer. I have a concern about the old snapshots when a release takes place. Currently the snapshots are removed from the apache snapshot repo as soon as a release is started. This means that dependent projects like karaf have to adapt all the time. Oh dear. I *thought* from what Dan had said that the old snapshot wasn't removed until the release was actually promoted. Certainly I can see, for example, 1.0.0-SNAPSHOT of blueprint-core at https://repository.apache.org/content/groups/snapshots/org/apache/aries/blueprint/org.apache.aries.blueprint.core/1.0.0-SNAPSHOT/. However, if the karaf builds have been red for 24 days, that suggests this understanding is wrong. :) So for each part of aries that is released we first have to switch to the next snapshot version as the release is not yet there and then to the release version. Even this effort only helps for local builds at the moment as the new snapshots do not seem to work through Jenkins. So each developer also has to build the aries trunk all the time. So basically this means that the karaf build on Jenkins is now red for 24 days. I agree this is not at all ideal and needs to be fixed, in some way or another. I'll investigate and see if I can figure out what's going on with the awol snapshots. So to improve this I propose to keep the old snapshots for some months so dependent projects have some time to adapt to a new release or snapshot. What do you think? Is this possible? I think this is a Nexus configuration issue, and nothing to do with us directly. Maybe Dan Kulp knows more? Holly Christian -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: Snapshots while a release is in progress
Following up to myself, I've just cleaned my local repo and built blueprint, and I see output like: Downloading: http://repository.apache.org/snapshots/org/apache/aries/blueprint/org.apache.aries.blueprint.core/1.0.0-SNAPSHOT/org.apache.aries.blueprint.core-1.0.0-20120719.033239-39.jar Downloaded: http://repository.apache.org/snapshots/org/apache/aries/blueprint/org.apache.aries.blueprint.core/1.0.0-SNAPSHOT/org.apache.aries.blueprint.core-1.0.0-20120719.033239-39.jar(374 KB at 124.9 KB/sec) So I think the snapshots are still there in the repo, and perhaps it's a maven or Jenkins config thing? Still something that needs to be fixed, of course ... Holly On Mon, Jul 23, 2012 at 12:53 PM, Holly Cummins holly.k.cumm...@googlemail.com wrote: On Mon, Jul 23, 2012 at 11:16 AM, Christian Schneider ch...@die-schneider.net wrote: Hi all, first many thanks to Holly for organizing the Aries release. This is really a lot of work and she is doinga great job making it possible. Btw. I hope aries can switch to a simpler release concept soon but this is not what I wanted to discuss. I know I keep saying it, but I do think once the 1.0.0 bundles are released, everything will be much easier. :) In particular, we'll have far fewer snapshot dependencies in our poms, so the case where we depend on an 'old' snapshot while a release is being voted through will be rarer. I have a concern about the old snapshots when a release takes place. Currently the snapshots are removed from the apache snapshot repo as soon as a release is started. This means that dependent projects like karaf have to adapt all the time. Oh dear. I *thought* from what Dan had said that the old snapshot wasn't removed until the release was actually promoted. Certainly I can see, for example, 1.0.0-SNAPSHOT of blueprint-core at https://repository.apache.org/content/groups/snapshots/org/apache/aries/blueprint/org.apache.aries.blueprint.core/1.0.0-SNAPSHOT/. However, if the karaf builds have been red for 24 days, that suggests this understanding is wrong. :) So for each part of aries that is released we first have to switch to the next snapshot version as the release is not yet there and then to the release version. Even this effort only helps for local builds at the moment as the new snapshots do not seem to work through Jenkins. So each developer also has to build the aries trunk all the time. So basically this means that the karaf build on Jenkins is now red for 24 days. I agree this is not at all ideal and needs to be fixed, in some way or another. I'll investigate and see if I can figure out what's going on with the awol snapshots. So to improve this I propose to keep the old snapshots for some months so dependent projects have some time to adapt to a new release or snapshot. What do you think? Is this possible? I think this is a Nexus configuration issue, and nothing to do with us directly. Maybe Dan Kulp knows more? Holly Christian -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
