Re: Bug#242449: fixed? not quite yet

[Zak Greant <zak@mysql.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Aug 11, 2004, at 1:52, Dave O wrote:
> On Wed, 11 Aug 2004, Christian Hammers wrote:
>
> > On 2004-08-10 Dave O wrote:
> > > This isn't quite ready to be considered "fixed" since the new 
> > > version > of the license exception will apply to future releases of 
> > > MySQL > including 4.0.21.  However, if 4.0.21 is not out by the 
> > > freeze, this
> > > is still a DFSG concern for sarge.  If only for the purpose of 
> > > raising
> > > awareness of this, this bug should probably remain open as a policy
> > > violation...
> >
> > As far as I understood Zak Greant (MySQL)'s intention and the text of 
> > the online doku, there is no point in which states that the currently 
> > displayed license at http://www.mysql.com/ does not apply to the 
> > currently downloadable versions, which includes 4.0.20.
> > A counterexample is that they do make a note that for the 3.23 server 
> > version which is to be used under a different license.
>
> From his email:
>
> "The exception will apply to future MySQL versions 4.0.21, 4.1.4 and
> 5.0.2."
>
> Is this not the way it ended up?

The text of the exception will be in source code of these releases. We 
would add it to the current releases, but we shouldn't modify a current 
release and we don't want to make a full new release, etc for the 
licensing when a full release is close anyway.

We could put a note online stating that v4.0.20 is covered (but this 
doesn't really help people who decide to reuse chunks of MySQL code 
under the FLOSS exception terms).

We are more than happy to have the Debian maintainers backpatch the 
exception into 4.0.20 if they like. Just make sure to flag the release 
so that people know that it is not stock 4.0.20.

Cheers!
- --zak
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (Darwin)

iD8DBQFBGdavctLVEMjfMB0RAulcAKDwsMWqmE/R0wWmfV0VsuvbVtdx4QCfSw7a
v9oJjcAeA2eLbh2f1e9P/3Q=
=Z9Ov
-----END PGP SIGNATURE-----