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

List:       kde-devel
Subject:    Re: i18n freeze ?
From:       Stephan Kulow <coolo () kde ! org>
Date:       2000-10-19 14:25:51
[Download RAW message or body]

Derek Fountain wrote:
> 
> > No! The KDE_2_0_BRANCH will remain under message freeze. HEAD branch will be
> > openend for feature commits and messages later today. If for some reason you
> > think you have to updated/fix a message in KDE_2_0_BRANCH, ask on
> > kde-i18n-doc fopr permission first.
> >
> > Speaking of bug fixes, KDE_2_0_BRANCH is intended for ciritcal bugs only. If
> > you however _want_ to have your khtml fixes in HEAD and the 2.0.1 release,
> > feel free to backport them from HEAD to KDE_2_0_BRANCH. But it is _not_
> > required. It _is_ required however to port all fixes you commit to
> > KDE_2_0_BRANCH to HEAD.
> 
> Can I just confirm I've got this right? I think Thomas asked
> this a couple of days ago, but I didn't see a response to
> his question.
> 
> KDE_2_0_BRANCH is the branch which contains the official
> KDE-2.0. I thought this was frozen last Monday (3 days ago)
> and the packages tarballed up for the packagers. Clearly
> not, since it's still open for critical bugs. OK, revising
> my idea of what is going on, the tarballs were taken last
> Monday, and that is the version the users will use next
> Monday, right? In the meantime, critical bug fixes are still
> going into that branch, but no new features. Therefore
> packagers _might_ choose to update their packages from that
> branch in a few weeks time, in order to give their users
> KDE-2.0.1, which will be the same as KDE-2.0, only more
> stable?
> 
> The HEAD branch remains the unstable development branch, and
> will soon open up for more features, etc, which will
> eventually go towards KDE-2.1.0.
> 
> Have I got this correct? The reason I ask in such detail is
> that I wanted to update my tree last night for my "live"
> desktop, and it occurred to me that I didn't know quite what
> I should be fetching to get the most stable version of the
> code. I ended up just getting HEAD.
> 
> While I'm on the subject, is there a method of getting a
> list of the branches from the CVS server?

The most common is cvs log admin/Makefile.common and look
what tags are there. We tried to name branch tags with _BRANCH :)

Greetings, Stephan

-- 
... but you ain't had mine
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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