Gentlemen and Ladies,
I have a madly insane idea - when bug fixes/updates are applied to a
project - simply HIDE or REMOVE the unpatched version from the end user's
accessible locations.
I know that the UNPATCHED version needs to remain, for rollbacks or other
badly done updates but, for
Hi :)
It's a good idea. It's already done. Previous versions of a branch are
hidden away in the archives.
Of course some people still need them when something is broken in a newer
release but only IF that proves to be a blocker for them.
The platform is mentioned in the download name, in much
Hi,
TomD wrote
In reply to
this post
http://nabble.documentfoundation.org/LibreOffice-Still-td4117297i100.html#a4124368
by alphacrash
Hi :)
It's not quite that simple :(
With Fresh the new features probably will work just fine. They have been
about as thoroughly tested as
Hello Paul,
Le 01.10.2014 00:55, Paul a écrit :
Hi Charles,
On Tue, 30 Sep 2014 16:32:53 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Hello Paul
On 30 septembre 2014 15:38:26 CEST, Paul paulste...@afrihost.co.za
wrote:
Once more unto the breach, dear friends, once
Hi :)
It's not quite that simple :(
With Fresh the new features probably will work just fine. They have been
about as thoroughly tested as possible. It's any pre-existing stuff that
could be broken.
If it was just the new features that were possibly broken then there would
be no real worry
On 9/30/2014 5:50 PM, Paul paulste...@afrihost.co.za wrote:
Personally I would vote for something like Stable-Current or
Stable-Features and Stable-Mature, or terms in that vein, but I
have to agree, choosing those sorts of terms would be more in line with
the explanations of what they are
On 10/1/2014 5:06 AM, Charles-H. Schulz
charles.sch...@documentfoundation.org wrote:
I don't see these on the Firefox site, I see Firefox, Firefox Beta and
Firefox Aurora, and these seem to have a passable explanation. I would
have liked a slightly better, or more in-depth one, but at least I
Hi,
Le 01/10/2014 12:27, Tanstaafl a écrit :
[...]
*Anytime* a long standing feature is totally ripped out and replaced
with something else that causes a major regression, it should be an
absolute top priority to fix it in the very next release. In fact, I
would say that it should be a
Hi,
I do like stable and old stable - because that's the situation. (Was a
suggestion from Debian) (deleted the rest)
Liebe Grüße, / Yours,
Florian Reisinger
--
To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org
Problems?
On 9/29/2014 2:55 PM, Tom Davies tomc...@gmail.com wrote:
Yes, Fresh is stable but because it's had new features added we can
expect to find that some things that don't so well in Fresh and yet still
find that they work perfectly fine in Still.
To many of us that all sounds like a lot of
Le 30.09.2014 13:26, Tanstaafl a écrit :
On 9/29/2014 2:55 PM, Tom Davies tomc...@gmail.com wrote:
Yes, Fresh is stable but because it's had new features added we can
expect to find that some things that don't so well in Fresh and yet
still
find that they work perfectly fine in Still.
To
Once more unto the breach, dear friends, once more...
On Tue, 30 Sep 2014 14:54:58 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Le 30.09.2014 13:26, Tanstaafl a écrit :
On 9/29/2014 2:55 PM, Tom Davies tomc...@gmail.com wrote:
Yes, Fresh is stable but because it's
Le 30/09/2014 15:53, Tom Davies a écrit :
Hi :)
I think people are talking about a single installer that does the whole
job. Something that normal users can just double-click on, rather than a
long set of complicated instructions.
That is what is doing the Windows installer. On Linux, there
Hi Paul,
Le 30/09/2014 15:38, Paul a écrit :
[...]
The other solution, to make it *easy* to install side-by-side versions,
should be done irrespective of the terminology, but I realise that will
take considerably longer to implement. Although it still should be
recognised as an important
On 30/09/14 16:00, Sophie wrote:
That is what is doing the Windows installer. On Linux, there is only one
command line and a file to edit, so really I don't see how it's
complicated. I don't know about Mac however.
On a Mac, you can install as many instances of LibreOffice as you want,
On 9/30/2014 8:54 AM, Charles-H. Schulz
charles.sch...@documentfoundation.org wrote:
I am sorry to say this, but what is ridiculous here is the inability of
some to even understand what is being discussed.
Oh, I understand what is being discussed.
What you don't understand is the complaint.
Hi Sophie, Tom, et al.
Thank you for the instructions. I knew it was possible, but hadn't
looked into it.
As Tom pointed out though, this does need to be part of the standard
installer, which I don't think this is? People shouldn't have to go
looking for ways to do this, just downloading LO and
On 9/30/2014 9:53 AM, Tom Davies tomc...@gmail.com wrote:
I think people are talking about a single installer that does the whole
job. Something that normal users can just double-click on, rather than a
long set of complicated instructions.
Yes. The installer should automatically detect the
Le 30/09/2014 16:04, Tom Davies a écrit :
Hi :)
I think i didn't state it clearly enough and something got lost in
translation
Errr, the single installer installs both Still and Fresh at the same
time as each other? One installer gets both versions at the same time?
Hum, read the doc ;)
Hello Paul
On 30 septembre 2014 15:38:26 CEST, Paul paulste...@afrihost.co.za wrote:
Once more unto the breach, dear friends, once more...
On Tue, 30 Sep 2014 14:54:58 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Le 30.09.2014 13:26, Tanstaafl a écrit :
On 9/29/2014
Hi Charles,
Le 30/09/2014 16:32, Charles-H. Schulz a écrit :
Where I disagree with you is that there are people who think that fresh is
unstable and not even a testing branch... but so be it.
IIRC, this is probably because this is how things were previously
introduced on the previous
Hi,
Le 30/09/2014 16:14, Tanstaafl a écrit :
On 9/30/2014 9:53 AM, Tom Davies tomc...@gmail.com wrote:
I think people are talking about a single installer that does the whole
job. Something that normal users can just double-click on, rather than a
long set of complicated instructions.
Yes.
Hi :)
I think i didn't state it clearly enough and something got lost in
translation
Errr, the single installer installs both Still and Fresh at the same
time as each other? One installer gets both versions at the same time?
Regards from
Tom :)
On 30 September 2014 15:00, Sophie
On 9/30/2014 10:41 AM, Sophie gautier.sop...@gmail.com wrote:
What makes no sense for me is to refuse something without even having a
look at it.
What am I refusing to look at? The complicated instructions?
Or are you saying that the installer already works as I described? If it
does,
Aha! I think I have solved the terminology problem!
For many working on the LO project, English is their second language.*
Clearly, when terms were being proposed, someone misheard, which why is why
the two forks were not named “Fresh and “Stale.
Rearguards,
Hedley
* I have only one language
On Tue, 30 Sep 2014 14:01:09 -0400
Tanstaafl tansta...@libertytrek.org wrote:
On 9/30/2014 10:41 AM, Sophie gautier.sop...@gmail.com wrote:
What makes no sense for me is to refuse something without even
having a look at it.
What am I refusing to look at? The complicated instructions?
On Wed, 1 Oct 2014 07:28:52 +1000
Hedley Finger hedley.fin...@gmail.com wrote:
Aha! I think I have solved the terminology problem!
For many working on the LO project, English is their second language.*
Clearly, when terms were being proposed, someone misheard, which why
is why the two
Hi Charles,
On Tue, 30 Sep 2014 16:32:53 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Hello Paul
On 30 septembre 2014 15:38:26 CEST, Paul paulste...@afrihost.co.za
wrote:
Once more unto the breach, dear friends, once more...
On Tue, 30 Sep 2014 14:54:58 +0200
Hi Tom,
Tom Davies wrote on 29-09-14 19:31:
That is the sort of argument MANY on this Mailing List agree with. Please
take it to the Discus Mailing List and maybe the social networking channels
if you really want to get heard but it's going to make you unpopular.
What you wrote here looks
Tom Davies wrote on 29-09-14 20:55:
To many of us that all sounds like a lot of politicians, or marketing,
double-speak.
Hence the sincere need to have it well and clearly visible explained.
Thanks a lot for your help,
Cor
--
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28
I see this is still doing the rounds. And the parties are as far from
common ground as ever. Ah well...
On Mon, 29 Sep 2014 20:37:26 +0200
Cor Nouws oo...@nouenoff.nl wrote:
Hi Tom,
Tom Davies wrote on 29-09-14 19:31:
That is the sort of argument MANY on this Mailing List agree with.
Hi :)
Yes, Fresh is stable but because it's had new features added we can
expect to find that some things that don't so well in Fresh and yet still
find that they work perfectly fine in Still.
To many of us that all sounds like a lot of politicians, or marketing,
double-speak.
Obviously what
On 07/08/14 09:07, Tom Davies wrote:
Ubuntu makes it very clear that their LTS is more stable and that their
other branch is more exciting.
Unfortunately, this is not always true. Ubuntu 12.04 LTS was based on a
buggy Unity, and although it was supported for a longer term than 12.10
(just to
On 08/06/2014 10:01 AM, Florian Reisinger wrote:
Hi Tom,
If we do not find the bugs in the fresh version, they won't be resolved until
the rename to Stable/Still. If less use Fresh, the quality of the next stable
will be lower Does this help?
No. Basically what you and Sophie are
Le 07.08.2014 09:55, NoOp a écrit :
On 08/06/2014 10:01 AM, Florian Reisinger wrote:
Hi Tom,
If we do not find the bugs in the fresh version, they won't be
resolved until the rename to Stable/Still. If less use Fresh, the
quality of the next stable will be lower Does this help?
No.
Hi Tim, all,
Le 07/08/2014 00:55, Kracked_P_P---webmaster a écrit :
On 08/06/2014 10:31 AM, Sophie wrote:
Hi,
Le 06/08/2014 15:49, arakish a écrit :
So, you do go through stages. You just misnomered them.
Why not just use that?
Stages:
Alpha
Beta
Release Candidate
Final Release
Hi :)
No-Op has been a huge help to many people on this User Mailing List since
the very early days of TDF. I know that user-support and customer service
are kinda frowned on as being not much work.
However it is the first point-of-contact between weeus and is a prime place
to build people up
Le 07.08.2014 14:28, Tom Davies a écrit :
Hi :)
No-Op has been a huge help to many people on this User Mailing List
since the very early days of TDF. I know that user-support and
customer service are kinda frowned on as being not much work.
I would never say that.
However it is the first
Quoting myself:
please describe, step by step, what is hard
about contributing or finding information about contributing.
No answer to that question.
As for customer service, we don't do customer service. Volunteers
provide users support. Users support in this case is not done as a
On Thu, 07 Aug 2014 10:09:37 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Le 07.08.2014 09:55, NoOp a écrit :
On 08/06/2014 10:01 AM, Florian Reisinger wrote:
Hi Tom,
If we do not find the bugs in the fresh version, they won't be
resolved until the rename
Hi :)
Quite!!
Ubuntu makes it very clear that their LTS is more stable and that their
other branch is more exciting. They don't force all new users into using
their least stable branch. Instead of making it complicated and difficult
to change versions they make it easy. Instead of hiding
Hi :)
Ahh, i understand now. You don't mean to be insulting and don't even
notice when you do it.
Your statement, As for customer service, we don't do customer service.,
well said. I'm not sure who the we is. It doesn't include almost anyone
on this mailing list since the whole reason for this
Hello Pikov
On 6 août 2014 07:29:17 CEST, Pikov Andropov piko...@gmail.com wrote:
Florian Reisinger wrote on 8/6/2014 1:22 AM:
Hi,
The problem we have: We do not have one release branch as Firefox
has, we have two... Users should use and find bugs on the Fresh
version in order to make thee
Am 06.08.2014 07:29, schrieb Pikov Andropov:
Florian Reisinger wrote on 8/6/2014 1:22 AM:
Hi,
The problem we have: We do not have one release branch as Firefox has, we
have two... Users should use and find bugs on the Fresh version in order
to make thee fresh, which will be renamed to
Hi :)
Ahh, so both branches are just as stable as each other? The only
difference is that the newer branch has more features?
So why do we still have the older branch at all?
Regards from
Tom :)
On 6 August 2014 08:23, Charles-H. Schulz
charles.sch...@documentfoundation.org wrote:
Hello
Hi :)
This seems to be contradicting what Charles is saying.
Also is it really a good policy to force new and unwitting users to act as
guinea-pigs? Should all new users be pushed into finding and fixing bugs?
Would it really be bad to give them a clear and easy route to a less buggy
version?
Hi Tom, all,
Le 06/08/2014 11:17, Tom Davies a écrit :
Hi :)
This seems to be contradicting what Charles is saying.
no, they are on the same page :)
Also is it really a good policy to force new and unwitting users to act as
guinea-pigs? Should all new users be pushed into finding and
Hi :)
This seems to contradict what both Charles and what Florian Reisinger were
saying.
It does seem to make more sense though. It kinda explains why people might
prefer one branch or the other one, which was very unclear from Charles and
Florian's posts.
It also kinda explains the graphic on
Hi :)
How do new users know what the difference is between the 2 branches?
Clearly it is not so easy for new people to figure it out otherwise we
wouldn't keep on having to answer this same question from so many new
users.
As a longer-term users i feel sufficiently experienced to know which
Hi all,
Le 06/08/2014 11:42, Tom Davies a écrit :
Hi :)
How do new users know what the difference is between the 2 branches?
Clearly it is not so easy for new people to figure it out otherwise we
wouldn't keep on having to answer this same question from so many new
users.
So you answer
Hi :)
The difference is that Charles is saying that both branches are as stable
as each other.
Florian was saying that new users have to do the bug-finding on the Fresh
branch in order to help it become more stable.
Florian's seems to explain what we find on this mailing list = that new
users
Hello Tom,
First, both Nino and Sophie's answers are really good. Mine was just
trying to be simple and short.
I think, just like Sophie suggested, that you are still thinking along
the stable-unstable pattern.
My answer, by the way, does not contraddict Nino or Sophie. Let me take
two
Am 06.08.2014 11:38, schrieb Tom Davies:
This seems to contradict what both Charles and what Florian Reisinger were
saying.
No. See below:
[...]
It also kinda explains the graphic on the;
https://wiki.documentfoundation.org/ReleasePlan
page, although that graphic doesn't make a lot of
Hi :)
Ok, so the question is why have 2 different branches at all?
The Fresh branch has the advantage of having more features but what
advantage does the older branch have?
In the case of Chevrolet Impala 2013 and 2011 i seriously doubt that both
models are being manufactured at the same time.
Hi :)
Ok, in the case of fruit, say apples and oranges. There are clear
differences between them. They might be available (or better) in different
seasons. One is usually orange and the other usually green or red. One
might be juicier than the other. One more acidic than the other.
Different
Am 06.08.2014 13:07, schrieb Tom Davies:
So again the question has apparently gone back to What is the advantage of
the Still branch. Why would people choose it or what circumstances would
suit Still better than Fresh?
The main advantage is its age: it's more mature; it has been in use for a
Le 06/08/2014 13:00, Tom Davies a écrit :
Hi :)
Ok, so the question is why have 2 different branches at all?
The Fresh branch has the advantage of having more features but what
advantage does the older branch have?
To have less bugs and regressions that make it more sure to use by
average
Nino,
Right on target; I could not have said it better. As for the release pace there
is a theory that suggests that slowing it to a rearly rythmn would decrease the
intetest of developers. But that is obviously a theory, and cannot be an exact
science.
Best,
Charles.
On 6 août 2014
Hi :)
Ok, so that sounds like the 4th or 6th cycle of a branch has reduced the
bugs and regressions = i think most people would call that making it more
stable wouldn't they?
Then the point about recent releases having had less usage seems to be
saying that it is not quite so stable.
Actually
Hi :)
Errr, i think the LTS idea works well as long as there is a 6 monthly
release, or at least a much faster-paced release cycle for another branch.
The 6 monthly alone is difficult for many people to keep up with, even for
big fans, but it does do a lot for excitement and energy. It motivates
We have developed a cycle for each line where we know that x.x.0 is
the newest and x.x.6/7 is the most mature of that line. So we should
use that idea.
Yes we have two lines.
Yes there is an idea of maturity vs. younger/fresher
Yes the newer line should have more features to work with or
Hello Tim,
Le 06.08.2014 15:04, Kracked_P_P---webmaster a écrit :
We have developed a cycle for each line where we know that x.x.0 is
the newest and x.x.6/7 is the most mature of that line. So we should
use that idea.
Yes we have two lines.
Yes there is an idea of maturity vs.
So, you do go through stages. You just misnomered them.
Why not just use that?
Stages:
Alpha
Beta
Release Candidate
Final Release Candidate (LO v4.3.0)
Stable (LO v4.2.6)
As said in my previous post. The download page is confusing enough.
Unconfuse it with the above stages. This fresh and
Hello Tom,
A few thoughts on the LTS - it's good we are on the users list just for
this topic I think.
LTS (Long Term Support) is often misunderstood. Canonical introduced the
notion of LTS, but few realize that they were able to do so and are able
to maintain this kind of version for the
Each branch has its own release candidates, even its final release
candiates. Each branch is autonomous (has its master branch, if you
will), and has its stable releases.
BTW: we don't reinvent the wheel here, this is how development works and
the use of terminology we use (alphas, betas,
Hi :)
+1
too.
Regards from
Tom :)
On 6 August 2014 05:47, J. Van Brimmer jerry...@gmail.com wrote:
+1
On Aug 5, 2014 6:42 PM, arakish rmfrun...@gmail.com wrote:
It is of my opinion that you should stick with the standards.
What is wrong with calling the newest possible stable version
On Wed, 06 Aug 2014 12:05:08 +0200
Sophie gautier.sop...@gmail.com wrote:
Clearly it is not so easy for new people to figure it out otherwise
we wouldn't keep on having to answer this same question from so
many new users.
So you answer them and they will know, this is how support works.
I don't know the cars in question, so maybe that specific case is
different. But in my general experience, when two car models are sold,
the only reason the older one is still sold is because they have unsold
vehicles that they need to get rid of, so they offer them at a lower
price, and the only
On Wed, 06 Aug 2014 15:56:13 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
LTS will never, however magically produce a better quality release
No, not magically, but by the very nature of it being around for longer
it will, in the end, result in a more stable product.
On 8/6/2014 9:49 AM, arakish rmfrun...@gmail.com wrote:
Stages:
Alpha
Beta
Release Candidate
Final Release Candidate (LO v4.3.0)
Stable (LO v4.2.6)
Or go the Debian way...
4.3 would be the 'Testing' branch...
4.2.x would be the Stable branch...
--
To unsubscribe e-mail to:
On Wed, 06 Aug 2014 13:52:28 +0200
Sophie gautier.sop...@gmail.com wrote:
Le 06/08/2014 13:00, Tom Davies a écrit :
Hi :)
Ok, so the question is why have 2 different branches at all?
The Fresh branch has the advantage of having more features but
what advantage does the older branch
Le 06.08.2014 16:22, Paul a écrit :
On Wed, 06 Aug 2014 15:56:13 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
LTS will never, however magically produce a better quality release
No, not magically, but by the very nature of it being around for longer
it will, in the
Hi,
Le 06/08/2014 15:49, arakish a écrit :
So, you do go through stages. You just misnomered them.
Why not just use that?
Stages:
Alpha
Beta
Release Candidate
Final Release Candidate (LO v4.3.0)
Stable (LO v4.2.6)
Please read this page to know more about our development process
Le 06.08.2014 16:14, Paul a écrit :
On Wed, 06 Aug 2014 12:05:08 +0200
Sophie gautier.sop...@gmail.com wrote:
Clearly it is not so easy for new people to figure it out otherwise
we wouldn't keep on having to answer this same question from so
many new users.
So you answer them and they will
On Wed, 6 Aug 2014 13:35:55 +0100
Tom Davies tomc...@gmail.com wrote:
Hi :)
Ok, so that sounds like the 4th or 6th cycle of a branch has
reduced the bugs and regressions = i think most people would call
that making it more stable wouldn't they?
By definition, yes.
Stable is hard to
On Wed, 06 Aug 2014 16:31:46 +0200
Sophie gautier.sop...@gmail.com wrote:
Hi,
Le 06/08/2014 15:49, arakish a écrit :
So, you do go through stages. You just misnomered them.
Why not just use that?
Stages:
Alpha
Beta
Release Candidate
Final Release Candidate (LO v4.3.0)
On Wed, 06 Aug 2014 16:36:33 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Le 06.08.2014 16:14, Paul a écrit :
On Wed, 06 Aug 2014 12:05:08 +0200
Sophie gautier.sop...@gmail.com wrote:
Clearly it is not so easy for new people to figure it out
otherwise we
Le 06/08/2014 16:48, Paul a écrit :
On Wed, 06 Aug 2014 16:31:46 +0200
Sophie gautier.sop...@gmail.com wrote:
Hi,
Le 06/08/2014 15:49, arakish a écrit :
So, you do go through stages. You just misnomered them.
Why not just use that?
Stages:
Alpha
Beta
Release Candidate
Final
On Wed, 06 Aug 2014 17:01:33 +0200
Sophie gautier.sop...@gmail.com wrote:
And we come back to the beginning of the discussion, if you have
better names, the marketing team will be happy to discuss them :)
Kind regards
Sophie
Sure, please pass on to the team:
Stable
Development (or Current,
On Wed, 06 Aug 2014 17:20:32 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Paul : did you intend to post this off list?
No, sorry, my bad for not checking the address. I just clicked reply.
For most messages that goes to the list, I don't know why some people
seem to
Hello Paul,
On 6 août 2014 17:37:58 CEST, Paul paulste...@afrihost.co.za wrote:
On Wed, 06 Aug 2014 17:20:32 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Paul : did you intend to post this off list?
No, sorry, my bad for not checking the address. I just clicked
Hi :)
Yeh, i have always thought that giving the newest users the least stable
version is a bad idea.
At the moment it is only once you are familiar with LibreOffice and become
able to cope with problems more easily that you are able to get the least
buggy version!
One of the problems with the
Hi Tom,
If we do not find the bugs in the fresh version, they won't be resolved until
the rename to Stable/Still. If less use Fresh, the quality of the next stable
will be lower Does this help?
Liebe Grüße, / Yours,
Florian Reisinger
Am 06.08.2014 um 11:17 schrieb Tom Davies
On Wed, 06 Aug 2014 17:55:14 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Hello Paul,
On 6 août 2014 17:37:58 CEST, Paul paulste...@afrihost.co.za wrote:
On Wed, 06 Aug 2014 17:20:32 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Hi Tom,
I will try to rephrase it... Fresh is going to be renamed to Still (Stable)
after a while. Bugs not found in Fresh will land in Stable within 6M... So the
quality of the Stable will decrease if less people use the Fresh branch... So
we need to find bugs early in the cycle ( when it is
On Wed, 6 Aug 2014 19:01:19 +0200
Florian Reisinger flo...@libreoffice.org wrote:
Hi Tom,
If we do not find the bugs in the fresh version, they won't be
resolved until the rename to Stable/Still. If less use Fresh, the
quality of the next stable will be lower Does this help?
That is
Hi Florian,
Florian Reisinger wrote on 06-08-14 20:01:
Hi Tom,
[...]
Thanks for your encouraging attempts to explain over and again.
I would expect that only for newcomers those items could ask for _some_
explanation.
Cheers,
Cor
--
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C
Just to add another point... (see inline)
On Wed, 6 Aug 2014 20:04:56 +0200
Paul paulste...@afrihost.co.za wrote:
On Wed, 6 Aug 2014 19:01:19 +0200
Florian Reisinger flo...@libreoffice.org wrote:
Hi Tom,
If we do not find the bugs in the fresh version, they won't be
resolved
Paul,
The fresh branch is stable enough for everyone to use. LibreOffice does
not pilot planes, it does not usually crash, it does the job. There are
people who want newer features and people who want more tested
versions. There's food for everyone.
Now: if you have ideas for new names, etc. you
On Wed, 6 Aug 2014 20:54:10 +0200
Charles-H. Schulz charles.sch...@documentfoundation.org wrote:
Paul,
The fresh branch is stable enough for everyone to use. LibreOffice
does not pilot planes, it does not usually crash, it does the job.
There are people who want newer features and people
Paul-6 wrote
So for me first prize would be to have both branches as equal downloads
on the LO download page. With a clear, concise explanation of what each
offers, and a link to a slightly longer, fuller explanation. That is
exactly what I am proposing should be done.
But barring that, if
On 08/06/2014 10:31 AM, Sophie wrote:
Hi,
Le 06/08/2014 15:49, arakish a écrit :
So, you do go through stages. You just misnomered them.
Why not just use that?
Stages:
Alpha
Beta
Release Candidate
Final Release Candidate (LO v4.3.0)
Stable (LO v4.2.6)
Please read this page to know more
On 8/6/2014 10:55 AM, Paul wrote:
But that doesn't change the fact that the concept of an LTS version has
nothing to do with the business deals behind it.
Yes, and no.
As a general rule, Long Term Support is a direct function of
business/corporate support. (Debian is probably the best known
Hi, good night all:
As I understand there are some official versions. I think that could be
better that The Document Foundation only has one version for all
languages for production and makes its firsts efforts to solve all the
most important bugs (This would be by user and programmer
It is of my opinion that you should stick with the standards.
What is wrong with calling the newest possible stable version Release
Candidate, the proven stable version Stable, the unstable beta-tester
version Beta?
It makes absolutely no sense to me to be different just for the sake of
being
+1
On Aug 5, 2014 6:42 PM, arakish rmfrun...@gmail.com wrote:
It is of my opinion that you should stick with the standards.
What is wrong with calling the newest possible stable version Release
Candidate, the proven stable version Stable, the unstable beta-tester
version Beta?
It makes
Hi,
The problem we have: We do not have one release branch as Firefox has, we have
two... Users should use and find bugs on the Fresh version in order to make
thee fresh, which will be renamed to stable after 6M.
So how to say you can use the feature packed fresh? It is not an RC it is an
Thoroughly agree!
+1
jdh
On 08/06/2014 06:47 AM, J. Van Brimmer wrote:
+1
On Aug 5, 2014 6:42 PM, arakish rmfrun...@gmail.com wrote:
It is of my opinion that you should stick with the standards.
What is wrong with calling the newest possible stable version Release
Candidate, the proven
Florian Reisinger wrote on 8/6/2014 1:22 AM:
Hi,
The problem we have: We do not have one release branch as Firefox has, we
have two... Users should use and find bugs on the Fresh version in order to
make thee fresh, which will be renamed to stable after 6M.
So how to say you can use the
I have to agree with NoOp on this.
I've ended up being quite confused on some things whose definition was only
available to the high priesthood who use forums that I would never
normally be interested in (marketing certainly being one of them).
--
View this message in context:
1 - 100 of 107 matches
Mail list logo
