From koffice-devel Sun Oct 24 12:06:47 2010 From: Cyrille Berger Skott Date: Sun, 24 Oct 2010 12:06:47 +0000 To: koffice-devel Subject: KOffice 2.3 release Message-Id: <201010241406.47411.cberger () cberger ! net> X-MARC-Message: https://marc.info/?l=koffice-devel&m=128792206913644 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============2130889300==" --===============2130889300== Content-Type: multipart/alternative; boundary="Boundary-01=_XFCxMgcMy8ThMhb" Content-Transfer-Encoding: 7bit --Boundary-01=_XFCxMgcMy8ThMhb Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, There seem to be a lack of agreement over what to do for the 2.3 release. There are two possibilities: 1) keep the schedule as it stands, release the RC in three weeks, final three to four weeks after, then split, and move forward 2) stop the process, split, each group does his RC, move forward I was under the impression that people wanted the split to happen as soon as possible, this is why I opted for 2). We still have some time to take a final decision, and there is some disagreement with my choice, so, I open this thread to discuss this issue. On a side node, there is quiet a few release blockers left, so further delay is not necesseraly a bad idea. -- Cyrille Berger Skott --Boundary-01=_XFCxMgcMy8ThMhb Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit

Hi,

There seem to be a lack of agreement over what to do for the 2.3 release.

There are two possibilities:

1) keep the schedule as it stands, release the RC in three weeks, final three to four weeks after, then split, and move forward

2) stop the process, split, each group does his RC, move forward

I was under the impression that people wanted the split to happen as soon as possible, this is why I opted for 2). We still have some time to take a final decision, and there is some disagreement with my choice, so, I open this thread to discuss this issue.

On a side node, there is quiet a few release blockers left, so further delay is not necesseraly a bad idea.

--

Cyrille Berger Skott

--Boundary-01=_XFCxMgcMy8ThMhb-- --===============2130889300== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ koffice-devel mailing list koffice-devel@kde.org https://mail.kde.org/mailman/listinfo/koffice-devel --===============2130889300==--