From kde-windows  Thu Jan 10 19:30:37 2013
From: "Thomas Friedrichsmeier" <thomas.friedrichsmeier () ruhr-uni-bochum ! de>
Date: Thu, 10 Jan 2013 19:30:37 +0000
To: kde-windows
Subject: Re: Emerge : error while install kdelib on windows with emerge python 33 no module info
Message-Id: <201301102030.42609.thomas.friedrichsmeier () ruhr-uni-bochum ! de>
X-MARC-Message: https://marc.info/?l=kde-windows&m=135784627021472
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2330156236301835101=="

--===============2330156236301835101==
Content-Type: multipart/signed;
  boundary="nextPart2076087.5ytkk14NXY";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2076087.5ytkk14NXY
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

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=20
recommendation for 4.9 is simply based on my personal - and thus extremely=
=20
narrow - experience. 4.9 gave me less trouble than 4.8. But yes, almost=20
certainly there will be regressions, too.
=20
> 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. Beside=
s=20
that we'd keep whichever branch(es) is(are) the focus for the next binary=20
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,=
=20
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"=
=20
would be fairly desirable(*). But IMO, that's not a top priority for emerge=
=2E=20
If you want a stable *release*, you can use the binaries. But the key selli=
ng=20
point for emerge is that you want to do development (or stand at the bleedi=
ng=20
edge, watching develoment). For that purpose you're most likely to pick the=
=20
youngest branches.

Regards
Thomas

(*): Talking about archives: Suppose, every time a release has been created=
,=20
self-contained snapshots of the build root would be created (one for each=20
arch), archived, and offered for download. I.e. something like what I've=20
zipped up for kde 4.9, mingw4, 32bit (http://lists.kde.org/?l=3Dkde-
windows&m=3D135541718223018&w=3D2). Interested developers (particularly, bu=
t not=20
only, third-party devs) could simply download and unpack these, and be sure=
 to=20
get a working environment - even years later. I think that would be one gre=
at=20
way to lower the entry barriers to KDE on Windows development.

--nextPart2076087.5ytkk14NXY
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEABECAAYFAlDvFt4ACgkQEKRv+5DVNhhh2gCgt47hSQX7+1tpbNVotDzq4lQb
ToUAnjm5Cm7pf/aVkErNAAANUBDO81g3
=k5UM
-----END PGP SIGNATURE-----

--nextPart2076087.5ytkk14NXY--

--===============2330156236301835101==
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

--===============2330156236301835101==--