[Pkg-salt-team] Backporting

[martin f krafft]

also sprach Joe Healy <joehealy at gmail.com> [2013.08.25.0216 +0200]:
> cython
> libzmq3
> python-zmq > 13
> 
> cython and libzmq3 can be done at the same time, python-zmq depends on
> the others so must be done afterwards. Once all of these are in then
> we can do salt itself.

Are you going to have to do all of these? Or are the respective
maintainers willing to maintain the backports, maybe after you
prepared them? Maintaining a backport does include uploading
security fixes, when they come around…

> Given we are looking at 3 stages (cython and libzmq3, python-zmq
> then salt) by 2 distributions is it worth giving the backports
> list advanced warning of the plan?

This never hurts; however, it's also not necessary. It's more
important that the maintainers of the packages involved are aware.
You could write a message to all of them and CC the backports list.

Thanks for your work on this!

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
"my experience is that as soon as people are old enough to know better,
 they don't know anything at all."
                                                        -- oscar wilde
-------------- next part --------------
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1124 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL: <http://lists.alioth.debian.org/pipermail/pkg-salt-team/attachments/20130825/d7aedbd3/attachment.sig>