3 May 2010 17:48
Scala Meeting report, 2010-04-27
Antonio Cunei <antonio.cunei@...>
2010-05-03 15:48:03 GMT
2010-05-03 15:48:03 GMT
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-04-27 People attending the meeting: Philipp, Tiark, Toni, Iulian, Ingo, Hubert, Martin, Miguel, Alex, Gilles, Lukas, Adriaan. * Current work - fixed deadlock when terminating linked actors - fixes to specialised (scalaz and scalatest work now) - working on ctors bugfix where specialised - fixed name-clashes due to erasure - work on .NET cross-compiler, updating GenMSIL - refactoring parallel collections for trunk - work on reflection for Scala - fixed erasure bug, fixed issues with named arguments - general bugfixing * 2.8 RC2 - Most of the bugs that concern us are fixed. - There is still one bug involving raw types from David that we still don't have info on. Probably #3349 - once we fix that, we can announce the of release RC2. Martin and Adriaan will take a look. If it's fixed today, RC2 is on Friday. - We can point to a certain nightly and say that it will become an RC in 3-4 days. In general, we will give people 3 days notice before we release an RC1, so that they can test their tools and libraries. Within these 3 days we will only fix critical issues, not introduce new features nor fix minor bugs. - We discussed having RCs for RCs, which we ship to 3rd party tools maintainers, but we won't do this, as it could introduce misunderstandings. We will simply firmly choose a nightly that should be used for tests of 3rd party tools before an RC comes out. * GSoC Application process is finished - we have 7 students working on the following projects: - scalable remote actors, NIO - Lift and sbt template engine - development in Emacs - ENSIME - additional features to Scala Eclipse IDE - hardware accelerated 2d graphics - use of shader DSL - adding Linq awareness - collaborative wiki for ScalaDoc We will write about our progress and results, and create a story for the website. Officially coding starts May 24, midterm evaluation is July 12th, the summer of code finishes in 20th August.