incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Schmidt <jogischm...@googlemail.com>
Subject Re: [RELEASE][AOO3.4.1] proposed time schedule and included content
Date Fri, 11 May 2012 09:25:55 GMT
On 5/11/12 11:20 AM, Yue Helen wrote:
> +1. Thanks for bring it out...it looks like a good plan! I agree that the
> focus of 3.4.1 is translation and critical bug fix only...And we should
> have separate discussion on 3.5 development.
>
> My only comment is that, it could be too aggressive to leave only one week
> for both RC voting and publish...maybe two weeks are better?

maybe but I thought that we will do the main work before on the dev 
builds and voting takes normally 72 hours. But you are probably correct 
when we take into account that we need PPMC and IPMC vote.
We can adapt it on demand and can start the RC 3 days earlier.

Juergen

>
> 2012/5/11 Jürgen Schmidt<jogischmidt@googlemail.com>
>
>> Hi,
>>
>> first of all I am volunteering to act as release manager for 3.4.1 as well
>> if our community think it's a good idea.
>>
>> Independent of the release manager I would like to propose the following
>> time schedule and content for a 3.4.1.
>>
>> Content
>> =======
>> - we will support further languages where we have volunteers working on
>> translation and where we have ideally 100% UI coverage. I think we should
>> focus and balance the support of new languages on demand and completeness.
>> Right now we have Finnish and British English with an updated 100% UI
>> translation. We can also think about language packs only.
>>
>> - we will include important and critical bug fixes or necessary changes.
>> Bugs/tasks have to be proposed and discussed on the ooo-dev mailing list
>> and the issue should be marked with the "3.4.1_release_blocker" flag,
>> concrete the "?" value.
>>
>> - we will include potential security fixes
>>
>>
>> Feature development and less important bugfixes should happen on the trunk
>> and will be included in the next major/minor release (3.5, 3.6, 4.0, ...).
>> The micro release should include minimal functional changes only.
>>
>>
>> Time schedule
>> =============
>>
>> - starting first week of June weekly developer snapshots
>>
>> - June 30, potential translation have to be ready to get included
>>
>> - July 25, providing RC and start voting
>>
>> - July 31, planned release
>>
>> QA should we continuously do on the dev builds.
>>
>>
>> Opinions, comments are welcome and appreciated.
>>
>> Juergen
>>
>


Mime
View raw message