openjdk build pages

[dalibor topic]

On 22.05.2014 01:44, Omair Majid wrote:
> * dalibor topic <dalibor.topic at oracle.com> [2014-05-21 05:15]:
>> Beside being potentially error prone,
>
> I am not sure I understand.

That was a reference to the "then we have to create it manually, which 
is error prone" section of your previous e-mail.

>> and update releases that we can't work on as part of OpenJDK (like
>> 7u55),
>
> I am not sure I follow. If you can commit the source to the repository
> and tag it, why can't you create a source bundle for those tags?

It doesn't make a lot of sense for a Project to provide source code 
archives for releases that are not releases actually produced by the 
Project.

> If not providing source
> bundles causes confusion, wouldn't the right fix be to provide source
> bundles?

See above.

> As for benefit, just today I saw people asking on #openjdk about where
> to get source bundles.

They are linked off the front (and any other OpenJDK web site) page.

> And they complained that using source control to
> get a release bundles is too hard (and shouldn't be necessary).

I'm not sure why one would consider

hg clone http://hg.openjdk.java.net/jdk7u/jdk7u40; cd jdk7u40; bash 
get_source.sh

to be too hard compared to

wget 
http://www.java.net/download/openjdk/jdk7u40/promoted/b43/openjdk-7u40-fcs-src-b43-26_aug_2013.zip 


- it seems to be fewer characters, even. ;)

Yes, it's 3 short commands instead of one short command. That doesn't 
appear to me as a significant difference in hardship, though.

> Also, if you think users have problems distinguishing 7u60 from 7u55,
> can you imagine the problems they will have trying to find the
> real/final tag for 7u55 in the repos?

I don't see that as problematic if it's documented.

For example, the Project page for JDK 7 Updates could eventually say 
'Hooray! 7u60 was released. The source code available in the 
jdk7u/jdk7u60 repository with the  release being tagged with 
something-or-other. Use hg clone [snip] get_source.sh to check it out.'

>  And how some tags do not exist in
> some repos at some points in time? [2].

As soon as you have more then one forest covering the same Project, some 
tags won't exist in some repo at some point in time, while they exist in 
another, because commits to repositories are not atomic - not at the 
forest level, and not at the inter-forest-synchronization level.

cheers,
dalibor topic

-- 
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>

ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment