Re: Display outstanding backported fixes for each release?

> On Dec 15, 2018, at 2:47 PM, Julian Foad <julianfoad_at_apache.org> wrote:
>
> Branko Čibej wrote:
>> But before we start on something I'd like to see some proposals on query
>> language, so that we don't implement ourselves into a corner. I'd
>> propose this as a starting point:
>>
>> https://www.mercurial-scm.org/repo/hg/help/revsets
>
> Yes. To be clear, I was rather intending this suggestion might be taken as a nudge towards developing some structured queries. Maybe I'll have a read through that and see how it could be adapted to Subversion, some time.

Just a meta comment ...

I am not 100% clear what you would like to see, so I am probably not alone. Maybe it would help if you put something manual in place first. Then that would give people something to look at and think about how similar information could be produced in a more automated manner.

I personally think when you start talking about putting information on a website that I think the abstraction of using something like the Jira issues would be more useful than commits. This project does not currently use Jira consistently enough that it would be an option, but aside from the occasional bug that is fixed with a single commit, I just do not think anything that is commit based will be useful. You might as well just use svn log output at that point if that is all you want. Think of a "feature" like shelving. That is basically one issue to show in a list, but you might have done 30-40 commits to implement it. Seeing the commits is too low level to be useful on the website ... IMO.

Anyway, that is why I would suggest you start doing this manually. If you start with svn log output and find yourself omitting a lot of commits that is going to give you a lot of hints about what would be needed in order to ever automate this.

Mark
Received on 2018-12-15 20:56:14 CET