You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2011/03/30 18:12:05 UTC

[jira] [Created] (LUCENE-3005) Define Test Plan for 4.0

Define Test Plan for 4.0
------------------------

                 Key: LUCENE-3005
                 URL: https://issues.apache.org/jira/browse/LUCENE-3005
             Project: Lucene - Java
          Issue Type: Test
    Affects Versions: 4.0
            Reporter: Grant Ingersoll
            Priority: Blocker


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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3005) Define Test Plan for 4.0

Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-3005:
--------------------------------

    Priority: Minor  (was: Blocker)
    
> Define Test Plan for 4.0
> ------------------------
>
>                 Key: LUCENE-3005
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3005
>             Project: Lucene - Java
>          Issue Type: Test
>    Affects Versions: 4.0
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 4.0
>
>
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3005) Define Test Plan for 4.0

Posted by "Steven Rowe (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455929#comment-13455929 ] 

Steven Rowe commented on LUCENE-3005:
-------------------------------------

I think {{smokeTestRelease.py}} does exactly this.

What it doesn't/can't do is sanity check things to make sure no new problems have cropped up.  But even in this case, new checks can be added to the script once they have been identified.

So IMHO this should be closed as won't fix.  I'll do so tomorrow if there are no objections.


                
> Define Test Plan for 4.0
> ------------------------
>
>                 Key: LUCENE-3005
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3005
>             Project: Lucene - Core
>          Issue Type: Test
>    Affects Versions: 4.0-ALPHA
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 4.1
>
>
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3005) Define Test Plan for 4.0

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455960#comment-13455960 ] 

Robert Muir commented on LUCENE-3005:
-------------------------------------

Right, i think a lot of this is old news, its not perfect but we are closer.

As far as what Grant mentioned in the original thread: I think we've tried to automate this as much
as possible in the smokeTestRelease.py: it takes the actual generated artifacts and does a ton
of tests on them.

As i mentioned in the original thread, the worst part of the release process before was that the code
wasn't releasable until someone cleaned it up: I think this is significantly better. We have a lot
more checks in the build system: nitpicking over javadocs, 3rd party dependencies, license headers,
etc, etc. And we run the smokeTestRelease.py as a weekly hudson job to ensure things like packaging
are not broken.

In my opinion we should continue down this path, trying to ensure that our code is always releasable
at any time from this kind of perspective, rather than adding manual steps.

I think the right way to do this is just like how we handle bugs in our code. If a problem crops up
in e.g. packaging, don't just fix it, but also add a 'test' (code to smokeTestRelease or whatever) so
that jenkins is continuously looking for it.

In my opinion most of the previous problems were all due to:
* not having tests (in this sense 'test' means testing packaging, licensing, etc)
* not having automated builds running those tests.

                
> Define Test Plan for 4.0
> ------------------------
>
>                 Key: LUCENE-3005
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3005
>             Project: Lucene - Core
>          Issue Type: Test
>    Affects Versions: 4.0-ALPHA
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 4.1
>
>
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3005) Define Test Plan for 4.0

Posted by "Jack Krupansky (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455951#comment-13455951 ] 

Jack Krupansky commented on LUCENE-3005:
----------------------------------------

That Lucid link doesn't work for me. I think it is equivalent to:

http://www.gossamer-threads.com/lists/lucene/java-dev/120890
or
http://mail-archives.apache.org/mod_mbox/lucene-dev/201103.mbox/%3C5D982587-7316-4CC5-B1A0-2F91E50073B5@apache.org%3E

                
> Define Test Plan for 4.0
> ------------------------
>
>                 Key: LUCENE-3005
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3005
>             Project: Lucene - Core
>          Issue Type: Test
>    Affects Versions: 4.0-ALPHA
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 4.1
>
>
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3005) Define Test Plan for 4.0

Posted by "Uwe Schindler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Uwe Schindler updated LUCENE-3005:
----------------------------------

    Fix Version/s: 4.0

> Define Test Plan for 4.0
> ------------------------
>
>                 Key: LUCENE-3005
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3005
>             Project: Lucene - Java
>          Issue Type: Test
>    Affects Versions: 4.0
>            Reporter: Grant Ingersoll
>            Priority: Blocker
>             Fix For: 4.0
>
>
> 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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org