67 | | disappears, along with copies of items in the issue-tracker (though |
68 | | only as HTML dumps of the pages), and the material on the sunsource |
69 | | web site. The active ones have been transferred |
70 | | to the [ticket: issue tracker] here, but have somewhat suffered in the |
71 | | process. If the Sunsource mailing list archive disappears, you can still use |
| 69 | disappears, along with copies of items in the issue-tracker, and the |
| 70 | material on the sunsource |
| 71 | web site. The active issues have been transferred |
| 72 | to the [ticket: issue tracker] here, but some have somewhat suffered in the |
| 73 | process, since I only discovered after the fact that they were |
| 74 | accessible as an XML dump. |
| 75 | If the Sunsource mailing list archive disappears, you can still use |
105 | | project, but should be soon. You can create an account to put tickets |
106 | | in the [ticket: issue tracker], or use the `tourist` account with |
107 | | `sge` as the password, but there will eventually be a bugs email list. |
| 110 | project, but should be soon. Note that you can't currently reply to |
| 111 | any mail, such as notifications of tickets. You can create an account |
| 112 | to put tickets in the [ticket: issue tracker], or use the `tourist` |
| 113 | account with `sge` as the password. (It will eventually be possible |
| 114 | to make bug reports by mail.) |