https://bugs.freedesktop.org/show_bug.cgi?id=84441
--- Comment #15 from tommy27 <[email protected]> --- > (In reply to tommy27 from comment #12) > .... If you think it should works > differently, please file an enhancement request with an explanation how (and > why) the updater should work, depending on the version installed and the > version available in each branch. > For example: > # If the user is on the Fresh branch: propose to install each bugfix of the > Fresh branch as soon as it is available > # If the user is on the Stable branch: propose to install each bugfix of the > Stable branch as soon as it is available @JBF that's exactly what I've already proposed few comments ago. see below: (In reply to tommy27 from comment #7) > ... > so in the actual scenario I'd expect that a 4.2.5 user to be suggested by > the script to upgrade to 4.2.6, while a 4.3.0 user to be suggested to > upgrade to the 4.3.2 release. > ... you correctly pointed out that there's a corner case here: > # If the user is on the Stable branch and the Stable branch reaches its > End_Of_Life (~last bugfix): propose to jump to the Fresh branch. > > The last point is the most critical from a marketing point of view: what is > the best time to [suggest to] jump from Stable to Fresh branch, knowing that > the Fresh branch will become the Stable branch with the release of the next > main version (x.y.0, e.g. 4.4.0). as far as I know, correct me if I'm wrong, actually the end-of-life users of 4.2.x whose latest release will be 4.2.7 (end of october '14) will be prompted to update to 4.3.x only once the 4.4.0 will be released (early february '15), at that time LibO 4.3.5 will be available. see: https://wiki.documentfoundation.org/ReleasePlan so why not keeping the same behaviour? > Please open a new bug report as enhancement with a clear proposition in the > description. Otherwise all the discussion will be confusing. > > Best regards. JBF I really don't see the point to open a new report as it seems that there's nothing confusing here... please, don't misunderstand the tone of my words... I'm not attacking you, I'm just expressing a different opinion than you, all the bug reporters (including those of the multiple duplicates), Adolfo Jayme (who's an experienced community member) and me too think that's not obvious at all that the script doesn't prompt LO fresh users to upgrade once new release are available. considering the "instability" of the LO Fresh early version, any upgrade should be instead "strongly" suggested. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
