I don't see much of a reason to have the same JIRA listed under both 0.23 and 2.0. I can see some advantage of being able to see what went into 0.23.X by looking at a 2.0.X CHANGES.txt, but unless the two are released at exactly the same time they will be out of date with each other in the best cases. I personally think the only way to truly know what is in 0.23.X is to look at the CHANGES.txt on 0.23.X and similarly for 2.X. Having JIRA be in sync is a huge help and we should definitely push for that. I just don't see much value in trying very hard to have the CHANGES.txt stay in sync.
--Bobby On 10/8/12 10:21 PM, "Siddharth Seth" <seth.siddha...@gmail.com> wrote: >Along with fix versions, does it make sense to add JIRAs under 0.23 as >well >as branch-2 in CHANGES.txt, if they're committed to both branches. >CHANGES.txt tends to get out of sync with the different release schedules >of the 2 branches. > >Thanks >- Sid > >On Sat, Sep 29, 2012 at 10:33 PM, Arun C Murthy <a...@hortonworks.com> >wrote: > >> Guys, >> >> A request - can everyone please set fix-version to both 2.* and >>0.23.*? I >> found some with only 0.23.*, makes generating release-notes very hard. >> >> thanks, >> Arun
