'Re: On the road to 2.0, what's next ?'

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

List:       koffice-devel
Subject:    Re: On the road to 2.0, what's next ?
From:       Sven Langkamp <sven.langkamp () gmail ! com>
Date:       2009-02-12 2:29:58
Message-ID: 478b087a0902111829y7314007ayf659d2c39496c57d () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Mon, Jan 26, 2009 at 3:29 PM, Cyrille Berger <cberger@cberger.net> wrote:

> Hello,
>
>
> During the meeting in Berlin, we decided to have a three monthes more of
> beta testing, and bug fixing, and, by the end of January, to assess the
> situation of KOffice, and when we would be able to release.
>
>
> We have Beta6 coming shortly, then nothing is planned, so we need to decide
> if we need more beta, and which applications will be ready and when.
>
>
> Before we take a decision, we need to know about the state of KOffice, to
> do this:
> * I would like [1] to be filled with Release Critical Bugs for each
> applications (since once the list get empty, we can have a final release)
> * each application maintainer make a quick evaluation of their application,
> and how much time they think it will take to make it ready
>
>
> With this information, I believe we would have a clear view of which
> applications can be released and when.
>
>
> [1]
> http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.0/Release_Critical_Bugs
>

The release critical bugs from KPresenter, KSpread and KPlato are still
missing, Even if the app doesn't have any release critical bugs there should
be a short note in the wiki.

[Attachment #5 (text/html)]

<div class="gmail_quote">On Mon, Jan 26, 2009 at 3:29 PM, Cyrille Berger <span \
dir="ltr">&lt;<a href="mailto:cberger@cberger.net">cberger@cberger.net</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div style="font-family: \
&#39;DejaVu Sans&#39;; font-size: 9pt; font-weight: 400; font-style: \
normal;">Hello,<br> <p style="margin: 0px; text-indent: 0px;"><br></p>During the \
meeting in Berlin, we decided to have a three monthes more of beta testing, and bug \
fixing, and, by the end of January, to assess the situation of KOffice, and when we \
would be able to release. <br>

<p style="margin: 0px; text-indent: 0px;"><br></p>We have Beta6 coming shortly, then \
nothing is planned, so we need to decide if we need more beta, and which applications \
will be ready and when.<br> <p style="margin: 0px; text-indent: 0px;"><br></p>Before \
                we take a decision, we need to know about the state of KOffice, to do \
                this:<br>
* I would like [1] to be filled with Release Critical Bugs for each applications \
                (since once the list get empty, we can have a final release)<br>
* each application maintainer make a quick evaluation of their application, and how \
much time they think it will take to make it ready<br> <p style="margin: 0px; \
text-indent: 0px;"><br></p>With this information, I believe we would have a clear \
view of which applications can be released and when.<br> <p style="margin: 0px; \
text-indent: 0px;"><br></p>[1] <a \
href="http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.0/Release_Critical_Bugs" \
target="_blank">http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.0/Release_Critical_Bugs</a><br>
 </div></blockquote></div><br>The release critical bugs from KPresenter, KSpread and \
KPlato are still missing, Even if the app doesn&#39;t have any release critical bugs \
there should be a short note in the wiki.<br>

_______________________________________________
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] 