On Wed, Feb 20, 2013 at 4:46 AM, Jürgen Schmidt <jogischm...@gmail.com> wrote:
> Hi,
>
> we make good progress with the sidebar work which is done on the branch.
> The sidebar will be the most visible and important change for 4.0 (by
> the way I like what I have seen so far). We come closer to the point
> where we should talk about a more detailed schedule.
>
> I would like to start with the following proposal and still many steps
> have to be defined in more detail.
>
> 03/01 function verification test will start, define test case, prepare
> tests etc.
> 04/04 integrate sidebar branch in trunk, other new features should be
> finished by this date as well.
> 04/05 - 05/15 regression testing will be start on trunk
> 04/05 - 05/15 bugfix and stabilization, no feature development
> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new
> strings. This can change when we know exactly how many new strings we
> will have. But translation for new languages can already work on the
> existing po files for 3.4.1.
> 05/21 RC1
> 06/04 RC2
> 06/18 RC3 (optional), can be GA already
> 06/25 GA -> this should be our final target
>
>
> This is a proposal based on the ongoing work that I no. Please let me
> know if I missed something important.
>

Have we resolved the question of whether the extensions API is
changing?  If so we probably need an "API freeze" date (maybe the same
as feature freeze), so there is time for extension authors to prepare.
 So probably a set of things to aim for by that date:  1) API freeze,
2) a good build of AOO 4.0 and SDK, 3) Blog post for extension
developers letting them know what will be changing.

-Rob


> Regular developer builds 1/week + nightly builds
>
> Based on feedback and potential changes I will put this in the wiki later.
>
> Important is from my pov that we start talking about the improvements
> that we make in public. It should be very clear for anybody where the
> real important features and improvement for OpenOffice or derivatives
> are coming from ;-)
>
>
> Juergen

Reply via email to