On 13.07.2015 10:45, Andrew Haley wrote:
OK, so let me be sure I understand what you mean. We could create a new Project in JBS called (say) OpenJDK7u. It would therefore be separate from proprietary 7u. That sounds quite attractive.
Yeah.
We'd still have the problem that only Authors could create and comment on bugs, but I think that's liveable.
Under the assumption that users detecting issues would continue to report and discuss them on their distributors' issue trackers first, as the distributor's binary they ran may carry additional changes not found in the OpenJDK JDK 7 Updates Project source code repositories, I believe that the number of situations where that restriction would play a role in practice would continue to be very, very small.
Looking at the jdk6-dev traffic from the past 6 months seems to support that conclusion, fwiw: http://openjdk.markmail.org/search/?q=list%3Anet.java.openjdk.jdk6-dev+date%3A2015
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 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
