From kde-windows  Thu Jan 10 19:55:58 2013
From: Laszlo Papp <lpapp () kde ! org>
Date: Thu, 10 Jan 2013 19:55:58 +0000
To: kde-windows
Subject: Re: Emerge : error while install kdelib on windows with emerge python 33 no module info
Message-Id: <CAOMwXhPNU8oQFedMMKfo4kdqJj2GQbUsG8FhFJN6Q=u9gxCwag () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-windows&m=135784778022201
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2679297494368706918=="

--===============2679297494368706918==
Content-Type: multipart/alternative; boundary=00151759329e4d6e3104d2f49165

--00151759329e4d6e3104d2f49165
Content-Type: text/plain; charset=ISO-8859-1

IMO, with KDE 4.10 on the radar, we should perhaps focus on master again.

On Thu, Jan 10, 2013 at 8:30 PM, Thomas Friedrichsmeier <
thomas.friedrichsmeier@ruhr-uni-bochum.de> wrote:

> Hi,
>
> On Wednesday 09 January 2013, Laszlo Papp wrote:
> > We would need to fix those anyway as that is the last release. There are
> > bugs everywhere, and I am sure there will be bugs in 4.9 not even
> > considered. Still, I would consider a stable branch for newcomers, and
> fix
> > the problem appearing.
>
> agreed, if there *is* any newcomer friendly stable branch at all. My
> recommendation for 4.9 is simply based on my personal - and thus extremely
> narrow - experience. 4.9 gave me less trouble than 4.8. But yes, almost
> certainly there will be regressions, too.
>
> > It is better to have less, but more stable branches now and also in the
> > future in my opinion.
>
> I agree. But which branches to focus on? master is a "natural" keep.
> Besides
> that we'd keep whichever branch(es) is(are) the focus for the next binary
> release(s). I used to assume that's kde-4.9.
>
> But perhaps the real question is: *Is* there a release target/focus at all,
> ATM? (And if so, where would be the canonical place to read up on this?)
>
> As far as kde-4.8 and older is concerned: Surely, having working "archives"
> would be fairly desirable(*). But IMO, that's not a top priority for
> emerge.
> If you want a stable *release*, you can use the binaries. But the key
> selling
> point for emerge is that you want to do development (or stand at the
> bleeding
> edge, watching develoment). For that purpose you're most likely to pick the
> youngest branches.
>
> Regards
> Thomas
>
> (*): Talking about archives: Suppose, every time a release has been
> created,
> self-contained snapshots of the build root would be created (one for each
> arch), archived, and offered for download. I.e. something like what I've
> zipped up for kde 4.9, mingw4, 32bit (http://lists.kde.org/?l=kde-
> windows&m=135541718223018&w=2). Interested developers (particularly, but
> not
> only, third-party devs) could simply download and unpack these, and be
> sure to
> get a working environment - even years later. I think that would be one
> great
> way to lower the entry barriers to KDE on Windows development.
>
> _______________________________________________
> Kde-windows mailing list
> Kde-windows@kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
>
>

--00151759329e4d6e3104d2f49165
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

IMO, with KDE 4.10 on the radar, we should perhaps focus on master again.<b=
r><br><div class=3D"gmail_quote">On Thu, Jan 10, 2013 at 8:30 PM, Thomas Fr=
iedrichsmeier <span dir=3D"ltr">&lt;<a href=3D"mailto:thomas.friedrichsmeie=
r@ruhr-uni-bochum.de" target=3D"_blank">thomas.friedrichsmeier@ruhr-uni-boc=
hum.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">Hi,<br>
<br>
On Wednesday 09 January 2013, Laszlo Papp wrote:<br>
</div><div class=3D"im">&gt; We would need to fix those anyway as that is t=
he last release. There are<br>
&gt; bugs everywhere, and I am sure there will be bugs in 4.9 not even<br>
&gt; considered. Still, I would consider a stable branch for newcomers, and=
 fix<br>
&gt; the problem appearing.<br>
<br>
</div>agreed, if there *is* any newcomer friendly stable branch at all. My<=
br>
recommendation for 4.9 is simply based on my personal - and thus extremely<=
br>
narrow - experience. 4.9 gave me less trouble than 4.8. But yes, almost<br>
certainly there will be regressions, too.<br>
<div class=3D"im"><br>
&gt; It is better to have less, but more stable branches now and also in th=
e<br>
&gt; future in my opinion.<br>
<br>
</div>I agree. But which branches to focus on? master is a &quot;natural&qu=
ot; keep. Besides<br>
that we&#39;d keep whichever branch(es) is(are) the focus for the next bina=
ry<br>
release(s). I used to assume that&#39;s kde-4.9.<br>
<br>
But perhaps the real question is: *Is* there a release target/focus at all,=
<br>
ATM? (And if so, where would be the canonical place to read up on this?)<br=
>
<br>
As far as kde-4.8 and older is concerned: Surely, having working &quot;arch=
ives&quot;<br>
would be fairly desirable(*). But IMO, that&#39;s not a top priority for em=
erge.<br>
If you want a stable *release*, you can use the binaries. But the key selli=
ng<br>
point for emerge is that you want to do development (or stand at the bleedi=
ng<br>
edge, watching develoment). For that purpose you&#39;re most likely to pick=
 the<br>
youngest branches.<br>
<br>
Regards<br>
Thomas<br>
<br>
(*): Talking about archives: Suppose, every time a release has been created=
,<br>
self-contained snapshots of the build root would be created (one for each<b=
r>
arch), archived, and offered for download. I.e. something like what I&#39;v=
e<br>
zipped up for kde 4.9, mingw4, 32bit (<a href=3D"http://lists.kde.org/?l=3D=
kde-
windows&amp;m=3D135541718223018&amp;w=3D2" target=3D"_blank">http://lists.k=
de.org/?l=3Dkde-<br>
windows&amp;m=3D135541718223018&amp;w=3D2</a>). Interested developers (part=
icularly, but not<br>
only, third-party devs) could simply download and unpack these, and be sure=
 to<br>
get a working environment - even years later. I think that would be one gre=
at<br>
way to lower the entry barriers to KDE on Windows development.<br>
<br>_______________________________________________<br>
Kde-windows mailing list<br>
<a href=3D"mailto:Kde-windows@kde.org">Kde-windows@kde.org</a><br>
<a href=3D"https://mail.kde.org/mailman/listinfo/kde-windows" target=3D"_bl=
ank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
<br></blockquote></div><br>

--00151759329e4d6e3104d2f49165--

--===============2679297494368706918==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows

--===============2679297494368706918==--