In the thread "JIRA Questions" that saw some posts on this list recently, we were discussing the JIRA checkbox used to indicate schema changes. During this discussion, Greg proposed how to deal with this box and what the policy was around code changes that trigger database schema changes.
Therefore I take the freedom to propose what Greg outlined in his last response, adding 3) since I think that everything else will just overload the release manager with work. Writing code should still be fun. However, making sure that adopters are able to keep up with our releases should be a priority for all of us. 1) The checkbox is used to notify the release manager that there has been a change to the schema. 2) The developer is responsible for updating the schema and ensuring everything still works before commit, but this box makes sure that the DB changes are double checked. As we experienced in the past, sometimes a change will work for the developer, but not for anyone else. 3) The developer is responsible for providing update scripts for the database between the version in trunk and the last stable release. Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
