Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
Received-SPF: pass (nike.apache.org: domain of jogischmidt@gmail.com
 designates 74.125.82.46 as permitted sender)
Message-ID: <53905EF9.4010009@gmail.com>
Date: Thu, 05 Jun 2014 14:13:45 +0200
From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= <jogischmidt@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dev <dev@openoffice.apache.org>
Subject: [RELEASE]: propose a AOO 4.1.1 bugfix release as next release
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

over the last weeks we have seen some bugs that seems to be serious
enough to provide a AOO 4.1.1 bugfix release. Well this is at least my
opinion and I would like to volunteer again to manage such a bugfix
release as acting release manager.

The issue 124985 [1] can be seen as a meta issue where we have started
to collect potential candidates for a AOO 4.1.1 bugfix release.

If nobody has bigger concerns or arguments against such a bugfix release
we can continue with a more detailed planning, like schedule,
milestones, QA, detailed selection/proposing of blocker issues etc.

I would like to keep the effort minimal because the main work should go
into a future release 4.2? It really depends what we can achieve when,
you all noticed the ongoing OOXML project that we drive and we will not
enable this work when we are not satisfied that it is a good alternative
and replacement for what we have today ;-)

But before we continue I would like to hear other opinions.

Juergen


[1] https://issues.apache.org/ooo/show_bug.cgi?id=124985

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