Freezes and Git Migration

[Andreas Pakulat]

On 25.04.10 23:40:02, Niko Sams wrote:
> On Sun, Apr 25, 2010 at 22:07, Andreas Pakulat <apaku at gmx.de> wrote:
> > 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.
> >
> Yay, git :D
> 
> what about:
> - kdevelop-plugins

Thats extragear/sdk/kdevelop-plugins, right? i.e. php+php-docs?

> - quanta
> I could do the conversion... If you would set them to read only too and help
> me with uploading the repo to the correct place.

Running the conversion is a no-brainer, if the rules are complete. So if
you want the conversion to happen at the same time I can do that too
(including read-only+README), no big deal. Oh, quanta also has the
problem of afterwards fixing old tags right? Does the script take of
that completely now? If so thats fine, else I'd like to ask you to do
quanta yourself (I'll help with the final push of the repository).

> and plugins in playground should be converted by their authors manually?

Yes, there's (AFAIK) no hurry with most of them and I'd like to avoid
total mess by trying to do everything at once. In particular because
there's also some extra administrative steps (permissions, getting
translations setup and ebn/apidox). And for those plugins its not really
necessary to have them write-locked by the sysadmins as there's at most
2 persons working on them and no scripty is executed on them.
 
-- 
Beware of a tall blond man with one black shoe.