RFC: Moving Java PRs to Gcc database

[Bryce McKinlay]

Tom Tromey wrote:

> I was planning to leave the old database up indefinitely.  The only
> change would be that it would no longer be possible to create new PRs.

Once the PRs are moved, I think the old database should go away. It would
be confusing to have an old obsolete database that never gets updated.
The same goes for the old cvs repo, which I think should be killed off
sooner rather than later. When classpath moved their cvs without closing
the old one down, there were still mailing list messages months later
from people who hadn't been following the mailing list, wondering if the
project was dead because there had been no updates.

> The fact that the old database would stay around is why I wasn't going
> to move closed/feedback/suspended PRs.  However, I don't have strong
> feelings about this.  I think moving closed PRs won't hurt anything
> (most people won't even notice them).

> Does this address your concern?  Or does it just make the situation
> worse, by ambiguating PR numbers?

Thats fine. As long as all the PRs get moved then I'm happy. However,
another issue that I thought of is will we still be able to get mail
notification of new Java PRs without having to get notified of all gcc
PRs? One cool bugzilla feature is that it has nice user options to
filter/control what bugs you get email notification of.

regards

  [ bryce ]