[7u-communication] Pushing into the right forest for 7u60
dalibor topic
dalibor.topic at oracle.com
Wed Jan 22 07:01:25 PST 2014
Hi,
in order to make our life a bit simpler, I'd like to propose that
changes destined for 7u60, once we create the stabilization forest, go
into jdk7u-dev first, and then get pulled over into jdk7u60(-dev).
In other words, all approved changes would go straight to jdk7u-dev, and
just the ones approved for 7u60 with the corresponding label would then
be picked out and regularly (but typically not instantly) integrated
into the 7u60 stabilization forest by one of the Maintainers.
The benefit of this approach is that we won't run into the
post-stabilization-forest-creation phenomenon of developers wondering
which particular forest to push their particular change to, and
sometimes ending up sending me e-mails to figure out if they had made
some critical error in the process and pushed to the wrong place. ;)
In addition, this approach simplifies synchronization between the
stabilization forest and the jdk7u-dev forest, as there would be only
one direction in which the changes would flow - into jdk7u-dev and from
there to the stabilization forest.
In terms of process documents, that means changing the last line of
http://openjdk.java.net/projects/jdk7u/phase2/phase2-process.html from
"Fixes to the regular 7u-dev forest follow the normal approval template
process."
to
"Fixes approved for the stabilization forest are pushed to the jdk7u-dev
forest by a Committer. They are integrated into the stabilization forest
by a Maintainer. Fixes not destined for the stabilization forest follow
the normal approval template process and upon approval, are pushed into
the jdk7u-dev forest."
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
More information about the jdk7u-dev
mailing list