Re: [AD] Announcement: New CVS module opened / Allegro 5 work started.

["Eric Botcazou" <ebotcazou@xxxxxxxxxx>]

> Today, I opened a new cvs module @ sourceforge which is intended for work
> on what will eventually become Allegro 5.0.

Don't forget to tag the current Allegro 4 trunk with ALLEGRO_5_FORK_POINT or
something alike, so that we know where the module starts from.

> 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.

I think that's over-complicated. IMHO bugfixes need only be diffed against
the current stable (4.x) series.

> Grzegorz, I believe 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.

We are at a very early stage of development, so I think such a strong
control is not really necessary. If a patch/feature is discussed and agreed
on by the [AD] people, then any CVS commiter can apply it to the module.

--
Eric Botcazou
ebotcazou@xxxxxxxxxx