search

jglobus / JGlobus

jGlobus is a collection of Java client libraries for Globus® Toolkit security, GRAM, and GridFTP.
http://www.globus.org/toolkit/jglobus/
Apache License 2.0
24 stars 44 forks source link

Tags and versions. #24

Closed ellert closed 11 years ago

ellert commented 12 years ago

Also when building code from a git tag, the version of the created jars is 2.0-SNAPSHOT. If I check out the 2.0.4 tag I expect the version of the jars to match the tag. The version 2.0-SNAPSHOT gives the impression that the jars were built form the git master.

It might be bad to change this for existing tags so long after the tags were created, but it is something to consider for the next tag.

bbockelm commented 12 years ago

Something to consider for next release, I think.

It feels like we're doing well in closing up old issues (1 pull request remains, and we still need to switch the hashing algorithm on RHEL6 and later), so I think the release is not too far away.

ghost commented 12 years ago

What is the next targeted version?

bbockelm commented 12 years ago

Hi Suresh,

I think the next targeted version is 2.0.5. There really aren't too many large new features, just scrubbing the source code. We've been fixing bugs, performance regressions, and simplifying the dependency chains. I don't think it's enough to bump to 2.1.x.

Brian

vijayanand commented 12 years ago

Hi Brian, The first important change was stability. If it is considered stable with test cases and removal of spring then we can change the version.

It also has to be release on maven central.

The next important change which had been a part of discussion for a pretty long time inside computation institute was moving to Bouncycastle Lightweight TLS . Currently we are using JAVA JSSE which has limitations. NCSA moved to bouncycastle sometime back and we would also like to move to that.

Best Regards, Vijay

bbockelm commented 12 years ago

Hi Vijay,

Is there a document describing how to perform a release? If not, could you write one?

We should make sure the release process is well-documented to avoid this problem in the future, verify that the release process is not tied to one person, and set up the base rules for "blessing" a release.

Brian

vijayanand commented 12 years ago

Hi Brian, There is none as of yet.

I will document the release process.

Best Regards, Vijay

bbockelm commented 11 years ago

Hi,

I did the 2.0.5-rc1 tag last week. Can you verify it was done correctly? I'm going to try to do the precisely same steps for the 2.0.5 final tag next week.

I don't particularly want to re-do old tags, but can follow the same procedure for future releases.

Brian

ellert commented 11 years ago

When building the 2.0.5-rc1 tag the versions of the jars are 2.0.5-rc1, and not 2.0-SNAPSHOT anymore like for the previous tags. So for me it works correctly.

I agree we do not have to fix the old tags.

ellert commented 11 years ago

Time to close.