I think we should just add a CHANGES section for 4.0.1? There are 2 commits actually that Stefan made that should be moved under this section: I felt like i intended to do this (create 4.0.1 section and move them), but I think I forgot.
In the past these branches (e.g. lucene_solr_3_6) have been setup with the assumption that there might be a 3.6.1... personally Ive been handling bugs by just committing them to 4.1. If someone said they wanted to do a 4.0.1, i would probably think about backporting some of these, but features etc are already starting to look nice for 4.1 so I havent worried myself yet. On Wed, Oct 17, 2012 at 4:13 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > I notice that the CHANGES.txt files on the lucene_solr_4_0 doesn't yet have > a section for 4.0.1 bug fixes even though it looks like there have been some > bug fix commits on that branch since 4.0.0 was released. > > On the other hand it looks like some folks (maybe just miller?) have been > using the Jira label "4.0.1_Candidate" on issues that get committed to the > branch_4x, but aren't being commited to lucene_solr_4_0 -- presumably as a > reminder that we should backport if we do a 4.0.1 release > > All of which leaves me a bit confused: is there any concensus on how we > should be dealing with (potential) 4.0.1 bug fixes? > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
