Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
Date: Sun, 03 Dec 2017 22:25:08 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <F705DC0B-3B35-4D1D-9C05-60292EDBD7AE@jaguNET.com>
References: <FECD28B5-A3D7-4A68-B74F-7253972C2572@comcast.net> <9c3fa32d-7a52-d284-f4ce-1962fcf3e788@wtnet.de> <BB110949-6A3D-4976-BC03-33287049CB92@jaguNET.com> <b39763c2-ddf0-a85d-ff05-1864543d403a@hamburg.de> <7B576A6A-B7CA-47A1-B848-AF900DFF790A@jaguNET.com> <2182a60a-8e13-7b11-9c8b-d2d63d0ee69a@hamburg.de> <a856e618-a28c-0b20-494d-57a420746671@wtnet.de> <00413281-D762-469C-AE5D-C539FED9CA36@jaguNET.com> <533966c2-33fc-7477-61ca-0c8af4ddb827@wtnet.de> <4850cd00-0a05-0807-451a-af4ba11de3bb@Apache.org> <5ac6e568-a124-7370-9d9e-2b1f67deb1c9@wtnet.de> <d153b035-5c85-f031-7a12-c658ed98f6e0@acm.org> <F705DC0B-3B35-4D1D-9C05-60292EDBD7AE@jaguNET.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PROPOSAL] Public Beta for 4.2
To: dev@openoffice.apache.org
From: Peter kovacs <petko@apache.org>
Message-ID: <4D61FF73-44FD-4B53-BC22-0022647104F1@apache.org>
archived-at: Sun, 03 Dec 2017 21:25:24 -0000

How do we then distinguish one beta build from another? By Build number? We=
 need to track build versions=2E

If the vote is the only bad things we could use following flow:
The last voted RC does not have to be the last beta RC=2E We have special =
beta splash screens=2E Maybe an warning in about=2E
When the quality of the release is production ready we close the beta, rem=
ove all beta specials and build a last production version and that will be =
voted on=2E

By this we have simple names, every one can follow, plus we do not break o=
ur work process=2E

All the best
Peter

Am 3=2E Dezember 2017 18:40:23 MEZ schrieb Jim Jagielski <jim@jaguNET=2Eco=
m>:
>
>> On Dec 3, 2017, at 10:06 AM, Patricia Shanahan <pats@acm=2Eorg> wrote:
>>=20
>> On 12/3/2017 6:50 AM, Marcus wrote:
>>> Am 03=2E12=2E2017 um 11:11 schrieb Peter Kovacs:
>>>> I would put Beta into the Splash screen, but Release I would use RC
>for for Release Candidate plus a number=2E So the first version would be
>4=2E2=2E0RC1
>>>>=20
>>>> If this does not break something of course=2E
>>> I think this wouldn't be suitable=2E As soon as we have the last RC
>which get approved, it is automatically the final release build=2E But a
>RC in names and graphics is not what we want=2E
>>> And doing a new build without the RC stuff cannot be done as it is
>not what we had voted for=2E
>>> The max we could do is to use RC in the filenames=2E Then we need
>maybe just a rename and we have the final build=2E In the worst case it's
>just a new upload with the same binary files but then with correct
>filenames=2E
>>> Marcus
>>=20
>> I am opposed even to changing file names=2E Anything we do between the
>final testing and uploading to SourceForge is a risk of something going
>wrong with the process at a point where it can affect millions=2E
>>=20
>
>FWIW, I agree=2E This part of the process works well enough, I think,
>and any "improvements" are likely not worth the risks=2E
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@openoffice=2Eapache=2Eorg
>For additional commands, e-mail: dev-help@openoffice=2Eapache=2Eorg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org