Le 04/07/2015 22:09, Benedict Holland a écrit :
I suppose, that said, I don't mind testing lyx on various systems but
the 2.0.8 branch is old and is in release for what, at least a year?
What additional testing, apart from that, is required? Is there a spec
sheet for various usability tests that
On 07/04/2015 04:09 PM, Benedict Holland wrote:
Right. I deeply question that logic though. The fact that a corrupted
save bug was fixed is sort of a game changer from a usability
perspective. I mean, if it wasn't well known, well documented, or
fixed, I might say that it makes sense but as it
Right. I deeply question that logic though. The fact that a corrupted save
bug was fixed is sort of a game changer from a usability perspective. I
mean, if it wasn't well known, well documented, or fixed, I might say that
it makes sense but as it stands, releasing code that has a known
catastrophic
On 07/02/2015 03:24 PM, Benedict Holland wrote:
Just curious, why are we testing old versions of an application with
known catastrophic bugs? Wasn't the uncorrupted save feature
implemented in the 2.1 branch? Also, I have been using the 2.1.3
exclusively for a long time and I admit that I am a
Just curious, why are we testing old versions of an application with known
catastrophic bugs? Wasn't the uncorrupted save feature implemented in the
2.1 branch? Also, I have been using the 2.1.3 exclusively for a long time
and I admit that I am a power user. It is stable as anything I use and when
On Thu, Jul 2, 2015 at 11:57 AM, Jean-Marc Lasgouttes
wrote:
> Dear all,
>
> Ubuntu trusty 14.04, the long term support version, currently only has LyX
> 2.0.6. While it is not possible in a LTS version to upgrade to the latest
> LyX version[*], it has been decided to update to the latest 2.0.x ve
Dear all,
Ubuntu trusty 14.04, the long term support version, currently only has
LyX 2.0.6. While it is not possible in a LTS version to upgrade to the
latest LyX version[*], it has been decided to update to the latest 2.0.x
version, that is 2.0.8.1.
This is now accessible in the proposed ch
