MEP for release 1.3.2

[Christian Schulte]

Fine by me. However what are the fixes. Is there a changelog?

Christian

--
Christian Schulte, http://www.imit.kth.se/~schulte/ 

-----Original Message-----
From: hackers-bounces at mozart-oz.org [mailto:hackers-bounces at mozart-oz.org]
On Behalf Of Boriss Mejias
Sent: Wednesday, February 15, 2006 12:21 PM
To: hackers at mozart-oz.org
Subject: MEP for release 1.3.2


Dear hackers.

Following the regular procedure, we submitted a MEP to mep at mozart-oz.org 
in order to carry on with the release. Unfortunately, MEP editor has 
told us that there are some problems with the scripts that gives 
identifiers to MEPs and introduce them to the database.

So, he suggested us to post it here to receive comments, and possible 
votes already from board members. The MEP follows

cheers
Boriss

MEP: XXX
Title: Mozart release 1.3.2
Author: Yves Jaradin <yjaradin at info.ucl.ac.be>, Boriss Mejias 
<bmc at info.ucl.ac.be>
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 10-Feb-2006
Post-History:


Abstract
========

The purpose of this MEP is to make a new release of the Mozart platform. The
new release will:

* Fix various bugs in Mozart 1.3.1

* Add support for recent versions of gcc (gcc 3.4 and 4.0)

The release manager will be Boris Mejias, assisted by Yves Jaradin. In order
to make the release we will need:

* Update access to the website for Boris Mejías

* CVS write access for Yves Jaradin


Motivation
==========

Bugs
----

A fair amount of bugs have been fixed since Mozart 1.3.1 or will be fixed
soon. As the fixes are only available through CVS, many users continues to
fight with these bugs. A bug-fix release is therefore recommended for the
typical users.


GCC
---

Mozart 1.3.1 can't be built with gcc newer than 3.3. Mozart 1.3.2 will be
buildable with (at least) all commonly deployed versions of gcc up to gcc
4.0.

Background
==========

Team
----

The release manager for Mozart 1.3.2 is Boriss Mejias, he will be assisted
by Yves Jaradin.  Everyone is invited to participate in producing bug
reports, fixes or patches.


Activities
----------

* Announcement of the coming release to hackers and users, asking for
   bug reports

* Bugs and documentation fixes + testing

* Code freeze

* Documentation fixes

* Release tagging and source release packaging (tgz, srpm)

* Critical binary release packaging (tgz, generic rpm, win32)

* update website for new release

* Release announcement

* More source and/or binary packages


Schedule
--------

No deadlines are fixed yet.


Backwards Compatibility
=======================

Mozart 1.3.2 will be compatible with Mozart 1.3.1.  Native modules compiled
with gcc >3.2 will be compatible with the binary release packages.


Copyright
=========

This document has been placed in the public domain.

____________________________________________________________________________
_____
mozart-hackers mailing list
mozart-hackers at ps.uni-sb.de      
http://www.mozart-oz.org/mailman/listinfo/mozart-hackers