It wasn't anything i advocate, I'm just describing what it seems like we do 99% of the time? (in my example, Uwe committed it, and I didnt fix anything)
On Tue, Jun 21, 2011 at 1:23 PM, Steven A Rowe <sar...@syr.edu> wrote: > Robert, > > Is the CHANGES.txt policy you advocate (and police) written up in one place? > I'm sure you'd like to not have to fix up everybody's entries.... > > Steve > >> -----Original Message----- >> From: Robert Muir [mailto:rcm...@gmail.com] >> Sent: Tuesday, June 21, 2011 1:14 PM >> To: dev@lucene.apache.org >> Subject: Re: managing CHANGES.txt? >> >> On Tue, Jun 21, 2011 at 1:09 PM, Chris Hostetter >> <hossman_luc...@fucit.org> wrote: >> > >> > 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. >> >> --------------------------------------------------------------------- >> 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
