Release for v6.3 has begun

[Ryan Culpepper]

The release process for v6.3 has begun: the `release' branch was
created for any work that is left and is now bumped to v6.2.901.900. You
can go on using the `master' branch as usual, it is now bumped to
v6.3.0.1 (to avoid having two different trees with the same version).

If you have any bug-fixes and changes that need to go in the release
then make sure to specify that in the commit message or mail me the
commit SHA1s. You can `git checkout release' to try it out directly if
needed -- but do not try to push commits on it (the server will forbid
it).

Please make sure that code that you're responsible for is as stable
as possible, and let me know if there is any new work that should
not be included in this release.

>> NOW IS THE TIME TO FIX BUGS THAT YOU KNOW ABOUT <<<

The time between the `release' branch creation and the actual
release is for fixing new errors that prevent proper functioning of
major components and that show up during the preparation for a
release. You can also finalize piece of work that is not yet
complete, but please avoid merging new features.

Note that nightly builds will go on as usual (starting from
v6.3.0.1 and going up as usual), and pre-release builds will be
available shortly at

http://pre-release.racket-lang.org/

Please tell me if you think that this release is significant enough
that it should be announced on the users list for wider testing.

[Alex Knauth]

Would it make sense to revert the commit that changed (set-implements? (mutable-set) 'set-add) and (set-implements? (set) 'set-add!) to both return true? In previous version they returned false, and it does seem like returning false is a good idea.

I think it was this commit here:

https://github.com/racket/racket/commit/606a94621253391536e9c89c573dc70fd28efbe6

--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+...@googlegroups.com.
To post to this group, send email to racke...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/56181A6F.9080405%40ccs.neu.edu.
For more options, visit https://groups.google.com/d/optout.

[Asumu Takikawa]

Hi all,

On 2015-10-09 15:50:07 -0400, Ryan Culpepper wrote:
> If you have any bug-fixes and changes that need to go in the release
> then make sure to specify that in the commit message or mail me the
> commit SHA1s. You can `git checkout release' to try it out directly if
> needed -- but do not try to push commits on it (the server will forbid
> it).

I don't have a bug fix for this, but I do think the current problems in the
macro debugger (due to the new expander) are worth blocking the release on.

Currently if you use the macro debugger on these programs it will error:

#lang racket
(class object% (super-new))

or

#lang typed/racket

These problems are tracked as issues 5 and 7 on GH

https://github.com/racket/macro-debugger/issues/5
https://github.com/racket/macro-debugger/issues/7

The reason I think these are worth blocking over is that the macro debugger is
a widely used tool and it's easy to stumble on these broken cases. Any
thoughts?

Cheers,
Asumu