You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2011/05/31 01:19:47 UTC

[jira] [Resolved] (LUCENE-3163) CHANGES.txt has no release date for 3.1.0

     [ https://issues.apache.org/jira/browse/LUCENE-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir resolved LUCENE-3163.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2

Committed revision 1129427 (trunk), 1129430 (branch_3x), 1129432 (branch32).

When merging back from trunk, I noticed branch_3x got a merge conflict because the entire 2.9.4/3.0.3 section was missing, I added this from trunk to both these branches so that the CHANGES.txt files are properly synchronized.

> CHANGES.txt has no release date for 3.1.0
> -----------------------------------------
>
>                 Key: LUCENE-3163
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3163
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>              Labels: maybe32blocker
>             Fix For: 3.2, 3.3, 4.0
>
>
> CHANGES.txt has no release date for 3.1.0 - although we've stopped putting dates on RCs' CHANGES.txt for the release-to-be, we should add dates to CHANGES.txt for past releases.
> Alternatively we could remove releases dates for past release completely.

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