Berin Loritsch wrote:
My suggestion is to bring up the issue on the Pheonix dev list, and require them to bring Phoenix into a compilable and consistent build.
As Stephen has already pointed out, this *is* the phoenix dev list.
Peter is still able to submit patches, and has done so in a number of occasions.I suggest we give the Phoenix developers one week to make it stop the GUMP build errors. If it cannot, we revert the code base to the last CVS date that it was working. I know there are Phoenix developers who can pick up where Peter left off. I have a feeling he was in the midst of a bunch of changes/updates to Phoenix/Info when his commit privs were suspended. It presents a problem in that Phoenix development has essentially stopped in the middle of a change.
Either Phoenix has a community or it does not belong in an ASF hosted cvs repository.
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>