On Wed, 7 Feb 2018 11:52:48 -0700 Tom Russo <ru...@bogodyn.org> wrote: > To test out the release mechanism on github, I've gone ahead and > created a "new" Xastir 2.0.8 release branch (branched from the > xastir208 tag that was used for the SourceForge stable release), > bootstrapped it, pushed it to github, tagged it with > "Xastir-Release-2.0.8", and told GitHub to call it a release.
Going along with a release, It is worth thinking about having the release source code archived in Zenodo (and given a DOI - for anyone who might be interested in citing the xastir codebase in a publication). https://guides.github.com/activities/citable-code/ -Paul -- Paul J. Morris Biodiversity Informatics Manager Museum of Comparative Zoölogy, Harvard University m...@morris.net AA3SD PGP public key available _______________________________________________ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
