You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dyer, James" <Ja...@ingrambook.com> on 2012/04/23 19:01:48 UTC
How do I document bugfixes applied to 3.6 branch?
I would like to commit SOLR-3361 to 3.6 in case there is a 3.6.1. Should I start a new 3.6.1 section in changes.txt? Does it just go under 4.0 or 3.0 with a note that it is in the 3.6 branch also (but not released)?
James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311
Re: How do I document bugfixes applied to 3.6 branch?
Posted by Robert Muir <rc...@gmail.com>.
Did I miss adding 3.6.1 sections to any of the CHANGES files? If so,
this was just a mistake.
they should be present in the 3.6.x bugfix branch:
http://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_3_6/
As far as trunk, when backporting bugs to these bugfix branches,
before we've also listed it under 4.0, because we aren't even sure we
will even release a 3.6.1... but its good to backport bugs while they
are fresh, especially if they are nasty ones.
On Mon, Apr 23, 2012 at 1:01 PM, Dyer, James <Ja...@ingrambook.com> wrote:
> I would like to commit SOLR-3361 to 3.6 in case there is a 3.6.1. Should I
> start a new 3.6.1 section in changes.txt? Does it just go under 4.0 or 3.0
> with a note that it is in the 3.6 branch also (but not released)?
>
>
>
> James Dyer
>
> E-Commerce Systems
>
> Ingram Content Group
>
> (615) 213-4311
>
>
--
lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org