Fwd: Re: [Kde-cvs-announce] Dev Platform Tagging Freeze Next Week

[Tom Albers]

Hi,

It's news to me too.

I don't think this should be done this way. kdesupport follows kdelibs release path. 

So they should not use trunk kdesupport to work on the next version. In case they want to work on the next version, maybe they should move to extragear/libs like any other application/library.

-- 
Tom Albers	

At Wednesday 07 November 2007 02:02, you wrote:
> I didn't know this.
> This could lead to all kinds of mess.
> 
> I wonder if we should svn copy kdesupport/qca kdesupport/qca2
> and change the build instructions to say use qca2??
> 
> Comments?
> 
> ----------  Forwarded Message  ----------
> 
> Subject: Re: [Kde-cvs-announce] Dev Platform Tagging Freeze Next Week
> Date: Tuesday 06 November 2007
> From: Justin Karneges <justin at affinix.com>
> To: Allen Winter <winter at kde.org>
> 
> Hi Allen,
> 
> qca-2.0.0 from kdesupport was released last month.  Since then, development 
> has moved forward in trunk.  Because of this, KDE should target the 2.0.0 
> release, not trunk.  If by "Tagging Freeze" you refer to svn tags, I don't 
> think it makes sense to tag the qca trunk.  If it gets tagged simply because 
> you are tagging kdesupport or some parent directory, then that's fine, but I 
> hope nobody would use the qca found in that tag then.
> 
> Additionally, the KDE4 build instructions [1] should not suggest using an svn 
> version of qca.  Instead, it should suggest release packages [2].
> 
> -Justin
> 
> [1] http://techbase.kde.org/Getting_Started/Build/KDE4
> [2] http://delta.affinix.com/qca/
> 
> On Tuesday 06 November 2007 3:18 pm, you wrote:
> > Howdy,
> >
> > For planning purposes, we thought you'd like to know that
> > the next Tagging Freeze is coming Tuesday 13 Nov at midnight.
> >
> > The freeze is to make life easier for the tagging of the
> > next Development Platform release and only affects:
> > kdesupport, kdelibs, kdepimlibs, kdebase/runtime and kdebindings.
> >
> > The application modules (kdepim, kdenetwork,etc ) are not
> > covered under this particular freeze.
> >
> > So, plan accordingly.
> >
> > Regards,
> > Allen, KDEPIM Release Dude
> 
> 
> -------------------------------------------------------
> 
> _______________________________________________
> release-team mailing list
> release-team at kde.org
> https://mail.kde.org/mailman/listinfo/release-team