Re: Display outstanding backported fixes for each release?

Mark Phippard wrote:
> If we did not keep the STATUS file in the branch, then wouldn't it be fairly easy
> for anyone to see the info you want just by using svn log?

Look at the manual process I described: it starts with how the user has to remember the magic incantation for making 'svn log' find the branch-point of a tag, then copy a revision number from that output into another 'svn log' command. And after doing that, then there is still the 'STATUS' file to append, easy of course for anyone who knows how we run our backporting process, obscure to everyone else.

> Even with your svn log examples, there is still the issue of how you would want
> to display that info on the ROADMAP page.  If the output from log is not suitable

But I said the output of log *is* suitable. Specifically, I wrote, "Under that heading, either inline or links to the verbose text samples above." And I meant it. By "inline," I'm imagining a scrollable sub-window or something; obviously I wouldn't want it to ridiculously overwhelm the whole page. More distilled and polished output would be lovely, of course, but I really don't care about the presentation style; I just care about getting the information visible.

- Julian
Received on 2019-01-03 18:05:40 CET