Freezes and Git Migration

[Andreas Pakulat]

Hi,

as we discussed before we'll be moving to git as soon as possible after
the 4.0 release.

My current plan for the migration is to set extragear/kdevelop and
extragear/kdevplatform to read-only on May 1st (in worst case I'd have
to wait until Monday if no sysadmin is available), to make sure that I
can do a final rsync of the repo and then generate the git repository.

This means that from Apr. 28th until we're in git there'll be complete
commit freeze (with the exception of 28th - May 1st for release-critical
bugfixes like wrong version numbers or build-problems). 

If everything goes well we should have a git repo up and running within
a few days (which I'll announce here of course). Once we have I'll
replace the content of the two directories with a README pointing to the
git repository. I'm not sure what to do about the existing branches, but
since there's no active ones there's enough time to handle that.

One last thing: I'm not sure wether we talked about this yet, but once
we do live in git I think we should go with the usual (at least for
now): "Bugfixes should always be done in the oldest branch that you want
it to be in, usually not in master" and then merge the current stable
branch into master on a regular basis (I'm thinking about once a month).
There are other development models (amarok uses one, another is
explained here: http://www.nvie.com/git-model), so if anybody is of
different opinion please open a new thread about that.

Andreas

-- 
You will soon meet a person who will play an important role in your life.