On Wed, Aug 20, 2008 at 10:59 AM, Alex Boisvert <[EMAIL PROTECTED]> wrote: > On Wed, Aug 20, 2008 at 10:51 AM, lacton <[EMAIL PROTECTED]>wrote: > >> On Tue, Aug 19, 2008 at 11:42 PM, Alex Boisvert <[EMAIL PROTECTED]> >> wrote: >> > I agree with you, it's confusing. I would prefer to have: >> > >> > VERSION_NUMBER = '1.1.0-SNAPSHOT' >> > # No more NEXT_VERSION >> > >> > and do a release, the tag would be 1.1.0, released artifacts would be >> 1.1.0 >> > and after the release the new versions would be: >> > >> > VERSION_NUMBER = '1.1.1-SNAPSHOT' >> > >> > and if you want to change the next version number, edit the file and >> commit. >> >> And what do you think of interactively asking the user the new version >> after tagging the release? > > > Currently the release task is assumed to be non-interactive for build > automation. It is possible to reliably detect whether we have an > interactive terminal? JRuby?
My only concern, you get two different behaviors depending on how you run the task: buildr release => prompt to update version number buildr release | more => not Assaf > > alex >
