From kde-core-devel Mon Jun 06 23:02:28 2011 From: John Layt Date: Mon, 06 Jun 2011 23:02:28 +0000 To: kde-core-devel Subject: Re: Releases of the thing that was KDE Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=130740143110096 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--bcaec520ea37f56a1e04a513187f" --bcaec520ea37f56a1e04a513187f Content-Type: text/plain; charset=ISO-8859-1 On 6 June 2011 23:36, Scott Kitterman wrote: > > I get we need to modularize for a number of important reasons, but I don't > see > the companion story for how this all gets released as something coherent > and > functional. > > Where's that part of the story? > > Scott K > From Sebas' email: What does it mean for packagers? * We make it possible to ship our frameworks in a more modular way * We also plan to provide "monolithic tarballs" much as we do now, depending on the needs and preferences of downstreams An email will follow from the people who participated in the Build and Release work group on how they plan to make this work, please wait for them to report back. John. --bcaec520ea37f56a1e04a513187f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On 6 June 2011 23:36, Scott Kitterman <kde@kitterman.com<= /a>> wrote:
I get we need to modularize for a number of important reasons, but I don= 9;t see
the companion story for how this all gets released as something coherent an= d
functional.

Where's that part of the story?

Scott K

From Sebas' email:

What does it mean for packagers?

* We make it possib= le to ship our frameworks in a more modular way
* We also plan to provid= e "monolithic tarballs" much as we do now, depending
=A0on the= needs and preferences of downstreams
An email will follow from th= e people who participated in the Build and Release work group on how they p= lan to make this work, please wait for them to report back.

John.
=A0
--bcaec520ea37f56a1e04a513187f--