Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index
The key would be to ask yourself which version would you give your local government office, or largest business in your community, to use. Would you give them 3.5.6 or the brand new 3.6.2 version?
Even our own Release Plan page tells us that ".2 or .3 Early adopters" on the graph.
Sure, there are many improvements in the latest 3.6.x line, but would you stake the "company's" rep. on it? Which current version has the least issues to deal with? Which version has had the most work done to fix the bugs and other issues? Which version is for "critical applications"? Those are the things that must be answered.
Next week 3.5.7 comes out, which is the last of that line. 3.6.3 comes out the first week of November and 3.6.4 come out the first week of December.
I think the real problem is how we may assume that people will always want to try 3.6.x line while it still is in an "early adopter" stage. The download page seems to assume that. Many of us would lake to see that change.
As for Press Releases announcing the newest version of the 3.6.x line, it is a good thing. The only thing we should state somewhere is that there is another line for the "critical application user" if they do not want to use the "more cutting edge" line.
We have two lines and should be proud of that concept. If not, then we should drop the two line development cycle.
I run 3.5.6 and will be moving to 3.5.7, BUT I am waiting till 3.6.4 or 3.6.5 before I make the move over to the 3.6.x line for my default desktop. I may try it on one of my laptops, but not the desktop[s].
Was that not the reason for the two lines? You run the previous line till the newest one gets to the point where it is ready for "all users" and their "critical applications"? That is one reason why I still run the previous line till the newest one gets to the ".4" or ".5" version. That is the way the development cycle was set up. 


On 10/04/2012 08:54 AM, Charles-H. Schulz wrote:

Public announcements are obviously marketing. Someone repeatedly
complaining that software comes with bugs on the marketing list is not
related to marketing.

Charles.
Le 4 oct. 2012 14:48, "Tom Davies" <tomdavies04@yahoo.co.uk> a écrit :


Hi :)
Ahh, sorry.  I didn't realise that public announcements and press releases
have nothing to do with marketing.
Apols and regards from
Tom :)






________________________________
From: Charles-H. Schulz <charles.schulz@documentfoundation.org>
To: "marketing@global.libreoffice.org" <marketing@global.libreoffice.org>
Sent: Thursday, 4 October 2012, 13:30
Subject: Re: [libreoffice-marketing] Stable? Seriously?? Fw:

[tdf-announce] The Document Foundation announces LibreOffice 3.6.2

Tom,

The points you are making are repeated at each release. I cannot really
help if you refuse to understand how we work or how software development
works. But as we are on the marketing list we need to work on marketing

and

not lose our time with recurring rants that are not related to marketing.

We must discipline ourselves if we are on this list and post on it: we

work

on marketing and stay focused on it.

Thank you for your understanding.

Charles.

Charles.
Le 4 oct. 2012 14:01, "Tom Davies" <tomdavies04@yahoo.co.uk> a écrit :


Hi :)
Again.  The only advantage listed for the new release in the newest

branch

of LO is that it's "more stable".  What is it more stable than?  Is it

more

stable than the 3.5.6?

Putting anything mentioning bug-fixes and possible regressions just

makes

people wonder what new bugs and new regressions are likely to appear in
this new release.  Most profitable software companies avoid mentioning

the

possibility that their new software might be buggy and have new

regressions

despite the fact we know that both are likely.  I think we should avoid
mentioning it too until they become more open and honest about the
possibility.


Possibly marginally better to say "latest" rather than "last" unless you
include a date.  "Last" sounds fairly finally and hints that it

happened a

long time ago.  I don't know why.  Both really mean roughly the same

thing

if you look them up in a dictionary.


Again there are tons of advantages to the newest branch but stability is
not one of them.  If people want stability then they are better off

chosing

the latest release in the older branch.  If they want, for example,

better

compatibility with "other" formats and programs (ie such as MS's) then
3.6.x is probably best.


Please.  Can we have those circular or just plain wrong arguments again
about
1.  "I haven't noticed any bugs so far and few people have reported
bugs".  Therefore no bugs really exist because things don't exist until
after they have been discovered.  For example, the water on Mars didn't
exist until there were photos of it.

2.  "Any bugs found need to be reported against the earliest version of
LO/OOo they can be found in."

3.  Rinse and repeat.



1.  "It must be more stable.  It's newer."  Therefore it must be more
stable.

2.  "We must expect new branches  to have more bugs as a result of

having

much greater functionality"
3.  "Older branches focus on bug-fixes and therefore tend to have less

new

added functionality"

4.  Therefore "the only thing we can say about new branches is that they
are more stable."


1.  "All software has bugs."  [Perhaps implying that LO is no more

stable

than java]

Regards from
Tom :)





----- Forwarded Message -----

From: Italo Vignoli <italo.vignoli@documentfoundation.org>
To: announce@documentfoundation.org
Sent: Thursday, 4 October 2012, 12:05
Subject: [tdf-announce] The Document Foundation announces LibreOffice

3.6.2

Berlin, October 4, 2012 - The Document Foundation (TDF) announces
LibreOffice 3.6.2, for Windows, MacOS and Linux, solving bugs and
regressions and further improving the stability of the program for
corporate deployments. The best free office suite ever is quickly
becoming the de facto standard for migrations to free office suites,
thanks to the quickly growing feature set and the improved
interoperability with proprietary software.

The growing number of LibreOffice adoptions by private and public
enterprises is a demonstration of the improvements brought to the

legacy

code by TDF, thanks to over 500 developers who are focusing on

stability

and quality (in addition to new exciting features).

The last public administration to migrate has been the city of

Limerick,

Ireland's third largest city, where LibreOffice is now used on all 450
desktops in use at the city's six main locations including the three
public libraries, the fire department, the municipal museum and the

City

Gallery of Art.

The community behind LibreOffice will gather in Berlin for the second
LiboCon from October 17 to October 19. During three days, company
representatives and volunteers will discuss their experiences, learning

>from each other in the true spirit of the community.

Registration for the conference end on October 8, Registration for the
conference ends on October the 8th. If you want to join in, please
register at this address:

http://conference.libreoffice.org/registration.

LibreOffice 3.6.2 is available for immediate download from the

following

link: http://www.libreoffice.org/download/. Extensions for LibreOffice
are available from the following link:
http://extensions.libreoffice.org/extension-center.

Change logs are available at


http://download.documentfoundation.org/libreoffice/src/bugfixes-libreoffice-3-6-1-release-3.6.2.1.log

(fixed in 3.6.2.1) and


http://download.documentfoundation.org/libreoffice/src/bugfixes-libreoffice-3-6-1-release-3.6.2.2.log

(fixed in 3.6.2.2).

Short link to The Document Foundation blog: http://wp.me/p1byPE-jV.

--
Italo Vignoli - Director
phone +39.348.5653829 - skype italovignoli
email italo.vignoli@documentfoundation.org
The Document Foundation
Zimmerstraße 69, 10117 Berlin, Germany
Rechtsfähige Stiftung des bürgerlichen Rechts
Legal Details: www.documentfoundation.org/imprint

--
Unsubscribe instructions: E-mail to

announce+help@documentfoundation.org

Problems?

http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/

List archive: http://listarchives.documentfoundation.org/www/announce/





--
Unsubscribe instructions: E-mail to

marketing+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/marketing/
All messages sent to this list will be publicly archived and cannot be
deleted



--
Unsubscribe instructions: E-mail to marketing+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/marketing/
All messages sent to this list will be publicly archived and cannot be

deleted





--
Unsubscribe instructions: E-mail to marketing+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/marketing/
All messages sent to this list will be publicly archived and cannot be
deleted





--
Unsubscribe instructions: E-mail to marketing+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/marketing/
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.