[Pkg-puppet-devel] Fwd: Do we need different debian/ubuntu maintainer groups?

[Mathias Gug]

Hi,

On Tue, Jun 01, 2010 at 12:38:34PM -0400, Mathias Gug wrote:
> 
> On Sat, May 29, 2010 at 05:01:49PM -0700, Nigel Kersten wrote:
> > Ok. What's the next step then?
> > 
> > ubuntu folks, is there a nailing list for your team?
> > 
> 
> As the next step I think we should look at the workflow used by the tomcat
> maintainers as a starting point.
> 

I've talked with Thierry Carrez who is involved wit the tomcat maintenance from
the Ubuntu side. He has commit access to the tomcat Debian svn repository where
he pushes most of his changes. And then once in a while one of the Debian
maintainer uploads the tomcat packages to Debian. Then Thierry takes care of
pulling it into the archive if necessary (if DebianImportFreeze [1] is in
effect).

[1]: https://wiki.ubuntu.com/DebianImportFreeze

Packages may get out of sync because of the freezes in effect in Ubuntu (after
Feature Freeze for example Ubuntu won't get a new upstream version by default).
See the MaverickReleaseSchedule [2] for an overview of the Ubuntu release cycle
and the different freezes.

[2]: https://wiki.ubuntu.com/MaverickReleaseSchedule

For now the workflow is to push all the Ubuntu changes in the Debian bug
tracker (I've just updated existing bugs and filed new ones for all the changes
that the Ubuntu package carried in Lucid). I've based all the patches on the
Debian git repository and thus they should apply cleanly. It's now up to
someone that has commit access to the git repository on the Debian side to
review, discuss and apply the patches.

One proposal is to give commit access to the Debian git repository to an Ubuntu
developer so that most of the packaging work can be directly committed to
Debian without having to go through the Debian BTS. If this seems unreasonable
we can stick with the current process of filling bugs in BTS and waiting for
someone on the Debian side to perform the patch review.

-- 
Mathias Gug
Ubuntu Developer  http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20100603/afe6186f/attachment.pgp>