{"action":"created","issue":{"url":"https://api.github.com/repos/datacats/datacats/issues/189","labels_url":"https://api.github.com/repos/datacats/datacats/issues/189/labels{/name}","comments_url":"https://api.github.com/repos/datacats/datacats/issues/189/comments","events_url":"https://api.github.com/repos/datacats/datacats/issues/189/events","html_url":"https://github.com/datacats/datacats/issues/189","id":88425544,"number":189,"title":"Versioning in datacats","user":{"login":"JackMc","id":746519,"avatar_url":"https://avatars.githubusercontent.com/u/746519?v=3","gravatar_id":"","url":"https://api.github.com/users/JackMc","html_url":"https://github.com/JackMc","followers_url":"https://api.github.com/users/JackMc/followers","following_url":"https://api.github.com/users/JackMc/following{/other_user}","gists_url":"https://api.github.com/users/JackMc/gists{/gist_id}","starred_url":"https://api.github.com/users/JackMc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JackMc/subscriptions","organizations_url":"https://api.github.com/users/JackMc/orgs","repos_url":"https://api.github.com/users/JackMc/repos","events_url":"https://api.github.com/users/JackMc/events{/privacy}","received_events_url":"https://api.github.com/users/JackMc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-15T13:21:23Z","updated_at":"2015-06-15T13:52:48Z","closed_at":null,"body":"To keep pace with the fast-paced development of the project currently and also maintain backwards compatibility, it is important for us to develop some kind of versioning schema.\r\n\r\nSo, here is my proposal for versioning (both datadirs and containers):\r\n* Each time a breaking change occurs with the format of the datadir, we should increment the format version number (in migrate.py), and add a migration from the last version to the newest version. In an ideal world the algorithm would be a little smarter and know how to migrate from say version 1 to version 3 by migrating 1->2, then 2->3. \r\n* Each time that we add something to one of the containers, the version on the containers must also be incremented. This deliberately excludes the scripts which datacats mounts into the containers. Should we provide migrations (i.e. if the user doesn't have postgis, silently install it?). \r\n\r\nSo the current versioning should probably look something like this:\r\n\r\nDatadir:\r\n* Version 1 - Initial version pre-1.0.0. Only a single site allowed.\r\n* Version 2 - New version post-1.0.0. Multiple sites allowed.\r\n\r\nImage versions:\r\n* Version 1 - Anything prior to the introduction of this versioning scheme\r\n* Version 2 - PostGIS introduced\r\n* Version 3 - Datapusher introduced"},"comment":{"url":"https://api.github.com/repos/datacats/datacats/issues/comments/112078891","html_url":"https://github.com/datacats/datacats/issues/189#issuecomment-112078891","issue_url":"https://api.github.com/repos/datacats/datacats/issues/189","id":112078891,"user":{"login":"dborzov","id":816895,"avatar_url":"https://avatars.githubusercontent.com/u/816895?v=3","gravatar_id":"","url":"https://api.github.com/users/dborzov","html_url":"https://github.com/dborzov","followers_url":"https://api.github.com/users/dborzov/followers","following_url":"https://api.github.com/users/dborzov/following{/other_user}","gists_url":"https://api.github.com/users/dborzov/gists{/gist_id}","starred_url":"https://api.github.com/users/dborzov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dborzov/subscriptions","organizations_url":"https://api.github.com/users/dborzov/orgs","repos_url":"https://api.github.com/users/dborzov/repos","events_url":"https://api.github.com/users/dborzov/events{/privacy}","received_events_url":"https://api.github.com/users/dborzov/received_events","type":"User","site_admin":false},"created_at":"2015-06-15T13:52:48Z","updated_at":"2015-06-15T13:52:48Z","body":":+1: agreed, versioning is sorely needed."}}