Hi Johan, On 18 May 2015 at 15:44, Johan Corveleyn <jcor...@gmail.com> wrote: > > On Mon, May 18, 2015 at 2:59 PM, Nicolai Scheer > <nicolai.sch...@gmail.com> wrote: > > Hi all, > > > > we run our subversion repository with a rather standard layout, e.g.: > > > > /trunk > > /branches/1.0.x > > /branches/1.1.x > > /tags/1.0.0 > > /tags/1.0.1 > > /tags/1.1.0 > > /tags/1.1.1 > > > > Trunk of a project gets branched to the branches folder, and tagged from > > there on. > > > > We enforce that every commit's message includes a ticket number for > > reference. > > > > Currently, I'm trying to solve a seemingly simple task, that is, answer the > > question: > > "what's new in the release 1.0.1?". > > > > Speaking of code differences I can just compare the two tags "1.0.0" and > > 1.0.1". > > That's exactly the difference in source code that is about to be shipped, if > > a switch from 1.0.0 to 1.0.1 takes place. > > > > Now, I'd like to expand the question to "What tickets are involved in these > > changes?" > > This one gives me a headache. The diff output has no direct connection to > > the revisions anymore, which is quite obvious since a single diff can show > > the changes of a lot of revisions. > > > > Does anyone have a hint on how to tackle this issue? > > In our build system we generate the list of revision numbers that are > in 1.0.1 but not in 1.0.0 by asking svn for the "revisions that are > eligible for merging from 1.0.1 to 1.0.0" (i.e. anything that's in > 1.0.1 that can sensibly be merged into 1.0.0). I.e.: > > svn mergeinfo --show-revs=eligible $URL/1.0.1 $URL/1.0.0 > > Can you give that a try?
Thanks for your imput. That's indeed a very interesting approach. I did run a few tests and this seems to output exactly what I need. I'll have to check a few edge cases (e.g. comparing current trunk to latest release, including backports etc.) but this seems very promising! Thanks! Greetings Nico
