If it's possible to autogenerate CHANGES.txt, I'd vote for that. - Andy
________________________________ From: stack <[email protected]> To: [email protected] Sent: Saturday, June 13, 2009 3:09:25 PM Subject: Re: commits without entries in CHANGES.txt They both seem to be Ryan issues. JIRA can be a bit tricky too when it comes to saying fixed in branch and trunk (Can you mark it as fixed in two places? I haven't figured it). I'm up for whatever lads think is the easiest. We could copy/paste text-only version from time to time into CHANGES.txt. Hadoop does a nice thing where actual issue release notes show up in CHANGES.txt. I ain't sure how that is done. We should ask Nigel how its done. St.Ack On Sat, Jun 13, 2009 at 2:38 PM, Andrew Purtell <[email protected]> wrote: > There are commits in the tree without entries in CHANGES.txt, at least > these: > > HBASE-1304 > HBASE-1514 > > maybe more. > > With the release note tools provided by JIRA, do we even need a manually > updated CHANGES.txt? Otherwise I'd say this file is getting out of sync > with what is in the tree. > > - Andy > > > >
