[AD] About 4.3

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


Elias asked about the SVN repository.  When we convert the CVS
repository to Subversion, we should get something like this:

    /trunk
    /branches/4.0
    /branches/new_api_branch
    /tags/4.0.0
    /tags/4.0.1
    /tags/4.0.2
    /tags/4.0.3
    /tags/4.2.0

We can do a copy from /trunk to /branches/4.2, then delete /trunk.  Then
we can move /branches/new_api_branch to /trunk if we want, but it's not
necessary since the name "trunk" is just a convention.  Subversion
doesn't actually care.


The stuff sitting in the new_api_branch at the moment is enough for a
4.3.0 release, except that the OSX port is broken.  Peter Hull, I'm not
putting any pressure on you, but if you have some free time ;-) Anyone
else with a Mac that wants to help out, please come forward!  I will try
to answer any questions about what needs to be done, but basically the
keyboard and joystick drivers need to be updated for the new event
system.  Maybe something broke with regards to the gfx drivers as well;
Evert should know.

To keep the new_api_branch relatively stable for our intrepid Mac
hackers, intrusive changes should be put into branches.  For example, I
have a mouse API half finished here but if I commit it now it will only
make it harder to bring the Mac port up to scratch (plus the Windows
port will be broken).  I was going to wait for SVN before making a
branch for that, but unless we go with alternative hosting that may be
too long.

Alternative hosting: we can try either gna.org (licence scrutiny not
withstanding) or berlios.de (if they are not overloaded).  Or if someone
from the Allegro community can offer us temporary hosting then that
would probably be easiest...

Peter





Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/