Hi Geert,
Thanks very much for actioning my patch. I’ll update the wiki Documentation_Update_Instructions to add a note saying bug version should be git-maint if patch should be included in the next stable release. Is it also correct to add: bug version should be git-master if the documentation patch applies to the next unstable release? Shall I also add to http://wiki.gnucash.org/wiki/Release_Schedule something like: Stable releases have an odd version number. E.g. 2.4, 2.6, 2.8… Unstable releases have an even version number E.g. 2.5, 2.7, 2.9… and are only intended for developers working on longer term modifications. This isn’t actually stated anywhere that I have found. Regards, Chris Good From: GnuCash (GNOME Bugzilla) [mailto:[email protected]] Sent: Friday, 20 March 2015 2:45 AM To: [email protected] Subject: [Bug 744918] Update Help Manual for Mike Alexanders mods to Advanced Portfolio Rpt <https://bugzilla.gnome.org/page.cgi?id=describeuser.html&login=info%40kobaltwit.be> Geert Janssens changed bug 744918 <https://bugzilla.gnome.org/show_bug.cgi?id=744918> What Removed Added Version git-master git-maint Comment # 7 <https://bugzilla.gnome.org/show_bug.cgi?id=744918#c7> on bug 744918 <https://bugzilla.gnome.org/show_bug.cgi?id=744918> from <https://bugzilla.gnome.org/page.cgi?id=describeuser.html&login=info%40kobaltwit.be> Geert Janssens Lastly a small bug management nit: if you create a patch that should be included in the next stable release, please set the version to git-maint. I almost committed your patch to master, in which case it would only have appeared starting from gnucash 2.8.0 (still a few years away). Thanks again however for your contributions! _____ You are receiving this mail because: * You reported the bug.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
