Before jetting off the Colombo this weekend for the first annual Sahana software for disaster management conference, I want to provide an update on the input and ideas collected for the Sahana 1.0 release. I am personally a bit behind schedule myself on managing this, and for that I apologize.

However, I would like as much as possible to try to keep to the schedule I posted on the wiki which allows through the end of April to make a technical and strategic plan for what’s going into the release and what’s not. So, I would welcome any additional suggestions and thoughts as to what should be included in the 1.0 release. Please continue to send them in to the sahana-user or sahana-maindev mailing lists. I have a feeling some other ideas and discussions on this may take place in Colombo next week, so I will keep the list open through next week. This is definitely on my personal agenda to discuss at the BarCamp.

Anyway, here’s the list of ideas – most are new and some are adjustments to others already noted in some form on the wiki already:

- Merging of bug-fixes and enhancements from China / Sichuan deployment (for 1.0)

- Staff deployment and other enhancements from NYC deployment (for 1.1+)

- Make an RC branch off of trunk past 0.6.2.2 branch to capture many enhancements made for the 1.0 release – let release team work on it to capture bug fixes for trunk from other branches.

- Review list of bug fixes required for proposed 1.0 branch and trunk, and update tracker accordingly, such that experimental development can continue towards features planned for 1.1+ releases (currently noted as 0.7 and 0.8 on the wiki – plus GSOC 2009 projects).

- Windows and other supported OS installers to include as much auto configuration as possible and easy to follow prompts where user input is needed to set-up Sahana

- Document the installation package creation process on the wiki such that future release teams can follow it.

- Complete third party library review

- include the LGPL license text in the base directory of the package

I think that was it. Let me know if you think I missed anything; and please do feel free to send additional suggestions through next week.