[Pkg-clamav-devel] repo set up
Stephen Gran
sgran at debian.org
Wed Sep 3 11:05:52 UTC 2008
This one time, at band camp, Michael Tautschnig said:
> [...]
> >
> > My idea of workflow is to clone the group repository and add the
> > read only clamav-devel as a remote. When doing a new version
> > release, it should be possible to just pull the HEAD of the relevant
> > upstream branch (upstream/0.93, currently). When security or other
> > issues arise, it should be possible to just cherry-pick a commit
> > from upstream HEAD, which we see as master - in that case, just
> > update master from the remote and then cherry-pick into the
> > appropriate distro branch(es).
> >
> [...]
>
> Just one unmentioned workflow: Local bugfixing - am I right that this
> happens in the debian/unstable branch?
In general, yes. The etch-volatile and etch-security branches shouldn't
be updated too much, if we can help it (sometimes patches to the
packaging in unstable need to be cherry-picked into the etch-volatile
branch to deal with upstream changes, but I'm trying to minimize it a
bit - minimal changes to stable and all that).
> What about commit-mails? Are these set up, or should they be enabled
> for specific users instead of sending commits to the list?
I haven't set it up yet. I'll create a clamav-commits list and get
commit mails working. That way people don't have to see them if they
don't want to, but can easily if they do.
Cheers,
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : sgran at debian.org |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20080903/d3a9d92f/attachment.pgp
More information about the Pkg-clamav-devel
mailing list