lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3004) Define Test Plan for 3.2
Date Mon, 30 May 2011 20:41:47 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041285#comment-13041285
] 

Mark Miller commented on LUCENE-3004:
-------------------------------------

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

> Define Test Plan for 3.2
> ------------------------
>
>                 Key: LUCENE-3004
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3004
>             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 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


Mime
View raw message