openjdk build pages

[Kelly O'Hair]

I agree with Martin. Always wondered why we never did this.

In fact, when the jdkNuNN-bNN tag is created, just create a jdkNuNN tag at the same time, all the time.
That way it would refer to the latest build of an update. It would move from update to update, then get locked down on the last one.

-kto


On May 22, 2014, at 8:48 AM, Martin Buchholz wrote:

> 
> 
> 
> On Thu, May 22, 2014 at 8:22 AM, dalibor topic <dalibor.topic at oracle.com> wrote:
> Once an update release is released, cloning its forest will give you the OpenJDK source code for the release, as the forests are sealed once a release has been published. So there is no need for an explicit GA tag, etc for such releases - just cloning without any tags will do the job.
> 
> 
> While you are right, this feels like more of a workaround than a reason not to create these "GA" tags.  In any revision control system with labels, creating labels for actual releases is the single most natural and obvious thing to do.
> 
> Also, you don't need the actual 7u40 forest.  If you happen to have a jdk7u forest, you can do
> hg tupdate -r jdk7u40-b62
> 
> Why not allow
> hg tupdate -r jdk7u40
> 
> 

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