: > But there is no way for someone looking at the CHANGES for 4.0 to know
: > for certain that the bits that make up that bug fix are in the 4.0 release
: > -- the fact that it's listed in 3.2's CHANGES isn't an assurance, because
: > 4.0 comes from a completely different line of development.
...
: its in the 4.0 CHANGES.txt, under the 3.2 section.
(sigh ... i tried to let this go, i swear i did...)
You're missing my point entirely. yes it's in the 3.2 section but all
that tells the user is that it was fixed on the 3x branch just prior to
the 3.2 release -- that doesn't give users *any* info about wether that
bug ever affected (or was fixed) on the completely and radically different
4x branch. There were multiple commits -- the bits are not the same.
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
