[Pkg-lyx-devel] Fwd: [ANNOUNCE] LyX 1.6.8 is released!
Rainer Dorsch
rdorsch at web.de
Mon Dec 6 16:11:15 UTC 2010
Hi Sven,
thanks for replying.
Am Monday, 6. December 2010 schrieb Sven Hoexter:
> On Wed, Nov 24, 2010 at 10:40:48PM +0100, Rainer Dorsch wrote:
>
> Hi,
>
> > thanks for the quick reply. Is anybody packaging it for sid? At least
> > users could pull the package from sid, if they want...
>
> IMHO we should release squeeze and then continue with
> 2.0.0something/beta/rc early next year. I won't touch anything != RC due
> to time constraints this year anyway but that shouldn't hold someone else
> back from preparing 1.6.8 or 2.0.0something for experimental if he feels
> like doing so.
> I don't see any value to continue with 1.6.x releases for unstable so deep
> in the freeze. With a LyX 2.0.0 release around the corner I think we should
I probably have to compile my own version of 1.6.8 as soon as Ubuntu ships
1.6.8 (if they do). The reason is I work together with other people on a large
LyX document maintained in SVN. Since LyX stores the version information into
the document, having people working with different minor versions makes it
almost unavoidable to see merge conflicts (assume person A working with 1.6.8,
person B modifying with 1.6.6, person C modifying with 1.6.7 concurrently).
Therefore all authors have the agreement to work with the same minor version
(in general what Ubuntu distributes in the latest distro).
I do not know though how much other users there are out there which would
benefit for whatever reasons from a newer 1.6.8 version. Ideally it would go to
unstable once squeeze is released and then propagates via the now official
backports service to the (some) users
http://backports.debian.org/
(I do not know though how backports works in detail, probably there is more
required than a 10 day quarantine).
> help and and distribute that via unstable as early as possible to help
> upstream to get a solid release done because we're at that point far away
> from the squeeze+1 release.
I fully support you 2.0.0 plans, I would start putting them in experimental
though until 2.0.0 is released, otherwise there is a good chance that end up
in testing and interferes with 1.6.8 migrating to testing and backports.... or
the rolling release model (constantly usable testing). If that gets going,
rolling release users probably do not want to run 2.0.0 beta on their
production systems...
I hope that building and uploading 1.6.8 is little work, given that only minor
patches went in. I agree though if LyX maintainers are short of time,
supporting 2.0.0 makes more sense, even when quite a number of users are not
jumping to LyX 2.0.x immediately.
Thanks,
Rainer
--
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdorsch at web.de
jabber: rdorsch at jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/attachments/20101206/588dc7bb/attachment.pgp>
More information about the Pkg-lyx-devel
mailing list