Re: [MirageOS-devel] Updating TROVE or maintaining a remote

[Thomas Leonard <talex5@xxxxxxxxx>]

On 10 August 2015 at 11:02, Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx> wrote:
>>> - lint release: check that all tags on a repo have a non-empty GitHb 
>>> release, check that there's a CHANGES{.md} file, check that we have some 
>>> tests.
>>
>> Can we provide the "changes" information automatically somehow? It
>> seems that it just duplicates the release notes and/or the Git
>> history, and causes unnecessary merge conflicts.
>>
>> e.g. if you go to
>> https://github.com/talex5/mirage-trace-viewer/releases you'll see a
>> list of changes for each release, but I don't maintain a separate
>> changes file and I don't feel I'm losing anything by doing this.
>
> As long as there is a place where we can see the release changes (not `git 
> log`) I'm happy it to be anywhere. However https://mirage.io/releases/ is 
> looking at the GitHub release and I prefer to have it as a file in the repo 
> to be able to grep it for API changes (very useful when updating opam 
> dependency constraints), so I try to maintain both.

This might work for listing API changes (while excluding bug fixes and
other implementation-only details):

  git log  **/*.mli

That does depend on having an mli file for each module, but I think
all the Mirage libraries do that anyway.

> Thomas
>
>>
>>> - ideally, we should start to have "gatekeepers" for all of our projects. 
>>> If you are a gatekeeper, having a view for all issues/PR for these projects 
>>> would be useful.
>>>
>>> Thomas
>>>
>>> [1]:  https://github.com/mirage/mirage/issues/381
>>> [2]: https://github.com/mirage/irmin/issues/107
>>> [3]: https://github.com/mirage/mirage/issues/203
>>> [4]: https://github.com/samoht/opam-release
>>>
>>>
>>>>
>>>> Any thoughts on this?  Christophe is working on this infrastructure right 
>>>> now, and we're keen to get something up and running in August.  I'm 
>>>> particularly interested in missing workflow features that would make your 
>>>> life easier as MirageOS developers and users.
>>>>
>>>> [1] https://github.com/ocaml/opam-repository/pull/4625
>>>> [2] https://github.com/mirage/mirage-www/blob/master/TROVE
>>>>
>>>> thanks
>>>> Anil
>>>> _______________________________________________
>>>> MirageOS-devel mailing list
>>>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>>
>>>
>>> _______________________________________________
>>> MirageOS-devel mailing list
>>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>
>>
>>
>> --
>> Dr Thomas Leonard        http://roscidus.com/blog/
>> GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA
>



-- 
Dr Thomas Leonard        http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel