lucene-dev mailing list archives

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


Steven Rowe commented on LUCENE-3163:

bq. with no clear benefit to anyone.

I seriously disagree with this assertion.  I personally look for dates to help me understand
the release history on a project.  There is a clear benefit to *me* as a user of software,
and I don't think I'm alone.

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

Putting a date into a file is difficult?  After a release has been rolled out, not as a precondition
for the release?  Sorry, Robert, I don't buy it.

> 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