You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "lacton (JIRA)" <ji...@apache.org> on 2008/08/30 17:19:44 UTC
[jira] Created: (BUILDR-141) Release task is confusing
Release task is confusing
-------------------------
Key: BUILDR-141
URL: https://issues.apache.org/jira/browse/BUILDR-141
Project: Buildr
Issue Type: Improvement
Components: Core features
Reporter: lacton
Priority: Minor
VERSION_NUMBER = '1.1.0-SNAPSHOT'
NEXT_VERSION = '1.2.0'
seems to mean I am currently developing the 1.1.0 version, and when I'm done, I will tag this as a 1.1.0 release and start working on
the 1.2.0. Yet, when I call the release task, I get a tag called '1.2.0', not '1.1.0'.
Alex Boisvert suggests an improvement.
<quote>
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.
</quote>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-141) Release task is confusing
Posted by "lacton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lacton resolved BUILDR-141.
---------------------------
Resolution: Fixed
Fix Version/s: 1.3.3
$ svn ci
Sending CHANGELOG
Sending lib/buildr/core/build.rb
Sending spec/build_spec.rb
Transmitting file data ...
Committed revision 690727.
> Release task is confusing
> -------------------------
>
> Key: BUILDR-141
> URL: https://issues.apache.org/jira/browse/BUILDR-141
> Project: Buildr
> Issue Type: Improvement
> Components: Core features
> Reporter: lacton
> Priority: Minor
> Fix For: 1.3.3
>
>
> VERSION_NUMBER = '1.1.0-SNAPSHOT'
> NEXT_VERSION = '1.2.0'
> seems to mean I am currently developing the 1.1.0 version, and when I'm done, I will tag this as a 1.1.0 release and start working on
> the 1.2.0. Yet, when I call the release task, I get a tag called '1.2.0', not '1.1.0'.
> Alex Boisvert suggests an improvement.
> <quote>
> 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.
> </quote>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.