Hi, On 3/22/20 10:59 AM, intrigeri wrote: [...] > Zooming further into what we heard about (C), the changelog address > these needs: > > C.1 Need more details than what the release notes include, > i.e. the "how" information > > C.2 Need easy access to the aggregated information across multiple > releases > > Here's something I believe would address these 2 needs: > > - Write a program that fetches from GitLab the list of issues and MRs > closed by a specified set of releases, and presents them together, > grouped by milestone, via 1 single user operation (C.2). > > - And for C.1, sometimes issue/MR titles don't include this > information, but commit messages do. So this program could have > a mode in which, for each MR, it displays the corresponding > commit messages. > > I suspect this program exists already. If not, it should be pretty > cheap to write (modulo perhaps some issue <-> MR matching and > de-duplication, if we feel fancy). > > Once we have this program, it becomes very cheap for the RM to paste > its output as-is in the changelog file, and/or for us to publish this > information over HTTPS somewhere (so one can click on links to go > explore issues/MRs/commits further). > > This would solve 90% of my use case and I know how to deal via Git > with the remaining 10%. > > Muri, would this be good enough for you?
Yes! cheers, muri _______________________________________________ Tails-dev mailing list [email protected] https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
