| Re: [AD] Proposal for new branch |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2004-08-30, Peter Wang <tjaden@xxxxxxxxxx> wrote:
> ... Then we need a link to a more detailed document explaining
> what's going to happen with the new & old APIs issue.
Is this document meant to be included in the WIPs documentation? If
so, it could be added to the CVS like another help._tx file or
whatever, and I'll get the text from it. If it is meant to be showed
only on the web page, I would suggest posting here or sending
me directly the raw text. I will format it in restructured text
(http://docutils.sourceforge.net/rst.html) and put it somewhere.
> Also, the front page should say something about what's happening.
> And disclaim AllegroPro, please!
Ah, I don't know what's happening. I guess I'm too happy with the
delete key. Besides, disclaim AllegroPro? I think it's clear that
it was started by Kroval. Some text like this perhaps?
Allegro lives!
It's back from limbo and it is going to rock your world. Allegro
development has taken a new breath and is recovering to a healty
state. Proof of this is the fact that the Allegro 5 mailing lists
has been closed with it's discussion moved to the main developer
mailing list, and the recent creation of a new branch in the CVS
<link> named new_api_branch. The path for Allegro will be now blah
blah blah and some more blah blah without forgetting blah.
Note that this is different from the AllegroProCore project started
by Korval several months ago. Korval's code doesn't follow the
proposed designs which have been discussed publicly on the mailing
lists. It is a solitaire project at the moment with it's own goal,
and it is not endorsed by the current Allegro developers.