[
https://issues.apache.org/jira/browse/LUCENE-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041451#comment-13041451
]
Robert Muir commented on LUCENE-3163:
-------------------------------------
bq. I didn't know about this functionality. I think putting this link in the
CHANGES.txt files is an acceptable alternative to dates in the CHANGES.txt
files themselves.
OK, but lets do this for 3.3, 4.0?
If it really makes you that upset, i'd rather put the link in the actual
release email than respin.
> 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: [email protected]
For additional commands, e-mail: [email protected]
