dbs to update the release process doc with a mention of the version_upgrade directory
STATUS: Updated release checklist with some specific mentions of the version_upgrade directory for creation & testing, however this is very high level and doesn't specify:
who actually will create the script (I lamely said evergreen-dev which leaves it pretty wide open)
naming conventions for the point-to-point upgrade scripts to avoid any ambiguity
expectations about what data should be upgraded and what should not be touched (for example, permissions and permission groups)
how to notify users about any outstanding manual steps that may need to be taken to complete the database schema upgrade
bshum and others to continue thread discussion about developer meeting times.
STATUS: Done by kmlussier, see mailing list. Thanks for participating in the doodle poll!
dbs to talk about GSOC stuff next time (or send thoughts to -dev mailing list)
Does the Doodle poll indicate that Mondays at this timeslot seems to work best for now? Should we consider other ways of managing/scheduling future developer meetings?