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:59:48 GMT


Robert Muir commented on LUCENE-3163:

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

Yes, it makes releasing more difficult. we really need to reduce the amount of little things
we have to do to take a release.
we have 12 fucking changes files 2 branches (stable and trunk) to maintain.

Removing these dates is 24 less little things i have to do to make a release... thats a pretty
big deal. I'm gonna do everything I can to tone down what we have to do to make a release.

> 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