Differences between revisions 6 and 7
Revision 6 as of 2010-10-11 15:47:30
Size: 3298
Editor: DidierRaboud
Comment:
Revision 7 as of 2010-10-15 07:28:06
Size: 3648
Editor: DidierRaboud
Comment: Add mt-compositor
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
|| DebianPts:meegotouch-compositor || DebianBug:600202 || [[http://git.debian.org/?p=pkg-meego/meegotouch-compositor.git|Git]] || [[http://meego.gitorious.org/meegotouch/meegotouch-compositor|meegotouch-compositor]] || [[http://meego.gitorious.org/~odyx/meegotouch/meegotouch-compositor-clean|meegotouch-compositor-clean]] || DidierRaboud || … ||

Debian meego maintainers

Infrastructure

Interacting with the team

  • Mailing list: <pkg-meego-maintainers AT alioth DOT debian DOT org>

  • Public IRC channel: #debian-meego on irc.debian.org (OFTC)

Packages list

Package

ITP

VCS

Upstream git

Cleaned up git

Uploaders

Comments

libmeegotouch

597295

Git

libmeegotouch

libmeegotouch-clean

DidierRaboud

meego-packaging-tools

592314

Git

meego-packaging-tools

N/A

?FathiBoudra

mic2

578170

Git

image-creator

N/A

?FathiBoudra

meegotouch-compositor

600202

Git

meegotouch-compositor

meegotouch-compositor-clean

DidierRaboud

meegotouch-theme

599738

Git

meegotouch-theme

meegotouch-theme-clean

DidierRaboud

spectacle

592311

Git

spectacle

N/A

?FathiBoudra

Packaging practices

''upstream'' branches

Despite the [Proposal] Packaging management in DVCS mail, most upstream repositories still ship packaging files (debian/, *.spec, *.yaml files and directories). In order to workaround this, DidierRaboud runs a "cleaning" script bi-daily that pushes to gitorious too. The master branch of said "cleaned" repository doesn't contain the packaging files and upstream/${version} tags are created with "git changelogs" included. This master branch is regularly (hand-)merged into the "upstream" branch of the alioth git repositories.

Additionally, as the upstream/${version} are git leaves (not in the chain of commits leading to "upstream"), most alioth repositories include a "mergeNewUpstreamRelease.sh" that should be called from the "master" branch as $ debian/mergeNewUpstreamRelease.sh upstream/${version} . This handles the merging and the pristine-tar generation.

Usertags

Here is a proposal for the use of usertags (or user categories):

User: pkg-meego-maintainers@lists.alioth.debian.org

Usertags actually in use: