[Mono-dev] Building release (Mono-devel-list Digest, Vol 121, Issue 11)

Alex J Lennon ajlennon at dynamicdevices.co.uk
Sat May 16 17:33:04 UTC 2015

On 16/05/2015 17:01, Jo Shields wrote:
> We use a 4-part versioning scheme internally, for our Mac builds - our
> build system increments every time a new commit happens on a branch
> after configure.ac has been bumped to a new 3-part version. Some (but
> not all) of our builds go to our customers' Alpha channel after being
> QA'd, then some of those are promoted to beta, then later to stable.
> I'm working on automating our procedures so that *every* product
> release gets a corresponding Open Source release, and and
> are the first examples of this - alpha channel releases that
> have happened since  started work on this procedure. As time goes by,
> I'll make sure the website gets automatically updated too, so it'll be
> clear which 4-part versions should be considered stable

Great. Thanks for explaining Jo :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150516/39dd7bd9/attachment.html>

More information about the Mono-devel-list mailing list