* Andrew Hughes <gnu.and...@redhat.com> [2015-07-07 14:51]: > I'm working on the assumption so far that we'll use an OPENJDK7 > instance equivalent to the one we did for OpenJDK 6. As you say, > access to the OpenJDK JIRA is limited and it would be difficult > for us to e.g. add milestones, additional users, etc.
There should definitely some change in the OpenJDK JIRA to allow the project lead to make the changes they see fit (including adding milestones and what not). I am not sure I am convinced by additional users, though: if you are committing to OpenJDK 7, you have an OpenJDK user id and can access the bug tracker. > It's also > replete with references to proprietary 7 releases, such as u85, > which would only cause confusion. I wonder if we can use a separate project in the official OpenJDK bug tracker. There are existing projects like KONA and DIO there and perhaps we can create OPENJDK7, if the official JDK project is not usable. If not, then I agree about falling back to a separate project on java.net. > Most importantly, we need somewhere to host source tarball releases > and the java.net instance would provide this too. In the short term, agreed. But perhaps, in the long run (I am thinking when 8 goes through something like this) it might be better to have a project-specific place to publish project-official source releases (if any). I can't imagine that other projects would object to having an optional place where they can upload releases if they want. I see that Oracle also seems to be using java.net for their proprietary JDK 9 builds [1] too. I am not sure we want something like that, because we will be trying to distribute open source tarballs under licence terms matching the rest of the OpenJDK project. Thanks, Omair [1] https://jdk9.java.net/ -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681
