incubator-ooo-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][3.4.1]: preparation of download links etc.
Date Sun, 29 Jul 2012 21:35:13 GMT
Am 07/28/2012 01:09 AM, schrieb Kay Schenk:
> On Fri, Jul 27, 2012 at 3:48 PM, Rob Weir<robweir@apache.org>  wrote:
>
>> On Fri, Jul 27, 2012 at 6:18 PM, Rob Weir<robweir@apache.org>  wrote:
>>> On Fri, Jul 27, 2012 at 6:10 PM, Rob Weir<robweir@apache.org>  wrote:
>>>> On Fri, Jul 27, 2012 at 6:00 PM, Dave Fisher<dave2wave@comcast.net>
>> wrote:
>>>>>
>>>>> On Jul 27, 2012, at 2:49 PM, Roberto Galoppini wrote:
>>>>>
>>>>>> On Fri, Jul 27, 2012 at 11:34 PM, Marcus (OOo)<marcus.mail@wtnet.de>
>> wrote:
>>>>>>> Am 07/27/2012 02:25 PM, schrieb Rob Weir:
>>>>>>>
>>>>>>>> On Fri, Jul 27, 2012 at 4:55 AM, J├╝rgen Schmidt
>>>>>>>> <jogischmidt@googlemail.com>   wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> do we need special preparation for the upcoming release
of aOO
>> 3.4.1?
>>>>>>>>>
>>>>>>>>
>>>>>>>> I think we should start preparations for:
>>>>>>>>
>>>>>>>> 1) Updating the /download site to point to 3.4.1 release
files
>>>>>>>
>>>>>>>
>>>>>>> Of course you mean *prepare* the update, aren't you? ;-)
>>>>>>>
>>>>>>> I'll takeover this part and try to deliver first things on Sunday.
>>>>>
>>>>> We should avoid even modifying ooo-site staging as people may very
>> well inadvertently push to production.
>>>>>
>>>>>> Ok, let us know when you want to light it up, since we do need to
>>>>>> prime the mirrors before.
>>>>>
>>>>> Whoa, slow down. There is no way that we are releasing on Sunday.
>> ASFAIK. No one has cut, proposed, reviewed or VOTED on any AOO 3.4.1 RC of
>> any kind.
>>>>>
>>>>> It's good to be ready, but let's not jump the gun.
>>>>>
>>>>
>>>> Right.  We're just establishing a list of items that will need to be
>>>> done once we have a release.   Some are entirely predictably and can
>>>> be prepared off-line now.  For example, the final file names and paths
>>>> are known, so download pages, scripts, etc., can be prepared.  I just
>>>> checked in an updated stats python script to support AOO 3.4.1
>>>> download stats, for example.
>>>>
>>>> But before things go onto the public website, or onto the blog or
>>>> ooo-announce, we need an actual release, as well as time to load the
>>>> mirrors.
>>>>
>>>> This might be a good thing to track on a wiki page, or even we
>>>> webpage.  A check list of release tasks that we can refer to.
>>>>
>>>
>>> Ah, that's why it seemed like a good idea.  We did this with AOO 3.4 as
>> well:
>>>
>>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Distribution+Tasks
>>>
>>
>> I copied that page, removed the parts not needed with AOO 3.4.1 and
>> added the copy here:
>>
>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4.1+Distribution+Tasks
>>
>> Let's work from that.
>>
>> -Rob

Thanks Rob, I've already forgotten this list for the 3.4 release. ;-(

> Ok, a much better idea. As Dave said, we don't even want to DO things and
> let them sit in staging...changes can be published at any time.

Therefore I've some tasks finsihed locally only, ready to commit when 
time has come.

> I'm happy Marcus is around to lend a hand again! YAY!
>
> This should go pretty smoothly I think.

Marcus



>>> -Rob
>>>
>>>> -Rob
>>>>
>>>>> Regards,
>>>>> Dave
>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Roberto
>>>>>>
>>>>>>>
>>>>>>> I don't know if I can bring in some more automatism for the releade
>> (DL
>>>>>>> links in the table, with checksums, etc.) but maybe then short
after.
>>>>>>>
>>>>>>>
>>>>>>>> 2) Keep the legacy download page as it is now, pointing to
the
>>>>>>>> previous major release, which is still OOo 3.3.0
>>>>>>>
>>>>>>>
>>>>>>> Yes. IMHO we should change this earliest with 3.5 when we can
offer
>> some new
>>>>>>> features. But latestly 4.0 is the time to delete the legacy website
>> stuff
>>>>>>> and point the users to the archive when there is still need for
the
>> last OOo
>>>>>>> release.
>>>>>>>
>>>>>>> Marcus
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 3) Copy the AOO 3.4.0 files into archives.apache.org
>>>>>>>>
>>>>>>>> 4) Draft the announcement blog post
>>>>>>>>
>>>>>>>> 5) Submit SHA256 hashes to Symantec for whitelisting.  (Any
other AV
>>>>>>>> vendors have a similar process?)
>>>>>>>>
>>>>>>>> 6) Update the podling website to point to the new source
>> distribution
>>>>>>>>
>>>>>>>> Of course, these are preparations only at this point.  We'll
need to
>>>>>>>> wait for an approved ballot to actually complete 3 and 5,
and will
>>>>>>>> need to wait for the mirrors and SourceForge to update with
the
>>>>>>>> released files before we pull the trigger on the other items.
>>>>>>>>
>>>>>>>> I'm already working on #4.  I did #5 before and can do it
again,
>>>>>>>> unless anyone else wants to see how this is done.
>>>>>>>>
>>>>>>>> -Rob
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> I assume that we don't have the time to rework the directory
>> structure
>>>>>>>>> for this release. I would keep it for now in the same
structure as
>> for
>>>>>>>>> 3.4 but would like to work a simply structure for 3.5
in time.
>>>>>>>>>
>>>>>>>>> Juergen
>>>>>>
>>>>>> --
>>>>>> ====
>>>>>> This e- mail message is intended only for the named recipient(s)
>> above. It
>>>>>> may contain confidential and privileged information. If you are not
>> the
>>>>>> intended recipient you are hereby notified that any dissemination,
>>>>>> distribution or copying of this e-mail and any attachment(s) is
>> strictly
>>>>>> prohibited. If you have received this e-mail in error, please
>> immediately
>>>>>> notify the sender by replying to this e-mail and delete the message
>> and any
>>>>>> attachment(s) from your system. Thank you.
>>>>>>
>>>>>
>>
>
>
>



-- 

Ciao

Marcus

Mime
View raw message