[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
[Repost because I didn't receive anything]
The 4.0.1 version was released nearly three months ago and it seems we have
enough new material in the 4.0.x branch to make up a 4.0.2 release:
http://membres.lycos.fr/ebotcazou/dev/allegro_4_0_branch-20020605-change.log
Moreover, several modifications made on the trunk could be backported to the
branch:
2002-03-19 11:41 ebotcazou
* allegro.cfg, docs/src/allegro._tx, src/win/wddwin.c: Added an
option to disable direct updating in color conversion mode under
Windows
2002-04-22 05:39 tjaden
* makefile.vc, misc/zipwin.sh: Don't look at MSDEVDIR any more,
only MSVCDIR Note: backport this after testing
2002-04-24 17:15 ebotcazou
* makefile.mgw: Henrik fixed installation under Cygwin
2002-04-24 17:37 ebotcazou
* docs/build/mingw32.txt: Henrik updated build instructions for
Cygwin
2002-04-27 08:13 ebotcazou
* docs/src/allegro._tx: Added a warning about the use of blocking
functions under Windows
2002-05-11 09:37 ebotcazou
* allegro.cfg, resource/keyboard/cf.cfg: Maxime Carey added a
Canada (French) keyboard mapping file
2002-05-11 18:12 svens
* examples/exswitch.c: Prevented watcom from crashing by fp
exceptions, and made fractal faster
2002-06-01 15:53 svens
* resource/language/setext.cfg: Added many strings (in particular
drivers) to Swedish translation
2002-06-03 14:52 svens
* resource/language/setext.cfg: added "BeOS joystick" translation
2002-06-03 22:20 svens
* makefile.mgw: make install now creates system directories
Comments ?
The complete changelog for trunk and branch is located at:
http://membres.lycos.fr/ebotcazou/dev/allegro-20020605-change.log
We also have to decide what to do with the new drivers recently posted on
the list: should they go in the 4.0.2 release ? I personally don't think so,
primarily because of a lack of testing. [Off topic: I think we should
quickly release a 4.1.0 WIP version after the 4.0.2].
I'm ok to act again as the release manager for that one, provided that
nobody disagrees. I think the release process should be far more
straightforward than that of the 4.0.1 because the branch was cut from
day one (contrary to what happened for the 4.0.1 release). The main goal
is again 0 regression with regard to the previous release. The list of
platforms is still the same:
8 primary platforms:
- DJGPP,
- Watcom (DOS),
- Mingw32,
- MSVC,
- Borland C++ (Windows),
- BeOS,
- QNX,
- Linux,
3 secondary platforms:
- FreeBSD,
- Solaris,
- IRIX
The 4.0.1 release reportedly worked out of the box on the first 9 platforms.
Hopefully we can do even better !
--
Eric Botcazou
ebotcazou@xxxxxxxxxx