Dear hackers community,

Since Mozart-1.3.1 release, several bugs has been fixed and now the sources compile with gcc-4.0, which can motivate a 1.3.2 release. Here at UCL, we want to be responsible for that, so we volunteer to do the job.

Another motivation for us is to gain expertise on making a release, taking into account the work we have carried on in the integration of Mozart and the DSS (see also MEP-102). The idea of having a Mozart-1.3.2 _does not_ include anything from the DSS, but it will give us expertise for a later release.

I have discussed this idea with Kostja, who was release manager of Mozart 1.3.0 and 1.3.1. He also agrees and is willing to help us. If nobody else volunteers, I would like to take the job of release manager. Yves Jaradin, here at UCL, would be assistant, as Kevin did working with Kostja.

Reactions?, ideas? suggestions?

cheers
Boriss


_________________________________________________________________________________
mozart-hackers mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-hackers

Reply via email to