Discussion:
LyX 2.0.8.1???
Richard Heck
2014-05-29 15:32:47 UTC
Permalink
Where are we after Enrico's latest?

I suppose if need be I can always release a 2.0.8.2.....

Richard
Pavel Sanda
2014-05-29 17:30:26 UTC
Permalink
Post by Richard Heck
I suppose if need be I can always release a 2.0.8.2.....
Looks like reasnoble way to go. Pavel
Georg Baum
2014-05-29 19:13:22 UTC
Permalink
Post by Richard Heck
Where are we after Enrico's latest?
I suppose if need be I can always release a 2.0.8.2.....
Looks good. The recent developments made me think about lyx2lyx tests again,
and I'll try to come up with a proposal. After we have that, we can think
about further beamer fixes, but without automated tests I personally would
not dare to do more changes to the code. However, this will take some more
weeks, and this is too late for 2.0.8.1.


Georg
Jürgen Spitzmüller
2014-05-30 06:34:48 UTC
Permalink
Post by Georg Baum
Post by Richard Heck
Where are we after Enrico's latest?
I suppose if need be I can always release a 2.0.8.2.....
Looks good. The recent developments made me think about lyx2lyx tests again,
and I'll try to come up with a proposal. After we have that, we can think
about further beamer fixes, but without automated tests I personally would
not dare to do more changes to the code. However, this will take some more
weeks, and this is too late for 2.0.8.1.
I have a major rewrite of the frame argument routine in the making (which
attempts to remove all known restrictions of the current method). But it might
need some more time to get it finished, and it certaily will require testing
before it goes into a stable release.

Jürgen
Post by Georg Baum
Georg
Richard Heck
2014-05-30 15:02:57 UTC
Permalink
Post by Jürgen Spitzmüller
Post by Georg Baum
Post by Richard Heck
Where are we after Enrico's latest?
I suppose if need be I can always release a 2.0.8.2.....
Looks good. The recent developments made me think about lyx2lyx tests again,
and I'll try to come up with a proposal. After we have that, we can think
about further beamer fixes, but without automated tests I personally would
not dare to do more changes to the code. However, this will take some more
weeks, and this is too late for 2.0.8.1.
I have a major rewrite of the frame argument routine in the making (which
attempts to remove all known restrictions of the current method). But it might
need some more time to get it finished, and it certaily will require testing
before it goes into a stable release.
We have people asking for 2.0.8 now, so I think I'll go ahead and
release and do an update later, if need be.

Richard
José Matos
2014-05-30 15:15:59 UTC
Permalink
Post by Richard Heck
We have people asking for 2.0.8 now, so I think I'll go ahead and
release and do an update later, if need be.
Richard
It makes sense. :-)

In the same line when do you think that it would be reasonable to release 2.1.1?

I am asking this because IMHO we are starting to have some fixes that are worth to have in a stable release. Are there any blockers right now?

Also at the same time the release of 2.0.8.1 creates a paradox in the sense that we have stable code available for versions 2.0 and 2.1 that is only released in the older version. :-) Of course the world is not black and white and this is a simplistic description of reality.

Regards,
--
José Abílio
Enrico Forestieri
2014-05-29 21:11:13 UTC
Permalink
Post by Richard Heck
Where are we after Enrico's latest?
I am now able to correctly load and compile the attached beamer
document with LyX 2.2, but I cannot do the same with 2.1.
However, if I copy lyx_2_1.py from 2.2 to 2.1, then it succeeds.
So, it seems that something was not backported to 2.1 (and maybe
also to 2.0)?

I also think that you forgot to cherry-pick da75d319.
Post by Richard Heck
I suppose if need be I can always release a 2.0.8.2.....
Yes, that seems a viable path.
--
Enrico
Richard Heck
2014-05-29 22:19:10 UTC
Permalink
Post by Enrico Forestieri
Post by Richard Heck
Where are we after Enrico's latest?
I am now able to correctly load and compile the attached beamer
document with LyX 2.2, but I cannot do the same with 2.1.
However, if I copy lyx_2_1.py from 2.2 to 2.1, then it succeeds.
So, it seems that something was not backported to 2.1 (and maybe
also to 2.0)?
I've just copied it over, then. I tried cherry-picking everything, but
since some later
stuff has been done that changed earlier stuff, I kept getting
conflicts. So I gave up
and did it the dirty way.

Richard
Continue reading on narkive:
Loading...