[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5524?page=c...
]
Steve Ebersole commented on HHH-5524:
-------------------------------------
You are focusing on the specific time it would not be useful. What about when 3.6 goes
Final? Now granted our (en)forced usage of the Final qualifier makes this logic very
specific, but thats ok because this is a specific script.
But at any rate, given 3.6.0-SNAPSHOT you guess the versions as : 3.6.0.Final and
3.6.1-SNAPSHOT. Now the releaser has to enter 2 values, the same 2 values they have to
enter today as a matter of fact!
Now given 3.6.1-SNAPSHOT (so after 3.6.0.Final has actually been released) the guess would
be : 3.6.1.Final and 3.6.2-SNAPSHOT, *exactly* the values you would enter!
I said its a "nice to have", so if you don't have time or don't want to
do it then thats a different story and don't do it. But don't try to minimize its
usefulness.
Move tagRelease.sh into svn
---------------------------
Key: HHH-5524
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5524
Project: Hibernate Core
Issue Type: Task
Components: core
Reporter: Steve Ebersole
Assignee: Hardy Ferentschik
Fix For: 3.5.6, 3.6.0.CR1
http://community.jboss.org/wiki/HibernateRelease35wMaven includes a script to perform svn
tagging for releases. Lets:
# Move this into svn
# Add handling for scm urls
# (nice to have) Would really like to see it guess the versions to use, ala what the
Maven release plugin does
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira