Yes-
People just need to agree to send all patches to RT first so that
they can be tagged in their subject line, so discussion gets
tracked. For now, RT needs to be CC'ed on followups - soon it
will just "listen".
When Simon/Dan/$PATCHER applies/rejects a patch, they can tag the
ticket as patch-applied or patch-rejected, and then close the
ticket.
Do we want these to be in the same queue as parrot bugs? I don't
see why not.
Eventually, we will develop a custom interface to these patch
tickets.
-R
(Once we start using RT there will be a little bit of tweaking to
get things right - things we can't do until we know what the
changes are.)
Nathan Torkington writes:
>Simon Cozens writes:
>> So maybe the best thing would be for people to send patches to the
>> list and Cc [EMAIL PROTECTED]
>
>I wonder if, when RT comes online, we could use that to manage the
>patches. In other words, patches become open "to do" items, which are
>cleared when the patches are definitively applied or rejected.
>
>Nat
--
