I've had no problems looking in git log (or in GitX a git GUI) but sounds like everyone else uses release-log.txt, so I guess I'm in the minority here.
Let's leave the release-log.txt as is then. On Thu, Mar 26, 2015 at 2:26 PM, Rohini Palaniswamy <[email protected] > wrote: > I agree with Bowen. That is the first place we look for changes that have > gone in. Running queries on JIRA or going through git logs is cumbersome > and not easy to go over multiple releases. Also currently Fix version is > not followed properly at all. We are more disciplined with release-log.txt. > > Regards, > Rohini > > On Thu, Mar 26, 2015 at 12:56 PM, bowen zhang < > [email protected]> wrote: > > > I don't see a good alternative to track which jira goes into which > > branch.I would advise against removing release-log.txt > > > > From: Robert Kanter <[email protected]> > > To: "[email protected]" <[email protected]> > > Sent: Thursday, March 26, 2015 12:07 PM > > Subject: [DISCUSS] get rid of release-log.txt? > > > > Hi all, > > > > Do we need to keep maintaining the release-log.txt? It's an extra step > for > > committing (that we sometimes mess up or forget) and I'm not sure how > much > > benefit we get from using it given that we have the same information in > > JIRA and the git log. Personally, it makes backporting patches to CDH > more > > cumbersome because there's almost always a conflict in release-log.txt, > so > > I pretty much ignore it. > > > > Hadoop has been discussing getting rid of their CHANGES.txt recently. > And > > while most people seem to agree it would be good to get rid of, they're > > having a lot of discussion on what to use instead. I think our project > is > > small enough compared to Hadoop that git and JIRA should be fine. > > > > What do others think? > > > > > > thanks > > - Robert > > > > > > > > >
