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:47:47 GMT


Steven Rowe commented on LUCENE-3163:

Upon review, many previous lucene releases had no date here, and solr stopped putting them
in a long time ago.

If someone is a historian, they can use the apache mail archives or websites or something
else to discover all these dates... lets make it one less hassle.

I don't like this.  It really pisses me off when I look at release notes and nothing anchors
the releases to dates.  Having to look elsewhere sucks big time.  Release numbers plus relative
time between releases contains information that's helpful to people when they decide what
release to choose.  You removed useful information.

I'm guessing your motivation, Robert, was to reduce release friction.  I support that motivation.
 But I didn't say that the missing date should block the release, so as far as I'm concerned,
release friction reduction doesn't cut it as motivation for this change.

I want to put back the release dates.

I'm open to other opinions.

> 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