'2.0 / 2.1 Release plan'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    2.0 / 2.1 Release plan
From:       Cyrille Berger <cberger () cberger ! net>
Date:       2009-05-05 7:59:46
Message-ID: 200905050959.46411.cberger () cberger ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

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

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; \
font-weight:400; font-style:normal;">Hi,<br> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>==== 2.1 ====<br> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>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:<br> \
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.1/Release_Plan<br>
 <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>It's still subject to adjustment, and if you have any \
comments, objections or wishes, now is the best time for that.<br> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>==== 2.0 ====<br> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>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:<br> 1) overlaping dockers<br>
2) disappearing tool docker on crash<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>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.<br> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I propose the \
following schedule:<br> Tag on May 20th<br>
Release on May 27th<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>Would that be ok for the marketing dudette and dudes ?<br> \
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>-- <br> Cyrille Berger</p></body></html>

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread] 