From koffice-devel Tue May 05 07:59:46 2009 From: Cyrille Berger Date: Tue, 05 May 2009 07:59:46 +0000 To: koffice-devel Subject: 2.0 / 2.1 Release plan Message-Id: <200905050959.46411.cberger () cberger ! net> X-MARC-Message: https://marc.info/?l=koffice-devel&m=124151059201317 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1545387944==" --===============1545387944== Content-Type: multipart/alternative; boundary="Boundary-00=_yH//Jmx41bMvKR2" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_yH//Jmx41bMvKR2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, ==== 2.1 ==== I have started to work on a draft for the 2.1 release plan, it's a 6 monthes release plan, with 3 monthes and half of general development, 1 month of lets finish your feature, and a month and half of dedicated bug fixing. 2 betas and hopefuly 1 RC: http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.1/Release_Plan It's still subject to adjustment, and if you have any comments, objections or wishes, now is the best time for that. ==== 2.0 ==== I also would like to finalize the 2.0 release... I see that the list of release blocker for kword is equal to 0, yay :) So that leave the two docker bugs: 1) overlaping dockers 2) disappearing tool docker on crash We have a patch for both, but we need someone that can reproduce those bugs to do testing. In case we can't reproduce, my recommendation on the subject is to not apply the patch for 1) since we don't really know if it fixes anything and might break things, and for 2) I don't think the patch can be harmful, so it could be a good idea to apply it. I propose the following schedule: Tag on May 20th Release on May 27th Would that be ok for the marketing dudette and dudes ? -- Cyrille Berger --Boundary-00=_yH//Jmx41bMvKR2 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi,


==== 2.1 ====


I have started to work on a draft for the 2.1 release plan, it's a 6 monthes release plan, with 3 monthes and half of general development, 1 month of lets finish your feature, and a month and half of dedicated bug fixing. 2 betas and hopefuly 1 RC:


http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.1/Release_Plan


It's still subject to adjustment, and if you have any comments, objections or wishes, now is the best time for that.


==== 2.0 ====


I also would like to finalize the 2.0 release... I see that the list of release blocker for kword is equal to 0, yay :) So that leave the two docker bugs:
1) overlaping dockers
2) disappearing tool docker on crash


We have a patch for both, but we need someone that can reproduce those bugs to do testing. In case we can't reproduce, my recommendation on the subject is to not apply the patch for 1) since we don't really know if it fixes anything and might break things, and for 2) I don't think the patch can be harmful, so it could be a good idea to apply it.


I propose the following schedule:
Tag on May 20th
Release on May 27th


Would that be ok for the marketing dudette and dudes ?


--
Cyrille Berger

--Boundary-00=_yH//Jmx41bMvKR2-- --===============1545387944== 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 --===============1545387944==--