[vtk-developers] Thoughts on changelog maintenance?

[David E DeMarle]

I support anything that move us further away from the
centralized/semi-manual way we make releases now and towards the perfect
world that David Gobbi recommends. Automating releases further will cut
down on the time it takes to put them together and make it feasible to do
them very frequently and on a regular schedule.

Benefits of the current system are, besides the convenience for developers
that David mentioned, are that the "tell us about your change?" emails are
good karma and a nice way to reach out to new developers, and that from
time to time the handcrafted release note announcements come out well. I
for one am willing to trade these for multiple releases per year.

I vote for optional md file per commit in a directory for the time being.
To get beyond that (which I think we should do) we'll have to enforce no
merges without accompanying issues or something like that to train us all
over to an ideal workflow.







David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Tue, Nov 7, 2017 at 2:54 PM, David Gobbi <david.gobbi at gmail.com> wrote:

> In a perfect world, the changelog would be generated automatically from
> all of the issues that were closed between releases.  That would require
> much more frequent use of the issue tracker (which would be a good thing).
> Issues and MRs would continue to be tied together via gitlab references.
>
> If someone wanted to see the latest changelog for master, they would just
> go to gitlab's list of closed issues.  The changelog put into the source
> upon release would just be an md file that was a copy of the same.
>
> Overall, though, I'm not sure if a new changelog mechanism is even needed.
> The current workflow (summarizing our changes at release time) already
> seems pleasantly lightweight.
>
>  - David
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtk-developers
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20171107/41325f09/attachment-0001.html>