https://bugs.freedesktop.org/show_bug.cgi?id=81734

          Priority: medium
            Bug ID: 81734
          Assignee: libreoffice-bugs@lists.freedesktop.org
           Summary: Release schedule / support status does not match
                    Download offerings
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: ulrich.wi...@rz.uni-regensburg.de
          Hardware: All
            Status: UNCONFIRMED
           Version: 4.2.5.2 release
         Component: Documentation
           Product: LibreOffice

According to the release schedule, LibreOffice 4.1.6 is end-of-life, but it's
still offered as "Stable" download. Likewise 4.2.5 is offered as "Fresh" while
it's actually close to end of life.
Despite of the fact that I see little sense with a time based release schedule,
the schedule should match the download offerings.
Personally I think the current version should no be end of life until the next
version is considered "Stable". And I see little sense to "push" version
numbers (like Firefox does recently): Software doesn't get worse while getting
older. just as newer software need not be any better than the older releases.
For LibreOffice I have the feeling that several features were broken in newer
releases, while some of the newer features still don't work well. How will that
pattern lead to truly reliable and useful software?

Maybe have three versions: One "stable" version that is supported until no more
bugs are found (unlikely), one "develop" version where new features are
implemented, and one "next" version where all the bug fixes from the stable
version are merged as well as new features that are considered "virtually bug
free and stable".
Users wanting reliable software should use "stable". Users who want to try (or
need) new features should use "next". Only developers or users that like to
lead a riscful life should use the "develop" version. So "stable" should be
replaced with "next", but "develop" should not simply become next; instead
selected features (stable and virtually bug-free) should be merged into stable
to make "next". Developers can continue to improve features on "develop"...
So bug fixes should be merged from "stable" to "next", from "next" to
"develop", and possibly the other direction as well.

I know this is a highly subjective topic, but maybe thing will become better...

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to