Scala Meeting report, 2010-01-27

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.

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

Report from the Scala Core Team meeting, 2010-01-27:

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

* Current work

- Improved performance of parallel data structures
- Work restarted on unique reference plugin
- Partest can test build manager
- Scala bytecode can be profiled with YouKit

* 2.8.0 Beta
- The 2.8 Beta release is ready and will be made public within hours.
- Miles gave us an Eclipse plugin that will be provided alongside the beta.
- Migration guide:
- Involve the community.
- Put up a wiki where people can contribute; as a starting point: the
email messages sent on the lists.
- We want users of the beta to be contribute their experiences.
- Need to write documentation for manifests.

* Style Guide
- We will look at it, and discuss it again next week.

* Talks at Scala Days
- We would like to invite more submissions for talk proposals.

Google Summer of Code
- We will check what needs to be done.