Downgrading

>
> Time based release trains have been shown to produce the best quality
> Free software. A time based release is one that does not wait for
> either features, or bug fixes - but is based (as purely as possible)
> on time. This enforces discipline in introducing fixes, gives
> predictability, and allows more regular releasing. It is also the case
> that we will necessarily release earlier, and then rapidly,
> incrementally bug fix releases based on the previous stable version.
> Thus if you have a need for the very highest quality version, it can
> make sense to defer a move until the first or perhaps second minor
> point release.
>
> Synchronizing our time based release schedule with the wider Free
> Software ecosystem also has huge advantages, by getting our new
> features, out to users as quickly as possible - with a minimum of
> distribution cycle lag. In consequence, we will aim at six monthly
> releases, and over time nudge them to align well with the March /
> September norms.
>

> I have downgraded my LO program from 3.5.0 to 3.4.5, as the lack of
> autospellcheck and recent documents in 3.5.0 were real show stoppers, and not
> being able to find any workarounds.
>
> I feel that 3.5.0 was released either with inadequate testing, or before it
> was ready for release. No matter, its no longer a problem for me.
>
> Thank you for the experience, and all those who suggested workarounds.
>
> Sharon.

> Hi Sharon,
>
> LibreOffice is released on a time schedule. This is more fully
> explained here:
> http://wiki.documentfoundation.org/ReleasePlan
>
> Included in this document is the following:
>>
>> Time based release trains have been shown to produce the best quality
>> Free software. A time based release is one that does not wait for
>> either features, or bug fixes - but is based (as purely as possible)
>> on time. This enforces discipline in introducing fixes, gives
>> predictability, and allows more regular releasing. It is also the
>> case that we will necessarily release earlier, and then rapidly,
>> incrementally bug fix releases based on the previous stable version.
>> Thus if you have a need for the very highest quality version, it can
>> make sense to defer a move until the first or perhaps second minor
>> point release.
>>
>> Synchronizing our time based release schedule with the wider Free
>> Software ecosystem also has huge advantages, by getting our new
>> features, out to users as quickly as possible - with a minimum of
>> distribution cycle lag. In consequence, we will aim at six monthly
>> releases, and over time nudge them to align well with the March /
>> September norms.
>>
> I generally wait until the 3.x.1 or 3.x.2 versions are out. If someone
> is not aware of how the release schedule for LibreOffice works, it is
> very easy for a person to reach the conclusion that you did that 3.5.0
> wasn't adequately tested or ready for release.
>
> Don
>
>
> On 02/21/2012 12:02 PM, sharon kimble wrote:
>> I have downgraded my LO program from 3.5.0 to 3.4.5, as the lack of
>> autospellcheck and recent documents in 3.5.0 were real show stoppers,
>> and not
>> being able to find any workarounds.
>>
>> I feel that 3.5.0 was released either with inadequate testing, or
>> before it
>> was ready for release. No matter, its no longer a problem for me.
>>
>> Thank you for the experience, and all those who suggested workarounds.
>>
>> Sharon.
>

> I am very sceptical about the so-called benefits of
> releasing on a strict time-schedule.
> The process seems to favour new features over bug fixes.
> I thought the old way was better - release it when it's ready.
>
> However, it seems to be the way things are at present,
> so I guess we have to live with it!
>
> cheers,
>
> Chris
>
> ____________________________________________________________
>
> Chris Morgan
>
> Software Manager
> Lynx Information Systems Ltd
> Tel: +44 (0)20 8780 2634
> Email: [hidden email]
> Web: http://www.lynxinfo.co.uk
> ____________________________________________________________
>
>
> On 21/02/2012 19:55, Don C. Myers wrote:
> > Hi Sharon,
> >
> > LibreOffice is released on a time schedule. This is more fully
> > explained here:
> > http://wiki.documentfoundation.org/ReleasePlan
> >
> > Included in this document is the following:
> >>
> >> Time based release trains have been shown to produce the best quality
> >> Free software. A time based release is one that does not wait for
> >> either features, or bug fixes - but is based (as purely as possible)
> >> on time. This enforces discipline in introducing fixes, gives
> >> predictability, and allows more regular releasing. It is also the
> >> case that we will necessarily release earlier, and then rapidly,
> >> incrementally bug fix releases based on the previous stable version.
> >> Thus if you have a need for the very highest quality version, it can
> >> make sense to defer a move until the first or perhaps second minor
> >> point release.
> >>
> >> Synchronizing our time based release schedule with the wider Free
> >> Software ecosystem also has huge advantages, by getting our new
> >> features, out to users as quickly as possible - with a minimum of
> >> distribution cycle lag. In consequence, we will aim at six monthly
> >> releases, and over time nudge them to align well with the March /
> >> September norms.
> >>
> > I generally wait until the 3.x.1 or 3.x.2 versions are out. If someone
> > is not aware of how the release schedule for LibreOffice works, it is
> > very easy for a person to reach the conclusion that you did that 3.5.0
> > wasn't adequately tested or ready for release.
> >
> > Don
> >
> >
> > On 02/21/2012 12:02 PM, sharon kimble wrote:
> >> I have downgraded my LO program from 3.5.0 to 3.4.5, as the lack of
> >> autospellcheck and recent documents in 3.5.0 were real show stoppers,
> >> and not
> >> being able to find any workarounds.
> >>
> >> I feel that 3.5.0 was released either with inadequate testing, or
> >> before it
> >> was ready for release. No matter, its no longer a problem for me.
> >>
> >> Thank you for the experience, and all those who suggested workarounds.
> >>
> >> Sharon.
> >
> ------------------------------------------------------------
> Incoming and outgoing emails are checked for viruses
> by Sophos AntiVirus.
>
> This email may contain confidential information which is
> intended for the named recipient(s) only. Â If you are
> not the named recipient you should not take any action in
> relation to this email, other than to notify us that you
> have received it in error.
>
> Lynx Information Systems Ltd
> 93-99 Upper Richmond Rd
> London SW15 2TG
> United Kingdom
> Web: http://www.lynxinfo.co.uk
> Email: [hidden email]
> Tel: +44 (0)20 8780 2634
> Fax: +44 (0)20 8780 0931
>
> Registered in England Number 2454130
> VAT Number GB 561 8979 88
> ------------------------------------------------------------
>

>>
> I generally wait until the 3.x.1 or 3.x.2 versions are out. If someone is not aware of how the release schedule for LibreOffice works, it is very easy for a person to reach the conclusion that you did that 3.5.0 wasn't adequately tested or ready for release.
>
> Don
>
>
> On 02/21/2012 12:02 PM, sharon kimble wrote:
>> I have downgraded my LO program from 3.5.0 to 3.4.5, as the lack of
>> autospellcheck and recent documents in 3.5.0 were real show stoppers, and not
>> being able to find any workarounds.
>>
>> I feel that 3.5.0 was released either with inadequate testing, or before it
>> was ready for release. No matter, its no longer a problem for me.
>>
>> Thank you for the experience, and all those who suggested workarounds.
>>
>> Sharon.
>

> On 2012-02-22 1:12 PM, Chris Morgan <[hidden email]> wrote:
>> I am very sceptical about the so-called benefits of
>> releasing on a strict time-schedule.
>> The process seems to favour new features over bug fixes.
>> I thought the old way was better - release it when it's ready.
>
> The problem with this method is - it is *never* ready (meaning,
> bug-free)...
>
> I like the new release schedule... it ensures that new features are
> introduced faster, and get better testing... everything simply speeds up.
>
> Yes, it does create some potential for breakage, but as long as you
> are prepared (can roll back if you get bit by a show-stopper), it
> shouldn't be a real problem. Also, what may be a show-stopper bug for
> one person is irrelevant to another (not everyone uses the same
> features).