On 17 July 2013 17:00, Emmanuel Lécharny <elecha...@gmail.com> wrote: > Le 7/17/13 5:53 PM, sebb a écrit : >> On 17 July 2013 15:19, Emmanuel Lécharny <elecha...@gmail.com> wrote: >>> Le 7/17/13 3:00 PM, sebb a écrit : >>>> On 17 July 2013 13:26, Emmanuel Lécharny <elecha...@gmail.com> wrote: >>>>> Le 7/17/13 2:21 PM, sebb a écrit : >>>>>> On 17 July 2013 10:56, <elecha...@apache.org> wrote: >>>>>>> Updated Branches: >>>>>>> refs/heads/trunk 0d04eba45 -> 84b2003fc >>>>>>> >>>>>>> >>>>>>> Revert "[maven-release-plugin] prepare for next development iteration" >>>>>>> >>>>>>> This reverts commit 0d04eba4525ca85886c4a03acc20b444ff69a52d. >>>>>> However trunk is now in an incorrect state, as all the versions are >>>>>> missing the -SNAPSHOT suffix. >>>>> The trunk will be fix when the perform will be done. (Actually, it >>>>> should be the case). >>>> But meanwhile any builds (including CI builds) will be using the >>>> non-SNAPSHOT version. >>>> Not ideal. >>> Yep. The plugin should rather create a branch, instead of committing in >>> trunk... >> No, it does not need to do that - at least not with SVN. >> >> With SVN the way I do it is: > We don't use SVN anymore.
I realise that. Maybe Git offers functionality that would allow a similar approach which achieves the same goals: - don't leave trunk in a temporary state even for a short period - make respins easier - don't update trunk until actually ready to move to the next development version > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com >
