This repository only has a master branch. Currently, analytics master is not building with canvas-lms stable (see #2).
The convention for the canvas-lms repo is that master is bleeding edge, while stable is… stable. If analytics is going to remain in a separate repository, this convention should be followed here as well and a stable branch should be created. The current analytics stable branch should always work with the current canvas-lms stable branch.
Tags would be nice to have (e.g. the 2015-01-31 analytics tag should always work with the 2015-01-31 canvas-lms tags), as long as tags in this repo don't have the same problems as tags in the canvas-lms repo (they don't point at the treesame commits, so you can't actually merge them into a fork without incurring massive git conflicts in files that have never been changed in the fork).
This repository only has a master branch. Currently, analytics master is not building with canvas-lms stable (see #2).
The convention for the canvas-lms repo is that master is bleeding edge, while stable is… stable. If analytics is going to remain in a separate repository, this convention should be followed here as well and a stable branch should be created. The current analytics stable branch should always work with the current canvas-lms stable branch.
Tags would be nice to have (e.g. the 2015-01-31 analytics tag should always work with the 2015-01-31 canvas-lms tags), as long as tags in this repo don't have the same problems as tags in the canvas-lms repo (they don't point at the treesame commits, so you can't actually merge them into a fork without incurring massive git conflicts in files that have never been changed in the fork).