On 11 Jun 2015, at 09:25, Thomas Gazagnaire <[email protected]> wrote: > > I've tried to "clean-up" some of my release scripts, that I published on > GitHub. It is a mix between opam-publish and my own conventions, so I'm not > sure it very useful to someone else than me. Feel free to clone and to adapt > to your need. Feel free to rewrite the shell scripts using a proper language > and submit a pull-request :-) > > With these scripts, using `opam release` at the root of my project will: > 1/ tag the project by greping the version number in _oasis or in opam; > 2/ push the tag to upstream repository on GitHub; and > 3/ call opam-publish with the new archive. > > My convention are: > - to name the tag as the raw version, not `vVERSION` (ie. not adding a `v` > prefix) > - to have an `upstream` git remote pointing at the upstream repository > - to have `opam-publish` installed in a switch called `publish`
Does this also do a GitHub release, or just create the tag upstream? -anil _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
