Hi Jonas and Alessio, I was concerned about the extra commits in the git repository firing off messages, but I realize it's probably only certain branches triggering this.
Alessio, in the workflow you described, the upstream.trunk branch is what I was referring to as "intermediate packaging work" I have an account on alioth (jeremysalwen-guest) and I requested to join the team a little while ago, but I haven't been accepted yet. as for > I have asked you to remove the debian directory at least from the release tarballs just to save some KiBs. I wasn't aware the dir was included. I'll try to fix that in the future. I'll try to set up the git repositories properly once I have a change. There's this project I'm working on that I'm really pushing to finish right now, so I'll probably be inactive for a few more days. Jeremy On Mon, Jun 20, 2011 at 11:50 AM, Alessio Treglia <ales...@debian.org>wrote: > Hi Jeremy, > > sorry for the long delay. > > On Sat, Jun 18, 2011 at 10:08 AM, Jeremy Salwen <jeremysal...@gmail.com> > wrote: > > A little confused. I do upstream development and debian packagin in the > > same git repository. > > And this isn't bad, you can develop your software the way you prefer, > however the packaging should be reviewed through our git repository. > > > If you're asking me to remove the debian directories from the upstream > > branch, no need, there is no debian directory in the upstream branch. > > I have asked you to remove the debian directory at least from the > release tarballs just to save some KiBs. > > > 1. upstream work is allowed in the pkg-multimedia repository > > There wouldn't be any particular problem for me. A good workflow may be: > > 1. Work on upstream side by committing the changes into a new > upstream.trunk branch. > 2. Once the sources are ready to be released: > a. Merge "upstream.trunk" into "upstream" and tag the latter > properly ("upstream/%(version)s"). > b. Prepare an orig.tar.gz, commit it into the pristine-tar branch > c. Merge upstream into master. > > > 2. intermediate packaging work is allowed in the pkg-multimedia > repository > > I fail to catch the point: what does "intermediate packaging work" mean? > > > 3. it would be okay to have the github and pkg-multimedia repositories > sync > > up. (or at least share commits). > > There would no need to set up such a sync if you follow that workflow > I drafted above. > > > 4. Am I supposed to have write access to these repositories, or is that > > reserved for DDs? > > You'd just need to have an account on Alioth and join the team. > > Cheers, > > -- > Alessio Treglia | www.alessiotreglia.com > Debian Developer | ales...@debian.org > Ubuntu Core Developer | quadris...@ubuntu.com > 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 >
_______________________________________________ pkg-multimedia-maintainers mailing list firstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers