I agree... someday we will. -kto
On Sep 1, 2011, at 10:47 AM, Jonathan Gibbons wrote: > All these mail-based solutions are a pain to keep track of. I hope we get an > issue tracking system some time, any time, that handles the approval process > semi-automatically. > > -- Jon > > > On 09/01/2011 10:18 AM, Kelly O'Hair wrote: >> >> >> I liked Dalibor's JDK7 Update approval template at >> http://openjdk.java.net/projects/jdk7u/approval-template.html >> >> For OpenJDK6 What I was thinking was: >> >> -------- DRAFT ---------- >> >> OpenJDK 6: Push Approval Request Template >> >> Push requests for OpenJDK 6 Project forest >> (http://hg.openjdk.java.net/jdk6/jdk6) >> SHOULD be sent to jdk6-dev@openjdk.java.net and follow this template: >> >> >> Subject: OpenJDK6 Request for approval for CR $NR - $Synopsis >> >> With the body of the email containing: >> >> * if the change applies to JDK 7, it needs to have been integrated into >> the JDK 7 >> Update repositories first. >> Refer to http://openjdk.java.net/projects/jdk7u/ for JDK 7 Update >> procedures. >> >> * if the change applies to the Oracle JDK 6 Update releases, include any >> information >> you have with regards to whether it was fixed in any JDK 6 Update >> release, or not. >> Recommendations on whether the change should or should not be included >> in a >> JDK 6 Update release can help the Oracle Sustaining team. >> >> * either a link to the publicly visible bug/CR on the bugs.sun.com site >> (or its equivalent), or a description of the change so a bug/CR can be >> created. >> >> * either a link to the publicly visible webrev or a link to the JDK 7 (or >> JDK 7 Update) >> changeset, in case it's the the same patch. >> If the review is taking place somewhere else, a link to the public >> review thread >> >> * if the fix has been reviewed the list of reviewers >> >> --------------------------- >> >> Let me know what you think. >> >> -kto >
