JDK 7 build 27 is available at the openjdk.java.net website

[Rob Ross]

Yes this helps.

So it turns out this process is similar to other SCM processes after  
all. The "top" level represents the latest (in this case pre-vetted)  
changes, but tagged changesets (repositories?) actually represent  
stable/milestone builds.


Rob Ross, Lead Software Engineer
E! Networks

---------------------------------------------------
"Beware of he who would deny you access to information, for in his  
heart he dreams himself your master." -- Commissioner Pravin Lal



On May 23, 2008, at 12:10 PM, Kelly O'Hair wrote:

> The most stable sources (changesets) will be those tagged by Xiomara
> and that represent the promoted build.
>
> As various teams push changesets into the master area jdk7/jdk7
> (http://hg.openjdk.java.net/jdk7/jdk7) these changesets should be
> solid but they have not gone through the release engineering build
> promotion process like the promoted build changesets.
> Also, because of the timing of the pushes, it's rare but possible that
> doing a forest pull from all the jdk7/jdk7 forest could get
> some but not all of the changesets a team may have pushed into this
> forest. Like I said, this is an extremely rare event.
>
> Pushes of changesets into the jdk7/jdk7 forest only happens a few
> times a day, based on integration slots listed here:
>   http://openjdk.java.net/projects/jdk7/builds/
> These time slots are dedicated to the team doing the integration,
> allowing them reserved access to the jdk7/jdk7 forest for  
> uninterrupted
> pulls, merges, and the pushes.
>
> Hope this helps.
>
> -kto
>
> Rob Ross wrote:
>> Sorry to ask again, but I'm trying to learn how this works :)
>> I had read through the archives regarding the repository process  
>> flow, and know there are several levels with gatekeeper  
>> repositories before the "master" repository, which I thought was  
>> at jdk7/jdk. I also thought that code does not get checked into  
>> this repository until it's gone through several gatekeeper  
>> repositories and been tested, reviewed, etc. So things would only  
>> get checked into master in well defined circumstances.
>> If my understanding of the above is not correct than what follows  
>> is also not correct. I understand about creating a changeset tag  
>> to be able to recreate that code in that moment in time, but I  
>> didn't understand where Xiomara said
>> "There is no difference in the code at this point.  Once  
>> integrations start to flow into the master repositories then the  
>> two below will defer, hence the reason to include the change set  
>> rev for this particular build number."
>> Wouldn't any changes that flow into the master repositories be  
>> based on code originally part of this tag, that had been tested,  
>> modified if necessary, and eventually approved? So any such  
>> changes in the master would be (excluding regressions) a positive  
>> development?
>> This is the opposite of how other SCM systems work, where the head/ 
>> top is usually in an unstable state due to active checkins, and  
>> you want to pull a stable release tag that has been created to  
>> mark a milestone during development - is this correct?
>> Rob Ross, Lead Software Engineer
>> E! Networks
>> ---------------------------------------------------
>> "Beware of he who would deny you access to information, for in his  
>> heart he dreams himself your master." -- Commissioner Pravin Lal
>> On May 23, 2008, at 10:05 AM, Kelly O'Hair wrote:
>>>
>>>
>>> Kelly O'Hair wrote:
>>>> http://hg.openjdk.java.net/jdk7/jdk7  is the root of the repository
>>>> forest, but you can only see the top repository.
>>>> Using:
>>>>    hg fclone http://hg.openjdk.java.net/jdk7/jdk7 yourjdk7
>>>> would get you the entire forest.
>>>> http://hg.openjdk.java.net/jdk7/jdk7/rev/56652b46f328  is a  
>>>> reference to
>>>> a specific changeset in the top level repository. And this  
>>>> changeset
>>>> is the one that Xiomara created to define the jdk7-b27 tag so we
>>>> have a permanent record of what changesets were in jdk7 build 27.
>>>> Each repository in the forest will have a similar changeset,  
>>>> which just
>>>> creates this jdk7-b27 tag.
>>>> Using this jdk7-b27 tag, you could
>>>>      hg fclone -R jdk7-b27 http://hg.openjdk.java.net/jdk7/jdk7
>>>                  ^^
>>>                  -r
>>> oops.
>>>
>>> -kto
>>>
>>>> yourjdk7-b27
>>>> if you wanted to get the repository forest and the exact state  
>>>> of the sources
>>>> when Xiomara did the build for jdk7 Build 27. A handy feature.
>>>> -kto
>>>> Rob Ross wrote:
>>>>> What is the difference between the code in
>>>>>
>>>>> (A) jdk7/jdk7
>>>>> (B) jkd7/rev/56652b46f328?
>>>>>
>>>>> I thought (A) was the "master" repository with the latest  
>>>>> "build" code (not latest snapshot though) but I think I may  
>>>>> just be confused. If (A) does not contain build 27 code, what  
>>>>> codes does it contain?
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>> Rob Ross, Lead Software Engineer
>>>>> E! Networks
>>>>>
>>>>> ---------------------------------------------------
>>>>> "Beware of he who would deny you access to information, for in  
>>>>> his heart he dreams himself your master." -- Commissioner  
>>>>> Pravin Lal
>>>>>
>>>>>
>>>>>
>>>>> On May 23, 2008, at 8:04 AM, Xiomara Jayasena wrote:
>>>>>
>>>>>>
>>>>>> The OpenJDK source is available at:
>>>>>> http://hg.openjdk.java.net/jdk7/jdk7
>>>>>> and the build 27 source is here:
>>>>>> http://hg.openjdk.java.net/jdk7/jdk7/rev/56652b46f328
>>>>>>
>>>>>> The OpenJDK source binary plugs and Jtreg binary for the  
>>>>>> promoted JDK 7 build 27 are available under the openjdk http:// 
>>>>>> openjdk.java.net website under Source Code (direct link to  
>>>>>> bundles: http://download.java.net/openjdk/jdk7)
>>>>>>
>>>>>> Summary of changes:
>>>>>> http://download.java.net/jdk7/changes/jdk7-b27.html
>>>>>>
>>>>>> -Xiomara
>>>>>>
>>>>>