Den 19.08.2011 09:04, skrev Barrie Treloar:
On Fri, Aug 19, 2011 at 4:01 PM, Kristian Rosenvold
<[email protected]> wrote:
I had a small discussion with Tamas on IRC yesterday about this, and I did
come to realize that the proper way to do this is to do a regular release of
maven-archiver 2.4.2, then make a branch in svn for maven-jar-plugin 2.3.2.
On the branch, update to maven-archiver 2.4.2 and then release from the
branch. In that way the build never breaks and CI does not need any staging
dependencies.
In retrospect I did the next-best thing, which was a temporary revert of the
upgrade on trunk. So I can procastinate/fear svn branches for a little
longer ;)
Whilst procrastination and fear are admirable attributes, doesn't
creating a branch mean you miss all the good stuff of CI?
And until you merge back to trunk your changes are not visible to others.
Good point. I suppose maybe updating jar-plugin trunk to use the
specific snapshot of the first maven-archiver-2.5-SNAPSHOT might be an
option, especially if a comment is added about why. It still does not CI
build the *exact* versions that are released, but it might be close
enough. The specific versions being released are, after all, being
tested for the vote (although I agree that's not entirely the same).
I can't speak with any authority on what we do, but in my personal
past I've had:
* trunk - keep latest changes here but dont break the build
* branches - something that is going to take a while to fix and/or is
a work in progress so stuff may be not thought out well enough to live
in trunk.
After some time with git you just start using branches for "anything you
feel like", and imposing that kind of constraint now seems strange. So I
bring that back to svn ;)
But I dont see which one of these two scenarios your problem resides,
i.e. you need a newer version of dependency that doesn't yet exist...
Can't you stick with the snapshot until the release passes and then
commit to the released version?
Because I want to save time. If I have to do both it takes me a week.
This way I can do both. And the vote is open, btw ;)
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
