-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 5, 2009, at 1:19 PM, Thijs Kinkhorst wrote:
On Monday 5 January 2009 17:09, Mark Sapiro wrote:
Please don't start (or extend) a list of downstream things to look at
in the week before a release. First of all, I'm just compulsive
enough
to actually look, but even so, the most likely result is I'll be
overwhelmed, defer everything and then forget about it.
I have on behalf of Debian a while ago reported a number of our
patches to the
SF.net tracker, which have not seen any response yet. It's not that
we're not
willing to contribute patches back, but the previous approach of
reporting
them to the patch tracker hasn't been fruitful. I have also sent
selected
patches to the development list in the past with the same result.
So I guessed I'd try something different instead.
If downstream patches are of general applicability or address bugs in
the upstream distribution, they should be reported in the upstream
tracker (currently <https://bugs.launchpad.net/mailman>).
Do I understand it correctly that I should resubmit the patches to
this new
tracker?
We're quite willing to help you get useful patches integrated, but
our time is
also limited so I'm looking for the way that is most effective for
both of
us.
I'll let Mark determine what works best for him an MM2.x, but a couple
of comments: first, the SF tracker issues /should/ have been migrated
to Launchpad. If not, it'll be quicker to resubmit them.
Second, I think in general if you can push bug fix branches to
Launchpad and link them to the bug, they will be much easier to review
and merge into the official branches. Patches in a tracker are more
difficult to use, but probably easier to generate. You could also try
'bzr send' to create a bundle, which is somewhere between a branch and
a patch.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkliWm0ACgkQ2YZpQepbvXEzmQCdH7L8ir2kWqcgQnpWwZuj5/Yj
Za0AnR80n/z/z1ym/3kYSC1weFvaKIXP
=3AHS
-----END PGP SIGNATURE-----
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
