lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3004) Define Test Plan for 3.2
Date Mon, 30 May 2011 20:33:47 GMT


Robert Muir commented on LUCENE-3004:

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".

> Define Test Plan for 3.2
> ------------------------
>                 Key: LUCENE-3004
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Test
>            Reporter: Grant Ingersoll
>            Priority: Blocker
>             Fix For: 3.2
> 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
> See

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message