Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi :)  
On my own machine at home and at work I think it is a good policy to download and install new 
versions of new branches asap.  Preferably even at beta-release stage (ie pre-release).  That 
allows me to test out all the features i think i use and play around to see if it feels alright.  

Then i can post bug-reports while the devs are still most keen and most focussed on fixing things 
and smoothing it out.  It's not always quick to fix but it helps the devs.  It might be really 
great if people could test out a new branch at pre-release stage and then go through some of the 
existing bug-reports to quickly see if they are still a problem with the newer release.  That might 
really help the devs.  

Of course on colleagues machines i stick with the stable branch.  Any release after x.x.3 is much 
more stable, with x.x.6 being about as rock-solid as it's possible to get.  

The question is are you happy to just sit&hope that someone else happens to notice issues that you 
personally find crucial?  I'd rather have an active say in pushing forwards things that i want to 
see fixed.  

After having a test drive i can always reinstall the older version if i need to/  "Simples" :)  

Errr, in the case of the 4.0.0 i got really lucky and found everything i cared about just seems to 
work!  WooHooo :D
Regards from 
Tom :)  






________________________________
From: M Henri Day <mhenriday@gmail.com>
To: Virgil Arrington <cuyfalls@hotmail.com> 
Cc: users@global.libreoffice.org 
Sent: Monday, 22 April 2013, 19:13
Subject: Re: [libreoffice-users] How to downgrade from 4.0.2. to 3.6.6


2013/4/22 Virgil Arrington <cuyfalls@hotmail.com>

Bill,

I hate to say it, but that was my experience as well with 4.0. There was
an important feature (to me at least) that worked well on 3.6 but no longer
worked in 4.0. I found the regression to be especially distressing.

I simply uninstalled 4.0, and reinstalled 3.6. If I recall, the uninstall
process (I also use Win7) did not delete the 4.0 user profile "users\(your
user name)\AppData\Roaming\**Libreoffice\4.0\etc, so I was able to copy
what I needed to the Libreoffice\3.0\etc. user profile after installing 3.6.

I've decided to be more deliberate about upgrading in the future. Study
the release notes and check out bug reports. LO 3.6 works very well for me,
so I probably won't upgrade until the latest/greatest has a feature I
really need or fixes bugs that have bothered me in the past.

Virgil


<...>

Bill and Virgil, it might be helpful to the developers if you could point
out the specific bugs/missing features, etc, that have been causing you
problems in 4.0....

Henri

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.