LibreOffice Still?

Hi,

TomD wrote

In reply to
this post
<http://nabble.documentfoundation.org/LibreOffice-Still-td4117297i100.html#a4124368>
by alphacrash

Hi :slight_smile:
It's not quite that simple :frowning:

With Fresh the new features probably will work just fine. They have been
about as thoroughly tested as possible. It's any pre-existing stuff that
could be broken.

If it was just the new features that were possibly broken then there would
be no real worry about using Fresh. people could just carry on using
LibreOffice in the same way they were doing previously.

The problem is often that people try to carry on doing things and suddenly
find that it doesn't work anymore because it's broken in "Fresh". Often
the simplest fix is just to go back to "Still" and then magically
everything works just fine for them again.

However, WARNINGS MUST BE SIMPLE. Failure to make warnings simple is an
explicit decision to cause harm.

The conflict comes from two different sources:

1. It is clear from Florian's and Sophie's comments that there is lack of
programmers and a lack of users of the current version being developed.

2. END USERS expect all the previous functionallity to which they have
become accustomed.

I have to say at this point the move to a nomenclature that conceals the
risk, or makes discovery of the risk a multi-step proccess appears to be an
attempt to mask the conflict as opposed to addressing the conflict directly.

*SUGGESTION: The term you use for the Old Stable equivalent should be
guarranteed to contain all previous functionality. (With the exception of
pre- advertised discontinuations such as defunct word processor formats)*

Warning: This suggestion could affect your release plans.

The question is: HOW IMPORTANT ARE YOUR USER'S RELIANCE ON LIBRE OFFICE
FEATURES ?

It should be stated that Microsoft benefits from ANY perception of
UNRELIABILITY and resulting time loss in LibreOffice.

I'll give a metric here regarding the WARNING of RISK that most users would
want to know.

CRITICAL DOCUMENTS:

*- Legal documents:* that are due by a specific time in a specific format or
you lose the case. /Users cannot afford to be surprised by the loss of a
time saving feature or something that alters the format or appearance of the
document in any manner or that document may be rejected. To be surprised
that functionality has dissappeared and then have to go through each line to
verify that the document will only serve the purpose of making LO too
unreliable to use. /

*- Business documents:*/ that are due by a specific time in a specific
format with specific content or you lose your job. These are often
documents developed over a time that spans releases. To be surprised that
functionality has dissappeared and then have to go through each line to
verify that the document will only serve the purpose of making LO too
unreliable to use. /

*- Medical documents: */ that must contain specific information and must be
documents are long. To be surprised that functionality has dissappeared and
then have to go through each line to verify that the document will only
serve the purpose of making LO too unreliable to use./

Regards.

Gentlemen and Ladies,

I have a madly insane idea - when bug fixes/updates are applied to a
project - simply HIDE or REMOVE the unpatched version from the end user's
accessible locations.

I know that the UNPATCHED version needs to remain, for rollbacks or other
badly done "updates" but, for heaven's sake if you insist on keeping the
unpatched version, call it "PackageName - Unpatched" or better yet give the
patched version a new name.

For, example: LibreOffice1 (the original version) LibreOffice1.1 (an updated
version) and finally, (LibreOffice1.1.1 -the version with all the latest
bug-fixes, enhancements, etc.).

When other platforms are also supported: refer to the program by appending
the name of the platform to the package name, i.e LibreOffice1.1.1 for
Android LibreOffice1.1 for Windows, etc.

Hi :slight_smile:
It's a good idea. It's already done. Previous versions of a branch are
hidden away in the archives.

Of course some people still need them when something is broken in a newer
release but only IF that proves to be a blocker for them.

The platform is mentioned in the download name, in much the way you
describe. When i go to the download page it tries to give me
"xx_Linux_deb_xx" when i ask it to give me the Windows version the name
changes to "xx_Win_xx". So it's a good idea and one that is already done.
Regards from
Tom :slight_smile: