On Mar 3, 2017, at 5:49 PM, Ron W <ronw.m...@gmail.com> wrote: > > I would argue that wiki pages, ticket changes and ticket attachments have > parent artfacts. For wiki pages, it would be the most commit of that page.
Okay, but what about new wiki pages? What is *their* parent? Ditto new tickets and new tech notes. Maybe my proposed tip-of-trunk rule should apply here, too. > bug fixes to 2.0 won't be version number capped.) The existence of Fossil 2.1 needn’t prevent making fixes to Fossil 2.0. Just use the same version numbering scheme as SQLite: 2.0.1, etc. What it *does* mean is that we can’t add new *features* to Fossil 2.0 after 2.1 comes out without breaking the version numbering semantics, but I don’t see how that’s even on the table given that there seems to be no interest in making Fossil 2.0 a long-term-stable release, with features backported to it. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
