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:20:26 GMT
On 5/11/12 11:16 AM, Xia Zhao wrote:
> Hi Juergen,
>
> I give +1 for contents you proposed.
>
> One thing I care more about is the key bug fixes. We need define what kind
> of defects are critical defects for maintenance release-- I think 3.4.1 is
> one maintenance here. Regression, High severity, Usability? With the
> schedule you proposed, I only suggest include high severity and regression
> ones. The focus should be more languages version and security fixes.

exactly, I agree and we should discuss all issue on ooo-dev to build a 
common understanding for this kind of problems.

Juergen

>
> I will suggest some areas for testing in qa list and delivery weekly report
> from next week.
>
> Best regards,
>
> Lily
>
> Best regards,
>
>
>
> 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