On 12/06/2012 08:56 AM, Jürgen Spitzmüller wrote:
2012/12/6 Jean-Marc Lasgouttes<lasgout...@lyx.org>:
For conferences/journals we probably do not have a choice (unless some
people rely on old layouts).
My idea would be to provide a new layout with a new name
(journalx-new.layout), then lyx2lyx could change this to
journalx.layout in the new major release (and also the old
journalx.layout) and revert accordingly.
This proper conversion would also prevent that people cannot process
anymore their old paper because the layout names change.
That seems like the obvious thing to do.
So a similar suggestion would be:
(i) With layouts that change versions like this, the layouts themselves
should have version numbers, corresponding to that of the class file. So
we'd have acmsiggraph-200.layout, and acmsiggraph-201.layout, or whatever.
(ii) For a major release (e.g., 2.1.0), we will provide out of the box
support only for the most recent version, dropping support for older
layouts. I.e., we'll move them to some "layout attic", and people who
want to use their old files with old layouts can always get them from
git or whatever. (The old layouts could always be shipped, but not
installed by default.)
The alternative here is Liviu's "deprecated" suggestion. But if we kept
all of these around, the already unmanageable layout list would get even
worse. (I keep thinking about some way of filtering that list.)
(iii) For minor releases (e.g., 2.0.6), if the class file changes, we
will provide a new layout file, but continue to ship the old one, as
well. This would mean that Uwe's new files should be versioned for 2.0.6.
Richard
