Add release tags to plugin subrepos

[infotexture]

If plugin subrepos had release tags, users could download pre-packaged zip files or install plugins using the dita command in OT 2.0 directly from GitHub.

See https://help.github.com/articles/about-releases.

(example to follow)

[infotexture]

See https://github.com/dita-community/org.dita-community.pdf-page-break/releases/tag/v1.0.0.

[drmacro]

The benefit is clear. The main challenge is automating the release creation--that must be possible using the GitHub API, yes?

[infotexture]

Basically, it's as simple as tagging a commit & pushing the tag.

GitHub adds an entry on the Releases tab for all tags. These automatically provide download links to .zip & tar.gz archives. You can add release notes for convenience, but it's not necessary.

[drmacro]

By "automation" I mean automating the release creation so that somebody doesn't have to manually create the releases for each plugin through the GitHub web UI. E.g., the general release process for multi-plugin projects should include creating a release for each plugin so that they are all in sync and consistently released. I would be surprised if this is not possible to do via an Ant script or a bash script, just a matter of figuring it out.

[drmacro]

Better late than never: My git fu has improved dramatically since this issue was first submitted. I'll automate the release tagging.