Hosted by:
Project page
|
|
Subversion read access
Subversion is a replacement for good'ol
CVS. You can get clients for most platforms at http://subversion.tigris.org/,
and there is good documentation like the Version control with
Subversion manual, by some of Subversion's authors.
You can get read access from the main URL https://alleg.svn.sourceforge.net/svnroot/alleg/.
While you can access this link directly and will see the files, that's really
boring - instead you want to use a Subversion client to check out the whole
source and make local modifications in order to send patches. Example:
svn co https://alleg.svn.sourceforge.net/svnroot/alleg/allegro/branches/4.2
(for the stable 4.2 branch)
svn co https://alleg.svn.sourceforge.net/svnroot/alleg/allegro/branches/4.9
(for the unstable 4.9 branch)
You can also use a web interface to
browse the repository, which you will find at http://alleg.svn.sourceforge.net/viewcvs.cgi/alleg/.
The Subversion tree was migrated from SourceForge's CVS repository,
so everything you used to know should be there (except the allegrowww
module).
If you need write access to the Subversion tree, please ask for
it on the Allegro development
mailing list.
Snapshots of the Subversion tree
These are snapshots of the Allegro SVN repository. The snapshots here
have been wrapped up like any normal WIP releases and are ready to compile.
Keep in mind that since these are snapshots and not actual releases,
they contain new code which has undergone little testing. Therefore
don't be surprised if you can't even compile it or if it gives you a
core dump, a bluescreen etc. So if stability is important for you, then
you should rather be using one of the WIPs.
Snapshots will be released regularly every week. The goal of these snapshot
releases is:
- To provide users unfamiliar with SVN, access to the latest Allegro
improvements.
- Increase the amount of testing that is done between each WIP release.
End-user feedback is important for the Allegro developers in order to
maintain and improve the quality of Allegro.
Available snapshots:
allegro_4_9_20071201.zip (3049 KiB),
allegro_4_9_newgfx_20070911.zip (2988 KiB),
allegro_4_9_newgfx_20070915.zip (2988 KiB),
allegro_4_9_newgfx_20070922.zip (2988 KiB),
allegro_4_9_newgfx_20070929.zip (3006 KiB),
allegro_4_9_newgfx_20071006.zip (3006 KiB),
allegro_4_9_newgfx_20071013.zip (3011 KiB),
allegro_4_9_newgfx_20071020.zip (3011 KiB),
allegro_4_9_newgfx_20071027.zip (3015 KiB),
allegro_4_9_newgfx_20071103.zip (3015 KiB).
Changelogs of the Subversion tree
Change logs for the SVN repository are generated every hour and
uploaded to the Allegro web page at SourceForge. The xml versions
are generated with the --verbose switch, unlike the text
versions. Note that these files include the whole repository
history since it was started, and they may be very big.
The SVN repository also has a commit hook for CIA, a system
for tracking open-source projects in real-time. The CIA web
interface may be easier to read than the above logs, provides
an RSS feed and notifications in the #commits channel on the
Freenode IRC network. You can monitor Allegro
activity at http://cia.navi.cx/stats/project/alleg.
|
