Fwd: KDE 4.6.3 tarballs (try#1 part1) uploaded

Jeremy Whiting jpwhiting at kde.org
Fri May 6 00:12:35 CEST 2011


Dirk,

You probably didn't see this, so resending directly to you.  Don't try to
fix the kdeedu git stuff, it's incomplete, if you want/need to release
kdeedu 4.6.3, release it from svn branch 4.6 rev 1227326, or we can do the
4.6.3 release of kdeedu next week once Nicolas has got the svn->git
migration issues fixed. I don't think it's worth delaying the rest of kde
for our mistake in kdeedu.

thanks,
Jeremy

---------- Forwarded message ----------
From: Jeremy Whiting <jpwhiting at kde.org>
Date: Tue, May 3, 2011 at 1:16 PM
Subject: Re: KDE 4.6.3 tarballs (try#1 part1) uploaded
To: KDE release coordination <release-team at kde.org>
Cc: kde-edu at kde.org


Dirk,

At this point, Nicolas has tried the reverting changes to build alone, and
has found that the kdeedu svn->git migration is incomplete.  I suggest we
either release 4.6.3 from the branches/KDE/4.6/kdeedu rev 1227326 or not
release kdeedu as part of 4.6.3 at all.  I don't think it's worth holding
the release up for us to fix the git migration and create the tarball
properly.

Jeremy


On Tue, May 3, 2011 at 6:46 AM, Jorge Manuel B. S. Vicetto <
jmbsvicetto at gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02-05-2011 21:56, Jeremy Whiting wrote:
> > Dirk,
> >
> > I got all the 4.6 branches to build as a whole kdeedu module using the
> > attached CMakeLists.txt.  I only changed the CMAKE_CURRENT_SOURCE and
> such
> > in those that wouldn't build, but maybe we should change them all.  At
> any
> > rate, would you like me to put this simple CMakeLists.txt somewhere (svn
> or
> > git) or do you just want to hold on to it until 4.6.x is done.  Are we
> going
> > to ship kdeedu as one tarball forever? or will 4.7 be separate tarballs?
>
> If the release team is considering splitting tarballs for future
> releases, as a Gentoo packager I'd like to ask you to warn us with
> enough advance so that we can review our packaging of KDE.
> It would also help if there were any policies or guidelines about
> "independent releases" of KDE apps like what just happened with marble
> so that packagers can know whether they should expect that or not.
>
> > thanks,
> > Jeremy
> >
> > _______________________________________________
> > release-team mailing list
> > release-team at kde.org
> > https://mail.kde.org/mailman/listinfo/release-team
>
> - --
> Regards,
>
> Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
> Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJNv/kgAAoJEC8ZTXQF1qEP8JIP/iXb2OueZw3YOubfNXENl1eM
> m6pplaGiLQpua3Mf38g47KPbPmNtRvMGOr39djZsF7BaD8/MnEJIkCm/RY8jAOKG
> N5OD1ne7Z98BnSyuxXTglGa042GLMo5iJlsbJ/mzLVf3L6mBWChKPr5Gjy7xcFlM
> If6wjOV6oMfj5IOhm9NfcxwzobOIBH9++fQjpOrWE02XpQCP7+hwRy1j8ecYrosn
> ODD4OpA8eqgr+7a47/v/M8kCIg14g3UONMWx+F1K4LNjYLR+wlsB9PgkYBvpe78h
> Tx0L+JvHFr+sqhCoPDH+xP+81M07Uf9Qm2U/93eFq4R9tYY9/B3CgI1ub2vd9PMm
> 9H74EZxE0CNhpoLNqFfjhlMDFC7pCHMVJH5bEHah3UtqTb9CHlNASvK9Bn0ZHfAk
> fHy7t8UqI7lFj/wzEm/1UaHm9CF4A/i6hZUcD59qz8/6838I1XpcRdZmWdVDijo0
> DWv2HGrKgX/XTXCHVZpDb/tVVghyqhKHGRh4RffktEfXKMOnjLFjTvlfxLJTIPYh
> 3g7wIk8IazXrNYG2PwfdbvtjBmMdlxCAccnc44vUULWnJYIS4Cf8sT1rIwNz40/B
> m4cNHXZhXrl5ZElD3ke19tbXWHUahZR5DkIZ6Kb6G3NezGuDfcl6PtaCVnLeyiw7
> ks4eekmJ9tOPvQ4e4tfV
> =Bnm1
> -----END PGP SIGNATURE-----
> _______________________________________________
> release-team mailing list
> release-team at kde.org
> https://mail.kde.org/mailman/listinfo/release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-buildsystem/attachments/20110505/c87949f9/attachment-0001.htm 


More information about the Kde-buildsystem mailing list