> On Aug 10, 2018, at 7:40 AM, Geert Janssens <geert.gnuc...@kobaltwit.be> > wrote: > > Op vrijdag 10 augustus 2018 16:02:56 CEST schreef Derek Atkins: >> Geert, >> >> Geert Janssens <gjanss...@code.gnucash.org> writes: >>> - <li><a >>> href="https://bugzilla.gnome.org/show_bug.cgi?id=796484";>Bug 796098 - V >>> 3.1 Missing images in Tutorial and Concepts Guide in PDF and Online Help >>> pages.</a></li> - <li><a >>> href="https://bugzilla.gnome.org/show_bug.cgi?id=796484";>Bug 795980 - >>> Void Reason Has No Visible Purpose.</a></li> + <li><a >>> href="https://bugzilla.gnome.org/show_bug.cgi?id=796098";>Bug 796098 - V >>> 3.1 Missing images in Tutorial and Concepts Guide in PDF and Online Help >>> pages.</a></li> + <li><a >>> href="https://bugzilla.gnome.org/show_bug.cgi?id=796980";>Bug 795980 - >>> Void Reason Has No Visible Purpose.</a></li> >> Why not also change the links to bugs.gnucash.org? >> >> -derek > > Lack of time at the moment I did the corrections. As someone (I believe it > was > Adrien) suggested it would be nice to update *all* urls, also for older > gnucash releases. That's a lot of news files. > > And as I mentioned in another reply, I was being conservative because maybe > some urls are not for gnucash bugs. Obviously most of them would but I don't > remember whether we referred to unfixed Gtk or Gconf or whatever bugs in > known > issues sections. > > Reconsidering it's probably worth doing the rename in one go for all website > pages potentially creating some minor collateral damage. If we create an > invalid link in the process, we can change those back to bugzilla.gnome.org > <http://bugzilla.gnome.org/> > whenever someone stumbles on one. Unless you have another idea ?
Sed will make short work of the global change on the website but we can’t use it on Github releases; those would all have to be changed by hand. Fortunately there are only 25-30 of them. I doubt that there are any not-GnuCash bugs in the release announcements, at least from the 2.2 on. In order to appear in a release announcement a bug would have to have been the subject line of a commit note, and that’s unlikely to happen unless it’s a GnuCash bug. All of which said, there’s a certain air of rewriting history to changing all of the bug links to bugs.gnucash.org <http://bugs.gnucash.org/>. I see no problem with changing the 3.2 announcement; in fact, I like that because it will keep me from screwing up the 3.3 announcement by copying the gnome URL and forgetting to fix it. I can sort-of see changing 3.0 and 3.1 as well. The further back in time the announcement the less sense it makes to me to change. At some point it makes more sense to just remove the announcements. The historical record of what happened when is preserved in git history and in the ChangeLog files. I don’t see much benefit to maintaining it all on the website as well. Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
