[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: Release proposition: Individual applications release
From: "Michael Fair" <michael () daclubhouse ! net>
Date: 2008-05-03 15:50:08
Message-ID: 9ca72c630805030850i5ace06cau3ced08880598efbc () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
How would an average end user install KSpread 2.0 and KWord 1.x without
confusing libraries?
On Sat, May 3, 2008 at 8:37 AM, Cyrille Berger <cberger@cberger.net> wrote:
> Hello,
>
> We have been trying to release KOffice 2.0 as a bundle for sometime, but
> it
> didn't work out since some important office applications are not ready,
> but
> at the same time some applications are getting closer to be ready. So
> Casper
> suggested to make individual application release. That would mean, once an
> application is ready we just release it. Then once KSpread, KWord and
> KPresenter have been released, we can go back to "normal" KOffice bundle
> packages, including all applications that are ready (probably for a 2.1
> release, or 2.0.x "remix").
>
> == Issues ==
>
> That leaves a couple of issues :
>
> * KoLibs : I don't think it's possible to freeze API/ABI of the libraries
> with the first "application release", so that probably means that we will
> have to release KoLibs, then a bunch of application tagged as "Stable",
> then
> other applications marked as "Beta" or "Alpha"
>
> * having 1.6 applications along with 2.0 applications, the biggest proble
> is
> application data (and by that I mean data that is "shared", like the
> content
> of koffice/pics/hicolor koffice/servicetypes and koffice/templates ...),
> since libraries are versionned (and of course KoApp 1.6 + KoApp 2.0 in the
> same prefix is out of question), it's probably something to discuss with
> packagers
>
> == Applications ==
>
> It should be up to the maintainer of an application to decide when he
> thinks
> his application is ready. But it would be nice to have an estimation of
> when
> your application is going to be in a beta state ?
>
> The application that looks the closest to a release is kspread (kplato
> doesn't
> seem to be far away as well), but there is no one commiting on it
> currently :/ And kchart isn't ready.
>
> Any thoughts ? Objections ?
>
> --
> Cyrille Berger
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
[Attachment #5 (text/html)]
How would an average end user install KSpread 2.0 and KWord 1.x without \
confusing libraries?<br><br> <div class="gmail_quote">On Sat, May 3, 2008 at 8:37 AM, \
Cyrille Berger <<a href="mailto:cberger@cberger.net">cberger@cberger.net</a>> \
wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px \
0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br><br>We have been trying to release \
KOffice 2.0 as a bundle for sometime, but it<br>didn't work out since some \
important office applications are not ready, but<br> at the same time some \
applications are getting closer to be ready. So Casper<br>suggested to make \
individual application release. That would mean, once an<br>application is ready we \
just release it. Then once KSpread, KWord and<br> KPresenter have been released, we \
can go back to "normal" KOffice bundle<br>packages, including all \
applications that are ready (probably for a 2.1<br>release, or 2.0.x \
"remix").<br><br>== Issues ==<br> <br>That leaves a couple of issues \
:<br><br> * KoLibs : I don't think it's possible to freeze API/ABI of \
the libraries<br>with the first "application release", so that probably \
means that we will<br>have to release KoLibs, then a bunch of application tagged as \
"Stable", then<br> other applications marked as "Beta" or \
"Alpha"<br><br> * having 1.6 applications along with 2.0 applications, \
the biggest proble is<br>application data (and by that I mean data that is \
"shared", like the content<br> of koffice/pics/hicolor koffice/servicetypes \
and koffice/templates ...),<br>since libraries are versionned (and of course KoApp \
1.6 + KoApp 2.0 in the<br>same prefix is out of question), it's probably \
something to discuss with<br> packagers<br><br>== Applications ==<br><br>It should be \
up to the maintainer of an application to decide when he thinks<br>his application is \
ready. But it would be nice to have an estimation of when<br>your application is \
going to be in a beta state ?<br> <br>The application that looks the closest to a \
release is kspread (kplato doesn't<br>seem to be far away as well), but there is \
no one commiting on it<br>currently :/ And kchart isn't ready.<br><br>Any \
thoughts ? Objections ?<br> <font color="#888888"><br>--<br>Cyrille \
Berger<br>_______________________________________________<br>koffice-devel mailing \
list<br><a href="mailto:koffice-devel@kde.org">koffice-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/koffice-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/koffice-devel</a><br> \
</font></blockquote></div><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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic