[AD] Announcement: New CVS module opened / Allegro 5 work started. |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Allegro Conductors <conductors@xxxxxxxxxx>
- Subject: [AD] Announcement: New CVS module opened / Allegro 5 work started.
- From: Henrik Stokseth <hstokset@xxxxxxxxxx>
- Date: Fri, 18 Jan 2002 18:26:59 +0100
Today, I opened a new cvs module @ sourceforge which is intended for work on
what will eventually become Allegro 5.0.
Everybody is welcome to participate. I see there's already been a whole lot
of constructive suggestions from people about what they would like to see in
the next version, and that's good.
When we now have two codebases to work on it's important that people are a
little aware when sending/committing patches. If you are unsure, send the
patch to the mailinglist or post an url to it if it's big. bugfixes are
committed to both 'allegro' and 'allegro_new', the same goes for small
features. try to create two patches, one relative to 4.0 or 'allegro' and one
relative to the 'allegro_new' codebase, it makes things easier for those who
commit the patch. patches which implies ABI breakage, API changes, redesign
or otherwise big changes to the codebase are to go in 'allegro_new' only. in
other words 5.x stuff.
Grzegorz, I beleive you can al_ prefix the whole 'allegro_new' module now.
Other changes will have to be approved by an admin, (Peter, Eric or Michael)
before they are committed, unless of course you're absolutely sure they are
ok.
--
Sincerely Henrik Stokseth.
-----------------------------------------------------------------------
E-mail: hstokset@xxxxxxxxxx Homepage: http://hstokset.n3.net