Hi Rob
Zitat von Rob Weir <robw...@apache.org>:
On Thu, Feb 27, 2014 at 3:31 PM, <i...@raphaelbircher.ch> wrote:
Hi at all
Zitat von jan i <j...@apache.org>:
On 27 February 2014 16:58, Vladislav Stevanovic <
stevanovicvladis...@gmail.com> wrote:
Is it too late for update Serbian language?
Wlada
2014-02-27 16:50 GMT+01:00 Jürgen Schmidt <jogischm...@gmail.com>:
just for my understanding, dont we need to vote on the beta as well as the
release. We send the beta out to general public, that would normally
require a vote (might be a fast one).
I wouldn't make a beta as a RC. After a Beta you have normaly several
showstopers to fix. I recall, RC = Release Candidate wich means, that we
assume the build is ready for release. Beta... wait two or tree weeks fix
showstoppers, and then a RC. And the important tests are not the one in the
RC, the important tests are at the build befor RC. Else we make the same
mess as in the 4.0.0.
It is an Release Candidate because a beta is a Release. When we vote
on the RC we agree it is ready for release as a beta. After that
we'll fix more bugs and have another RC and vote for that to be
released as 4.1.
I think the confusion is that we use the word "release" into two ways:
1) The Apache definition of a release == something that a PMC votes on
and approves for publication and public consumption
2) Release as the final version of a product cycle
One way to avoid confusion is to use "GA" for the 2nd meaning (GA=
General Availability). If we do that then it is clear:
1) We have a RC for the Beta and then we release the beta
2) Some weeks later, after fixing more bugs we have an RC for the GA
and then we release the GA
Oh yes, I missunderstud Jürgens answare. I forgot that we have to make
a RC for the Beta too.
Greetings Raphael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
