On Tue, Jun 7, 2016 at 12:10 AM, Andrew Parsloe <apars...@clear.net.nz> wrote: > On 7/06/2016 9:50 a.m., Richard Heck wrote: >> >> On 06/06/2016 03:33 PM, Georg Baum wrote: >>> >>> Jean-Marc Lasgouttes wrote: >>> >>>> Le 05/06/2016 à 21:05, Guillaume Munch a écrit : >>>>> >>>>> Yet, most of the file format changes are very simple. I wonder whether >>>>> one could introduce a single compilation variable to disable them, >>>>> and ask developers to enclose file-format-specific code between the >>>>> corresponding #ifdefs. (For instance in my last file format change all >>>>> that was needed to be enclosed was the parsing code.) This would allow >>>>> the release of "master versions without file format changes", either as >>>>> nightlies or as official "x.5" versions as Pavel suggested by Pavel in >>>>> another message (without having to maintain three branches in >>>>> parallel). >>>> >>>> This looks too complicated to me. And eventually there will be changes >>>> that cannot be treated like that, and all the previous work on small >>>> changes >>>> will be useless. >>>> >>>> Note that that stable nightlies could be updated with lyx2lyx code for >>>> new master versions in parallel with master. >>> >>> Or we could add a mode that calls lyx2lyx automatically after saving, so >>> that effectively the master version would use the old file format. This >>> would probably work fine as long as no new features are used. >> >> Yes, but do we want to warn people then not to use new features? I think >> it would just confuse people for us to tell them to test master but not >> to use some new features if they want to be able to go back to stable. >> >> Richard >> > As a potential user-tester I've followed this discussion with interest. I > can't imagine downloading and installing LyX daily, but I can imagine doing > this each month and using the resulting installation as my working LyX (as I > did for the alphas and betas of 2.2.0), therefore with all features turned > on and potential unreadability in earlier versions. > This is how I often use the devel builds as well --- switch to a devel build and work with it for some time. I think other testers broadly do the same when there is some new killer feature in master, but it isn't clear when a new release is due.
Liviu > Andrew > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus >
