Details

    • Type: Test Test
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 4.8
    • Component/s: None
    • Labels:
      None

      Description

      Before we can release, we need a test plan that defines what a successful release candidate must do to be accepted.

      Test plan should be written at http://wiki.apache.org/lucene-java/TestPlans

      See http://www.lucidimagination.com/search/document/14bd01e519f39aff/brainstorming_on_improving_the_release_process

        Activity

        Hide
        Robert Muir added a comment -

        Personally I don't like the idea of adding more manual checks to our release process, no matter how formal and well defined they are.

        I am, however, +1 to adding any additional checks and tests to our build system that are completely automated. I don't think we need more of these to block a release, instead this should be an area of continual improvement.

        For example, we added "fail on javadocs warnings" to the build instead of "verify there are no javadocs warnings manually".

        Show
        Robert Muir added a comment - Personally I don't like the idea of adding more manual checks to our release process, no matter how formal and well defined they are. I am, however, +1 to adding any additional checks and tests to our build system that are completely automated. I don't think we need more of these to block a release, instead this should be an area of continual improvement. For example, we added "fail on javadocs warnings" to the build instead of "verify there are no javadocs warnings manually".
        Hide
        Mark Miller added a comment -

        Def does not seem like a blocker to me is my first thought. Far, far from it.

        Also, I don't like the drive to formality this seems to represent - I understand what defines an acceptable release candidate - 3 PMC +1's. Shebam!

        We should just make more targeted improvement JIRA's as needed/motivated. Growth does not need to mean more formality by default. Please gods...

        Show
        Mark Miller added a comment - Def does not seem like a blocker to me is my first thought. Far, far from it. Also, I don't like the drive to formality this seems to represent - I understand what defines an acceptable release candidate - 3 PMC +1's. Shebam! We should just make more targeted improvement JIRA's as needed/motivated. Growth does not need to mean more formality by default. Please gods...
        Hide
        Robert Muir added a comment -

        bulk move 3.2 -> 3.3

        Show
        Robert Muir added a comment - bulk move 3.2 -> 3.3
        Hide
        Robert Muir added a comment -

        Personally I think we could actually mark this issue fixed, a ton of improvements have happened to the release process.
        I'm gonna unset blocker though.

        Show
        Robert Muir added a comment - Personally I think we could actually mark this issue fixed, a ton of improvements have happened to the release process. I'm gonna unset blocker though.
        Hide
        Hoss Man added a comment -

        Bulk of fixVersion=3.6 -> fixVersion=4.0 for issues that have no assignee and have not been updated recently.

        email notification suppressed to prevent mass-spam
        psuedo-unique token identifying these issues: hoss20120321nofix36

        Show
        Hoss Man added a comment - Bulk of fixVersion=3.6 -> fixVersion=4.0 for issues that have no assignee and have not been updated recently. email notification suppressed to prevent mass-spam psuedo-unique token identifying these issues: hoss20120321nofix36
        Hide
        Steve Rowe added a comment -

        Bulk move 4.4 issues to 4.5 and 5.0

        Show
        Steve Rowe added a comment - Bulk move 4.4 issues to 4.5 and 5.0
        Hide
        Michael McCandless added a comment -

        I think the stable release process is working well w/o adding a test plan; smoke tester now helps us catch silly mistakes.

        Show
        Michael McCandless added a comment - I think the stable release process is working well w/o adding a test plan; smoke tester now helps us catch silly mistakes.
        Hide
        Uwe Schindler added a comment -

        Close issue after release of 4.8.0

        Show
        Uwe Schindler added a comment - Close issue after release of 4.8.0

          People

          • Assignee:
            Unassigned
            Reporter:
            Grant Ingersoll
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development