jsr348
  1. jsr348
  2. JSR348-70

Simplify Maintenance Review process by eliminating Item Exception Ballot and Change Log

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Component/s: None
    • Labels:
      None

      Description

      Here's a proposed change that simplifies the Maintenance Review process by
      eliminating the Item Exception Ballot and the Change Log. The Change Log is
      replaced by the issue tracker, plus a general reference to the materials
      submitted to the PMO for the Maintenance Review. (References to the Change
      Log elsewhere need to be fixed as well.)

      4.1 MAINTENANCE REVIEW

      The ML will document all proposed Specification changes as separate
      line item changes (indicating dependencies between items) and then send
      a request to the PMO to initiate a Maintenance Review. Before the
      Maintenance Review begins, the ML must summarize comments received
      through the Maintenance feedback email list and must indicate the
      disposition of each comment (e.g. deferred with a brief explanation,
      rejected with a brief explanation, included in the proposal.) This
      summary may be in the form of references to an issue tracking system.
      This summary will be posted along with the MR request on the JSR Page.
      The PMO will then make a public announcement and begin the review.

      The ML may choose to modify one or more of the proposed changes based
      on comments received during the review.

      At the close of the Maintenance Review the PMO will initiate a 7-day
      Maintenance Review Ballot. During this ballot EC members should vote
      "yes" if they agree that the Maintenance Release should go ahead as the
      Spec Lead has proposed, and "no" if they believe that one or more of
      the changes proposed by the ML is inappropriate for a Maintenance
      Release and should be deferred to a follow-on JSR. "No" votes must be
      accompanied by comments in which the offending items are identified and
      the reasons for the objection are explained.

      If any line item receives "no" votes from 1/3 or more of the EC members,
      the ML may choose to complete the MR without those items, or may choose
      to withdraw the MR, possibly resubmitting a modified version or possibly
      submitting a full JSR.

      NOTE: there is no minimum number of "yes" votes required to move
      forward with the proposed Maintenance Release, and "no" votes cannot
      prevent a release unless the ML is unwilling to defer items.

      At the end of Maintenance Review the ML will update the Specification,
      incorporating all approved changes. Items that received "no" votes
      from 1/3 or more of the EC members must not be included.

      4.2 MAINTENANCE RELEASE

      At any time after a Maintenance Review Ballot the Spec Lead will update
      the Specification, RI, and TCK, as necessary and submit them to the PMO
      for publication in a Maintenance Release. The PMO verifies that the
      necessary changes have been made, and publishes the Specification, and
      pointers to the RI and TCK on the JSR Web Page.

      NOTE: until the Maintenance Release stage is reached any proposed
      changes should be considered preliminary and subject to change, and
      therefore should not be implemented in shipping products.

        Issue Links

          Activity

          Hide
          pcurran added a comment - - edited

          I've written up a new Maintenance Release process proposal based on our discussion during yesterday's Working Group meeting. See here.

          Please review this, and comment on it here.

          Thanks...

          Show
          pcurran added a comment - - edited I've written up a new Maintenance Release process proposal based on our discussion during yesterday's Working Group meeting. See here . Please review this, and comment on it here. Thanks...
          Hide
          starksm64 added a comment -

          I agree with the terms Issue Tracker, Issue and Issue List. I have added what I believe would be the minimum states/categories to the Issue Tracker (JSR348-71) definition issue.

          In terms of how changes to license, RI and TCK must be now be provided, this must be done via one or more Issues.

          Otherwise, I believe the proposal is good.

          Show
          starksm64 added a comment - I agree with the terms Issue Tracker, Issue and Issue List. I have added what I believe would be the minimum states/categories to the Issue Tracker ( JSR348-71 ) definition issue. In terms of how changes to license, RI and TCK must be now be provided, this must be done via one or more Issues. Otherwise, I believe the proposal is good.
          Hide
          pcurran added a comment -

          Re the suggestion that "In terms of how changes to license, RI and TCK must be now be provided, this must be done via one or more Issues," as discussed at last week's Working Group meeting this would be more easily handled by the PMO requiring this information in the template that they use for submissions.

          Show
          pcurran added a comment - Re the suggestion that "In terms of how changes to license, RI and TCK must be now be provided, this must be done via one or more Issues," as discussed at last week's Working Group meeting this would be more easily handled by the PMO requiring this information in the template that they use for submissions.
          Hide
          pcurran added a comment - - edited

          The first set of changes to implement the agreed-upon proposal

          Add this new definition

          Maintenance Renewal Ballot: a ballot during which EC members vote on whether to permit a Maintenance Lead to extend the deadline for delivery of materials for Maintenance Release, or whether the previous Maintenance Review should be rescinded and the ML be required to start the process again.

          Change these definitions as specified

          Maintenance Review: A period of at least 30 days prior to finalization of a Maintenance Release when Members and the public consider and comment on the changes the Spec Lead proposes to include in the release, as identified in the associated Issue List.

          Maintenance Review Ballot: An EC ballot to determine whether the changes and time line proposed by a Maintenance Lead are appropriate for a Maintenance Release.

          Delete these definitions

          • Item Exception Ballot
          • Change Log

          Make the following changes (line numbers refer to the Public Review Draft)

          Line 234: delete "in the Change Log"

          Lines 427-428: Change "the Change Log kept by the Maintenance Lead (see section 5)" to "the Issue list kept by the Maintenance Lead"

          Lines 497-500:

          Change:

          "the Maintenance Lead must update these deliverables as necessary and record the changes in the relevant sections of the Change Log. The modified Change Log, the Specification (if changed,) and URLs for the updated RI and/or TCK must be delivered to the PMO, who will publish them on the JCP website."

          to:

          "the Maintenance Lead must update these deliverables as necessary and report the changes to the PMO when the Specification (if changed,) and URLs for the updated RI and/or TCK are delivered for publication on the JCP website."

          Show
          pcurran added a comment - - edited The first set of changes to implement the agreed-upon proposal Add this new definition Maintenance Renewal Ballot : a ballot during which EC members vote on whether to permit a Maintenance Lead to extend the deadline for delivery of materials for Maintenance Release, or whether the previous Maintenance Review should be rescinded and the ML be required to start the process again. Change these definitions as specified Maintenance Review : A period of at least 30 days prior to finalization of a Maintenance Release when Members and the public consider and comment on the changes the Spec Lead proposes to include in the release, as identified in the associated Issue List. Maintenance Review Ballot : An EC ballot to determine whether the changes and time line proposed by a Maintenance Lead are appropriate for a Maintenance Release. Delete these definitions Item Exception Ballot Change Log Make the following changes (line numbers refer to the Public Review Draft) Line 234 : delete "in the Change Log" Lines 427-428 : Change "the Change Log kept by the Maintenance Lead (see section 5)" to "the Issue list kept by the Maintenance Lead" Lines 497-500 : Change: "the Maintenance Lead must update these deliverables as necessary and record the changes in the relevant sections of the Change Log. The modified Change Log, the Specification (if changed,) and URLs for the updated RI and/or TCK must be delivered to the PMO, who will publish them on the JCP website." to: "the Maintenance Lead must update these deliverables as necessary and report the changes to the PMO when the Specification (if changed,) and URLs for the updated RI and/or TCK are delivered for publication on the JCP website."
          Hide
          pcurran added a comment -

          Second - and final, for now - set of changes to implement the agreed-upon proposal

          Replace sections 5.2 and 5.3 with the following

          5.2 MAINTENANCE REVIEW

          The Maintenance Lead will document all proposed Specification changes through the Issue Tracker and then send a request to the PMO to initiate a Maintenance Review. This request must be accompanied by an Issue List that summarizes all formal comments that have been received and that indicates the disposition of each Issue. The Maintenance Lead should also supply a summary of the proposed Specification changes, ideally in the form of a diff between the proposed and the current Specification. The Maintenance Lead must also provide an estimate of when the final materials will be delivered for the Maintenance Release. If no estimate is provided the deadline will default to 30 days.

          The PMO will post the materials on the JCP website for public review. The Maintenance Lead may choose to modify one or more of the proposed changes based on comments received during the review.

          At the close of the Maintenance Review the PMO will initiate a 7-day Maintenance Review Ballot. During this ballot EC members should vote 'yes' if they agree that the Maintenance Release should proceed as the Spec Lead has proposed, and 'no' if they have objections to the proposed release on one of the following grounds:

          • One or more of the changes proposed by the Maintenance Lead is inappropriate for a Maintenance Release and should be deferred to a follow-on JSR
          • The proposed Maintenance Release date too far in the future. (EC members should bear in mind that many Maintenance Releases need to be synchronized with updates to a Platform, and that a Maintenance Review may therefore need to be carried out significantly in advance of the proposed Platform release.)
          • Unreasonable changes have been made to the RI or TCK licensing terms.

          'No' votes on other grounds will be rejected by the PMO and will be considered as abstentions. All 'no' votes must be accompanied by comments explaining the reason for the vote.

          If the ballot fails, the Maintenance Lead may make any necessary corrections before requesting another Maintenance Review and ballot. The process may be repeated any number of times.

          5.3 MAINTENANCE RELEASE

          After a successful Maintenance Review Ballot the Maintenance Lead will update the Specification, RI, TCK, and Issue List as necessary and submit them to the PMO for publication in a Maintenance Release. The PMO verifies that the necessary changes have been made, and publishes the Specification, the Issue List, and pointers to the RI and TCK on the JSR Web Page.

          NOTE: until the Maintenance Release stage is reached any proposed changes should be considered preliminary and subject to change, and therefore should not be implemented in shipping products.

          If the Maintenance Lead fails to deliver the final materials within the time-period specified at the beginning of the Maintenance Review process a Maintenance Renewal Ballot will be held to determine whether the deadline may be extended or whether the previous Maintenance Review should be rescinded and the Maintenance Lead be required to go through another Maintenance Review.

          Show
          pcurran added a comment - Second - and final, for now - set of changes to implement the agreed-upon proposal Replace sections 5.2 and 5.3 with the following 5.2 MAINTENANCE REVIEW The Maintenance Lead will document all proposed Specification changes through the Issue Tracker and then send a request to the PMO to initiate a Maintenance Review. This request must be accompanied by an Issue List that summarizes all formal comments that have been received and that indicates the disposition of each Issue. The Maintenance Lead should also supply a summary of the proposed Specification changes, ideally in the form of a diff between the proposed and the current Specification. The Maintenance Lead must also provide an estimate of when the final materials will be delivered for the Maintenance Release. If no estimate is provided the deadline will default to 30 days. The PMO will post the materials on the JCP website for public review. The Maintenance Lead may choose to modify one or more of the proposed changes based on comments received during the review. At the close of the Maintenance Review the PMO will initiate a 7-day Maintenance Review Ballot. During this ballot EC members should vote 'yes' if they agree that the Maintenance Release should proceed as the Spec Lead has proposed, and 'no' if they have objections to the proposed release on one of the following grounds: One or more of the changes proposed by the Maintenance Lead is inappropriate for a Maintenance Release and should be deferred to a follow-on JSR The proposed Maintenance Release date too far in the future. (EC members should bear in mind that many Maintenance Releases need to be synchronized with updates to a Platform, and that a Maintenance Review may therefore need to be carried out significantly in advance of the proposed Platform release.) Unreasonable changes have been made to the RI or TCK licensing terms. 'No' votes on other grounds will be rejected by the PMO and will be considered as abstentions. All 'no' votes must be accompanied by comments explaining the reason for the vote. If the ballot fails, the Maintenance Lead may make any necessary corrections before requesting another Maintenance Review and ballot. The process may be repeated any number of times. 5.3 MAINTENANCE RELEASE After a successful Maintenance Review Ballot the Maintenance Lead will update the Specification, RI, TCK, and Issue List as necessary and submit them to the PMO for publication in a Maintenance Release. The PMO verifies that the necessary changes have been made, and publishes the Specification, the Issue List, and pointers to the RI and TCK on the JSR Web Page. NOTE: until the Maintenance Release stage is reached any proposed changes should be considered preliminary and subject to change, and therefore should not be implemented in shipping products. If the Maintenance Lead fails to deliver the final materials within the time-period specified at the beginning of the Maintenance Review process a Maintenance Renewal Ballot will be held to determine whether the deadline may be extended or whether the previous Maintenance Review should be rescinded and the Maintenance Lead be required to go through another Maintenance Review.
          Hide
          pcurran added a comment -

          Please make the changes described in the previous two comments and then let's publish and seek further feedback.

          Thanks...

          Show
          pcurran added a comment - Please make the changes described in the previous two comments and then let's publish and seek further feedback. Thanks...
          Hide
          pcurran added a comment -

          Force assignment to Eduardo by closing and reopening...

          Show
          pcurran added a comment - Force assignment to Eduardo by closing and reopening...
          Hide
          eduardo added a comment -

          I've incorporated all suggested changes. I've also noticed that the changes include both "Issue List" and "Issue list". These should be normalized and "Issue List" should be either defined or left as "issue list". I will open an issue on this.

          Show
          eduardo added a comment - I've incorporated all suggested changes. I've also noticed that the changes include both "Issue List" and "Issue list". These should be normalized and "Issue List" should be either defined or left as "issue list". I will open an issue on this.
          Hide
          pcurran added a comment -

          Reopening until we've confirmed that the changes implement what we agreed.

          Show
          pcurran added a comment - Reopening until we've confirmed that the changes implement what we agreed.
          Hide
          pcurran added a comment -

          It is resolved - we just need to review

          Show
          pcurran added a comment - It is resolved - we just need to review
          Hide
          pcurran added a comment -

          Closed, as agreed at the September 21 Working Group meeting.

          Show
          pcurran added a comment - Closed, as agreed at the September 21 Working Group meeting.

            People

            • Assignee:
              eduardo
              Reporter:
              Bill Shannon
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: