"Joshua Slive" <[EMAIL PROTECTED]> wrote:
>> 5) Potentially add a bugzilla.apache.org CNAME that is a redirect
>> to http://nagoya.apache.org/bugzilla. [DNS and httpd admin]
>
> Not done: Someone suggested issues.apache.org, but I don't particularly
> care.
A "neutral" name can be used in the next transition as well... (To Tigris'
Scarab)...
>> 7) Configure bugzilla accordingly so that it sends an email to a
>> ML. If you are subscribed to tomcat-dev@, you know how it works -
>> any time a new bug is created, it sends an email, any time changes
>> are made, it sends an email. I'd say [EMAIL PROTECTED] would
>> be a good name. IMHO, we should move it over to a new list instead
>> of reusing the old one (apache-bugdb) that is on the wrong domain
>> anyway. [Daedalus 'apmail' and bugzilla admin]
>
> Partially done. The list will get all emails unless someone takes
> ownership of a bug and forgets to add the list as a cc. Not exactly
> ideal. Any suggestions? Or should we just live with this until the
> next migration.
Scarab should fix that, and if it doesn't, we can fix scarab...
>> 9) Configure bugzilla to send monthly/weekly (?) reports to dev@httpd
>> identifying confirmed PRs. I believe tomcat-dev@ gets these.
>> Personally, I don't care to be subscribed to bugs@httpd ML (it'll
>> be high-traffic), but I would like to see a summary once in a
>> while. [Bugzilla admin, but subject to dev@httpd consensus]
>
> Not done. I don't particularly care about this. Marc used to do this
> for gnats, but I don't think it had much of an effect. If people never
> look at the bug database, this isn't going to change.
Isn't it? Oh, no... Whops, I forgot! :) I'll fix it in the morning...
Pier
