Scala Meeting report, 2010-03-30

We are currently publishing a summary of each of the weekly meetings of the
Scala Core Team.

This information is made available as a service to the community. It is by
necessity rather brief and gives only a rough approximation of the main
points of discussions explored during each meeting; it should not be taken
as a source of reliable information, nor as a record of concrete or firm
decisions, nor as anything other than a record of a simple discussion.

The summary that follows is primarily intended for Scala contributors and
maintainers. If you are not a contributor to the Scala system, the
information below is unlikely to be very useful to you, and you might lack
some of the necessary background to make sense of all the discussion items.

We do not have enough people on the team to be able to write a more
complete record, and we might also not have the resources to discuss every
point in detail afterwards. Nevertheless, we hope that this record, cursory
as it is, is better than nothing.

------------------------------------------------------------------------------

Scala Meeting 2010-03-30

People attending the meeting: Lukas, Martin, Donna, Phil, Alex, Hubert,
Ingo, Tiark, Toni, Gilles, Philipp.

* Current work
- work on continuations
- new pickle format
- Scaladoc cleanups
- bug fixing

* 2.8 status
- Scaladoc
- specialization of the library: it's been announced and it is almost done
- classpath changes; the new changes resolve issues with projects which
use Java and Scala tools simultaneously
- specification: needs to be done for the 2.8 final, not the RC

Because of specialization, we will have to wait until after next Tuesday
for the release. The Lift project will need 6 weeks after the RC.

* Size issue of Scaladoc
Large size of Scaladoc. The fundamental problem is that all the members are
printed for every class now. Problem is also that the installer will grow
and become slower because of copying many files.

One way to do it is to have Scaladoc generated on demand, instead of it
being statically generated it's also possible to include the actual members
in html, generate elements with JavaScript. 25% could be shaved off by not
having short and longer comments on separate places having a server in the
background to serve pages is one solution, but could be cumbersome

* Complaints about Pickle format
Some people complained that Pickle format should be human-readable. On the
other hand, it is possible to read them by piping the output through a
filter. It does not appear to be a significant issue.

* Current build status
Stability issues in current trunk - wait until the nightly stabilizes,
which should be soon.