-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Apr 10, 2008 at 3:24 PM, Tom Lane wrote:
> "Brendan Jurd" writes:
> > Personally I don't feel that using a patch tracker or wiki is any more
> > onerous than using an email list, and it's a whole lot more responsive
>
> There are a couple of differences in my mind. One is that the email
> list provides an automatic historical archive, whereas trackers tend to
> be all about current state.
They do? We must be thinking about different species of trackers
then, because not only do trackers like bugzilla and Trac have
automatic historical archives, but they are much easier to query than
an email archive.
Even a wiki page has a built-in history (list of changes) although
admittedly this is not friendly to queries like "have we already
rejected similar patches" and such.
> Another is that the email list provides a
> "push" mechanism for putting the proposed patch under the noses of a
> bunch of people, a few of whom will hopefully take a sniff ;-).
> A tracker is very much more of a "pull" scenario where someone has to
> actively go looking for pending/proposed changes.
>
The typical way to solve this is to have the tracker send an automatic
notification email to a list saying "Hey, there's a new ticket at ,
come and check it out".
This is trivial to configure in a "real" tracker. Less so for a wiki
page, but it could still be accomplished with the careful application
of script-fu.
Cheers,
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org
iD8DBQFH/asy5YBsbHkuyV0RAkJoAJ9yJCZ1da5FN015xxmKY1g5LbAzygCfUpXQ
xJ0S/rcBzv2S3L8mQxz9aAs=
=MzEJ
-----END PGP SIGNATURE-----