forked from EOxServer/eoxserver
-
Notifications
You must be signed in to change notification settings - Fork 0
DeveloperGuidlines
Stephan Meissl edited this page Jul 3, 2013
·
1 revision
This is a non-exhaustive growing collection of general developer guidelines.
We're using Jenkins for Continuous Integration of all release branches and master. Please make sure you don't break the builds.
Any changes, extensions, additions, etc. that need consideration when upgrading EOxServer versions shall be added to #134, particularly database schema changes (cf. #168).
- All changes committed to git shall be supplemented with an informative description of the changes at commit time.
- In addition, any commits which include a change in the DB schema, and therefore requiring a DB migration after an upgrade, shall clearly indicate such a change.
- The phrase "DB-CHANGED-" shall be placed at the beginning of the description.
- Schema and data migration management is handled using South see data migrations documentation
- This will allow (if reviewed beforehand) to prepare for the needed DB migration (DB dump, etc.) before upgrading from the repository.