What if we for the version being released say “Release date: September 2016 (current release, see exact date on release archive)” but when we create the section heading for the next release we also fill in the exact date for the previous one.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 27. sep. 2016 kl. 15.03 skrev Yonik Seeley <[email protected]>: > > Release dates were always a problem because one would have to guess > when the vote would pass (and change the date every time a new RC is > spun... error prone). Perhaps just add month+year? > > -Yonik > > > On Tue, Sep 27, 2016 at 8:53 AM, David Smiley <[email protected]> > wrote: >> +1 to fix the reference to Lucene's CHANGES.txt and to add release dates. >> >> On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <[email protected]> wrote: >>> >>> Hi, >>> >>> In Solr’s CHANGES.txt there is this line for every release since 4.10: >>> >>> Consult the LUCENE_CHANGES.txt file for additional, low level, changes >>> in this release. >>> >>> But there is no file with that name… >>> >>> >>> Also, why don’t we add the release date for each release also to >>> CHANGES.txt? >>> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> -- >> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: >> http://www.solrenterprisesearchserver.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
