Pending Merge Requests

[Robert Goldman]

I would very much like to get 3.2.0 released, but I am starting to feel
like we have a Zeno process here.  Merge requests are appearing as fast
as they are merged.

Currently pending for 3.2.0:

!59
Link objects only

!60
Fix bad-system-name for "logical" .asd pathnames

!61
Remove *load-system-operation*

Which, if any, of these must be in our 3.2.0 release candidate?  I would
like to freeze a release candidate, marking it as version 3.2.0, for
people to play with for at least a week, before we push it into the world.

I'd very much like to do this this week, since the holidays are coming
up when people's minds will turn to other things than testing new ASDF
versions.

I can pretty much guarantee that if the answer to the above is "we need
all three," we are talking a 2017 release, instead of finishing this
year, because of limitations on my available testing cycles in the
remainder of 2016.

Thanks,
r