On Mon, 25 Sep 2017 16:12:31 +0200 Mateusz Loskot <mate...@loskot.net> wrote:
ML> On 25 September 2017 at 16:01, Vadim Zeitlin <vz-s...@zeitlins.org> wrote: ML> > On Sat, 23 Sep 2017 23:43:03 +0200 Mateusz Loskot <mate...@loskot.net> wrote: ML> > ML> > ML> On 23 September 2017 at 23:31, Mateusz Loskot <mate...@loskot.net> wrote: ML> > ML> > ML> > ML> > I'm experimenting with auto-generated change log. ML> > ML> > ML> > ML> > https://github.com/SOCI/soci/blob/master/CHANGELOG.md ML> > ML> > This looks too verbose/long to be useful to me. ML> > [...] ML> > IMO, be to highlight important changes and not list all of them, ML> ML> Although I agree about the optimal way to achieve it, my point is that ML> something is better than nothing and better is enemy of good. But we don't have nothing. Err, I mean, we do have something. I'd just convert the existing CHANGES to markdown (and maybe rename it to CHANGES.md) but otherwise keep it as it is. Should I do this? ML> > ML> Alternatively, CHANGES file is converted to release notes maintained ML> > ML> manually and included in the documentation: ML> > ML> ML> > ML> For example, http://www.mkdocs.org/about/release-notes/ ML> > ML> > This (or current SOCI changelog, for that matter) looks more useful to me. ML> ML> I can't promise enough steam will be left to do it. I can try to review/complete the existing changelog if it can help. VZ
pgpbqBQK6qWZ6.pgp
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ soci-devel mailing list soci-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-devel
