We continued with work in team strategy, helping team members to learn / share the work strategy and approach towards a problem. In last 5-6 days we have resolved 25 issues, created 29 and closed 43 issues which is the indication of better QA towards v2.0.
v2.0 has significant schema changes, and hence a simple sql script could no longer serve as our primary upgrade mechanism. We are introducing a new upgrade system in 2.0 which will run in a couple of steps and upgrade the user's database. It has been an interesting exercise to come up with the upgrade script. Here are a few things we learned as we went through the process.
The results of the first day of our Mumbai meetup were quite impressive. We successfully knocked out around 7-8 issues.
Day two started out with high energy levels. We divided the day into three sessions.
In the morning session, Piotr introduced us to the world of internationalization and some of the do-s and don’t-s about using ts() (the translation function). He also gave us a demo on using the Pootle-based translation server.
Most of the CiviCRM team is currently in Mumbai, India where we are having our first world wide developer meeting. :) We are missing Dave Greenberg who unfortunately had to cut short his trip to India. :( But he is present via the wiki, blog and issue queue prodding us along. :)
For several versions now, CiviCRM ships with version checking mechanism that pings our server from time to time (every time you visit the Administer CiviCRM page of your install, but not more often than once a day) and lets you know if there’s a new major stable version available for download. (This mechanism can be turned off by visiting Administer CiviCRM → Global Settings → Miscellaneous Settings.)
We have delayed CiviCRM v2.0 code freeze (and hence alpha/beta/final) dates. This was primarily because of other commitments, specifically developer boot camps and our combined travel schedules. We expect to have the code freeze in the second week of January (01/07/2008) to be followed by alpha, beta and final releases spaced out over the next six weeks.