openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus (OOo)" <marcus.m...@wtnet.de>
Subject Re: Release coordination proposal
Date Mon, 22 Jul 2013 19:55:14 GMT
Am 07/22/2013 09:45 PM, schrieb Rob Weir:
> On Mon, Jul 22, 2013 at 2:00 PM, Marcus (OOo)<marcus.mail@wtnet.de>  wrote:
>> OK, I've updated the DL webpages.
>>
>> After fixing some broken links, I think it's OK and ready for a review:
>>
>> http://ooo-site.staging.apache.org/download/index.html
>>
>
> The small print under the download box has two lines for me:
>
> Get all platforms, languages, language packs | Source Code tarballs and SDK |
>
> and
>
> Signatures and Hashes: ASC , MD5 , SHA256 | Release Notes | Legacy Version
>
>
> 1) Is the first line supposed to end with a '|' character?

Yes, a kind of intended line-break. Formerly it was a one-liner but the 
line-break was never appropriate.

> 2) What should the "legacy" link go to now?  Is 3.3.0 still "legacy"?
> If so, what is "3.4.1"?   We might need to reword and restructure that
> destination page, but I think it is OK for now.

In this context I understand "legacy release" as a release from a former 
instance - here Sun/Oracle. With the planned EOL for 3.4 this can be 
cleaned-up, too.

>> Only then I will publish to the live server.
>>
>
> I verified download of the binaries, source and hash files, from a
> Windows 7 machine running Firefox.  It looks good, Marcus!

Thanks

Marcus



>> Am 07/22/2013 07:08 PM, schrieb Kay Schenk:
>>
>>> On Mon, Jul 22, 2013 at 9:18 AM, Marcus (OOo)<marcus.mail@wtnet.de>
>>> wrote:
>>>
>>>> Am 07/22/2013 05:49 PM, schrieb Kay Schenk:
>>>>
>>>>    On Mon, Jul 22, 2013 at 8:16 AM, Rob Weir<robweir@apache.org>  
 wrote:
>>>>>
>>>>>
>>>>>    Can we do something like this?
>>>>>>
>>>>>>
>>>>>> Two stage:  release and announce.
>>>>>>
>>>>>
>>>> This was already planned to do.
>>>>
>>>>
>>>>    Release == put the 4.0 files into production on SourceForge, update
>>>>>>
>>>>>> our download web page to serve 4.0 files by default.
>>>>>>
>>>>>> Announce == go live with news on front page, header announcement
on
>>>>>> every page (branding.mdtext), announcement email, blog post, social
>>>>>> media, new logo on website, etc.
>>>>>>
>>>>>> For the Release part,  can we do that end-of-day today, say in a
>>>>>> couple of hours?
>>>>>>
>>>>>
>>>> Hm, in a couple of hours it's bed time in Hamburg, So, I need to publish
>>>> the new things earlier. I think in 1 or 2 hours, then I have some time to
>>>> correct faulty things.
>>>
>>>
>>>
>>> Yep! Do it! I think this is what Rob meant.  We do the bulk of the DL
>>> stuff
>>> WITHOUT the rebranding until tomorrow.
>>>
>>>
>>>>
>>>>    For the announcement part, this waits for the ASF press release to go
>>>>>>
>>>>>> out tomorrow (Tuesday) at 6am New York time.
>>>>>>
>>>>>> This will give us some time today to:
>>>>>>
>>>>>> 1) verify the downloads are working
>>>>>> 2) add the correct download links to the NL pages.
>>>>>>
>>>>>
>>>> Marcus
>>>>
>>>>
>>>>
>>>>
>>>>    A sterling idea! and one I was thinking about also! +1 !!!!
>>>>>
>>>>>
>>>>> I was just about to suggest holding off on the web site "branding"
>>>>> changes
>>>>> until much later today.  But, this idea is better.
>>>>>
>>>>> Re site branding updates -- later  today (1700 PDT? or suggest something
>>>>> an
>>>>> alternate time)  after 'Release' stage, I will commit/port branding/site
>>>>> changes to staging -- they're not there yet -- so someone else can
>>>>> publish
>>>>> this if need be. I will NOT be available at 0600 EDT -- later like 1100
>>>>> EDT
>>>>> probably.

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


Mime
View raw message