[Openmcl-devel] ccl 1.11 release and GitHub

Ron Garret ron at flownet.com
Sun Feb 12 15:11:42 PST 2017

On Feb 12, 2017, at 2:43 PM, Chris Hanson <cmhanson at eschatologist.net> wrote:

> On Feb 12, 2017, at 1:33 PM, R. Matthew Emerson <rme at acm.org> wrote:
>> Since 1.12 won't be ready for some time, I am considering making a 1.11.1 release, and hosting that on GitHub.  The 1.11.1 release would be binary-compatible with 1.11, but it would contain a few changes (like the version stuff mentioned above) that wouldn't normally go in a release branch.  What do you think?
> That all sounds reasonable to me, especially given the switch to GitHub: It would result in a release-quality CCL built and buildable by others from a tag in the (new) primary source repository.

If that’s your goal (and it’s a good goal) there is an easier way to achieve it: simply tag the old releases.

I don’t think it’s wise to expend scarce resources to generate a release simply for the sake of generating a release.


More information about the Openmcl-devel mailing list