frameworks -> debian-git notes

Harald Sitter apachelogger at ubuntu.com
Mon Sep 22 09:39:42 UTC 2014


random notes for the debian-git notes

# previous mail

note the previous mail on git prep, in particular the gitconfig aliases

# repo path on git.debian

repos should be created in
    /git/pkg-kde/frameworks/${source_name}.git

# repo creation

to create the initial repo one should use a fancy script on the server side:
  - cd /git/pkg-kde/frameworks/
  - ../setup-git-repository ${source_name}

# repo import

to import bzr first clone the remote repo and then export|import
  - git clone debian:frameworks/${source_name}.git
  - knextbzr co ${source_name} ${source_name}_bzr
  - cd ${source_name}
  - bzr fast-export --plain ../${source_name}_bzr | git fast-import
make sure the history is correct and all files are there; then push with --tags

should you encounter problems simply ditch it and copy everything
without history into the empty git clone to do a fresh import into
git... this should be good enough as we do not have much valuable
history for frameworks anyway

# branch setup

IIRC there was no absolute conclusion on what the branch setup should
be so simply throw everything in master for now, we'll cleanup later

supposed setup:
- master (moving debian packaging)
- debian/stable
- debian/unstable (assuming master isn't suitable for whatever reason)
- kubuntu/utopic/unstable (CI branch tracking upstream master)
- kubuntu/utopic/5.2 (CI branch tracking upstream stable for utopic)
- kubuntu/utopic/5.2.0 (release maintenance branch)
- kubuntu/utopic/5.2.1/ppa (ppa update branch)
^ all the kubuntu version bits may be argued to not have a version
unless the version is divergent from whatever is landed in archive/ppa

on our side all branches are derived from unstable and as such
unstable is the merge target for all branches on our side.

more to follow on branching from our side WRT CI following soon.

HS



More information about the kubuntu-devel mailing list