github release procedure
alex
info at alexanderbothe.com
Thu Jan 3 12:26:56 PST 2013
Couldn't we just make an auto-publishing cron-job service or so
which periodically (once a day or even just after a push/merge)
compiles dmd and everything, packs it and makes this archive
downloadable then?
Of course this literally rolling release should be marked as
unstable/nightly build. Anyway, if a halfway stable state has
been reached or if the community thinks that it's enough for a
version bump,
the latest build is simply tagged and marked as latest stable
version.
How easy is that?
More information about the Digitalmars-d
mailing list