lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3163) CHANGES.txt has no release date for 3.1.0
Date Tue, 31 May 2011 05:51:47 GMT


Robert Muir commented on LUCENE-3163:

Steven, well you can look through the CHANGES.txt before my commit and see that in Lucene,
many releases have no date (like most of the 1.x series).
Additionally Solr stopped doing this about 1.4 (instead just saying "see the website for the

I really don't like the dates, I'm sorry. The only thing the dates do is create another thing
to update, with no clear benefit to anyone.
Our goal here is to create open source releases... not maintain a historical record... these
dates make releasing harder.

If we must have dates in CHANGES.txt, then I vote to remove CHANGES.txt completely rather
than make releasing so difficult!!!!

> CHANGES.txt has no release date for 3.1.0
> -----------------------------------------
>                 Key: LUCENE-3163
>                 URL:
>             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:

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

View raw message