[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: comments / issues / and thoughts mentioned by a new linux/kde user
From:       Christian Parpart <cparpart () surakware ! net>
Date:       2002-12-25 20:07:34
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 25 December 2002 3:02 pm, Christopher Molnar inspired the 
electrons to say:
> On Wednesday, December 25, 2002, at 08:52 AM, James Richard Tyrer wrote:
> > Andras Mantia wrote:
> >> On Wednesday 25 December 2002 08:22, James Richard Tyrer wrote:
> >>> Is there some reason that you didn't check it out with the tag:
> >>> 3_1_0_RELEASE?
> >>>
> >>> Using HEAD is not a good idea.
> >>
> >> Yes, right now it's advisable to use KDE_3_1_BRANCH (and not the
> >> release...) instead of HEAD.
> >
> > OK, but this is a special circumstance isn't it?
> >
> > Usually, the last release is more stable than the BRANCH?
>
> Not in the KDE CVS. HEAD is current development, untested code and so
> on. You risk disaster when you use HEAD (not really that bad, but it
> makes my point).  There are a lot of times 1/2 finished changes
> committed to HEAD - sometimes won't compile. Only thing it will
> definitely do is take up hard drive space :-)
>
> KDE_3_1_BRANCH is a release branch. It will compile and it is stable
> (we hope). Anytime a branch is created with KDE_X_XX_BRANCH it is a
> release version tag. Use that unless you are really brave.
>
> Hope that helps.

Well, of course, I know about KDE_3_1_BRANCH, but this is not the point.
The intention of my initial mail was to show mainly the usability issues, not 
what branch I've installed.

Cya,
Christian Parpart.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ChAGPpa2GmDVhK0RAi4hAJ9VdoKcXEZomFM+8rzimbRivHmwSgCbBxSK
CHN1a7vFm4mRVZOA4U32yBE=
=dI3L
-----END PGP SIGNATURE-----

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]