tagging Re: openjdk build pages

David Katleman david.katleman at oracle.com
Fri May 23 22:20:13 UTC 2014


Slight rename/fork, since Martin & Kelly's suggestion a bit off topic of 
the original thread.

On 5/23/2014 1:55 PM, Martin Buchholz wrote:
>
> On Fri, May 23, 2014 at 9:07 AM, Kelly O'Hair <kellyohair at gmail.com 
> <mailto:kellyohair at gmail.com>> wrote:
>
>
>     On May 23, 2014, at 1:59 AM, dalibor topic wrote:
>
>     > The problem with moving tags is that what you get when you clone
>     a repository with a tag depends on when you cloned it.
>
>     That's always true when you request a clone without a tag, you
>     never know what you will get.
>
>     With a jdk7u40 tag, if it was released, it's stable, but if it
>     isn't you get the latest jdk7u40, which should be a stable release.
>      I don't see a problem with that.
>
>
> To amplify Kelly's point, there are already (pseudo-)tags that move 
> over time, e.g. "tip" and the endearingly named "qtip"

I agree that such a pseudo tag that always represents the latest of say 
jdk7u60 would be useful and you're right, no one knows which build is 
GA, until after GA actually occurs, so we could add a pair of tags 
jdk7u60 & jdk7u60-bXX for each promoted build. Simplifies things once 
jdk7u60 is released, and serves as a latest tag while 7u60 is under 
development.

Might want to make it bit more obvious than just "jdk7u60", like 
"jdk7u60-current" or "jdk7u60-latest"

         Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/web-discuss/attachments/20140523/ea17ed2b/attachment.html>


More information about the web-discuss mailing list