jsr348
  1. jsr348
  2. JSR348-22

3.3 - Agility - Concept of maintenance release should be replaced with semi-annual release.

    Details

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

      Description

      >> Maintenance releases concept should be deprecated. Instead, a new version of Java EE should be released semi-yearly, and all new final releases or maintenance releases should be included in the new umbrella EE specification. Vendors are free to certify against as many or as few semi-yearly releases as they choose. -Lincoln

      This would resolve the issues with specification communication, brittleness, and also empower change, while still ensuring stability of the platform through versioning. It is up to the vendor how much they want to keep up with versions or not.

      This would be much more in line with the nature of software development, instead of the current ... I'm just going to say, "sluggish," process we have now.

        Activity

        Hide
        lincolnbaxter added a comment -

        These ideas were drafted by an independent group reviewing the Early Draft from June 21, 2011 - apologies for out-of-date issues.

        Show
        lincolnbaxter added a comment - These ideas were drafted by an independent group reviewing the Early Draft from June 21, 2011 - apologies for out-of-date issues.
        Hide
        karianna added a comment -

        As per JSR348-10 I'll quote Patrick and myself:

        Patrick: "We cannot mandate that a Spec Lead invest resources and make a maintenance release - we can only encourage this (as we do.)

        Your specific comments should be addressed to the EE Spec Lead."

        Martijn: "To add further to this - there is nothing stopping a new JSR being raised if an individual or entity feels that a maintenance release isn't forthcoming from the original JSR EG."

        Show
        karianna added a comment - As per JSR348-10 I'll quote Patrick and myself: Patrick: "We cannot mandate that a Spec Lead invest resources and make a maintenance release - we can only encourage this (as we do.) Your specific comments should be addressed to the EE Spec Lead." Martijn: "To add further to this - there is nothing stopping a new JSR being raised if an individual or entity feels that a maintenance release isn't forthcoming from the original JSR EG."
        Hide
        pcurran added a comment -

        Closing this, since we've addressed the submitter's concern (though perhaps not to his satisfaction.)

        Show
        pcurran added a comment - Closing this, since we've addressed the submitter's concern (though perhaps not to his satisfaction.)

          People

          • Assignee:
            Unassigned
            Reporter:
            lincolnbaxter
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: