cms-dev/cms branching and versioning model

[jossemarGT]

Greetings CMS dev community.

I have been hacking around CMS for a few months, with the sole goal of adding a self service experience to the platform *without* altering the core. In other words, I'm creating an external set of web applications that manage the CMS data directly from its schema, letting the platform work as expected, and at least for user registration it worked :).

Unfortunately, I have stumbled with a "meta" problem, which at least for me, is not quite clear the branching and versioning model that CMS platform is following right now. For example, I started using a master branch revision (f7ebce619b886cbdd4620123889860a908f4ca65) dating form Jan 27th 2018, but the stable release v1.3.1 that came after it does not have some of the goodies that I was used to see (Ex.: C# and Rust language support). I could guess that the 1.3.x release branch was created while ago (before Jan 2018) and  the mentioned release came from it, but I would like to confirm with any of the current maintainers.

Thanks for the help :)

[Luca Wehrstedt]

Hello and welcome!

Here is how our versioning model works. The master branch is our development branch, which means that it is where all new commits are pushed, both for new features and bug fixes. Once in a while we "fork" a version branch out of the development branch, for example the v1.3 branch [1]. This means that we "freeze" the master branch at a certain state (in case of v1.3, this state was the one of March 12, 2017 [2]) and try to release that state as a stable version. That is, the version branch will not receive any of the new features that are added to the master branch, but it will receive the relevant bugfixes (the relevant ones that still apply to it). Once a version branch is stable enough we release the first micro version (e.g., v1.3.0). Once enough new bugfixes accumulate on that branch to warrant a new release we do so (which is why we released v1.3.1).

Hope this answers your question! Please follow up if it doesn't.

PS: While we do our best to keep the master branch as stable as possible, we advise against using it for production use and recommend instead to stick to the latest stable version.

[1] https://github.com/cms-dev/cms/tree/v1.3

[2] https://github.com/cms-dev/cms/commit/4a74741c3ac101e0c376136a196b90030c9a4c9a

--
You received this message because you are subscribed to the Google Groups "Contest Management System (discussion)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to contestms-disc...@googlegroups.com.
To post to this group, send email to contestm...@googlegroups.com.
Visit this group at https://groups.google.com/group/contestms-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/contestms-discuss/1917dd57-d53e-4c08-8656-328c9e1c2663%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jossemar Cordero]

That makes absolute sense, now it makes me wonder if the dev community have come around the idea of having nightly/edge releases alongside the LTS ones? just like Jenkins CI does[0]. Anyway, I am going to bite bullet and continue with the upstream (some master's revision).

Thanks for the explanation Luca!

[0] https://wiki.jenkins.io/display/JENKINS/Release+Process

[cristian...@unitn.it]

Hi,

Il giorno domenica 24 giugno 2018 07:35:34 UTC+2, jossemarGT ha scritto:

I have been hacking around CMS for a few months, with the sole goal of adding a self service experience to the platform *without* altering the core. In other words, I'm creating an external set of web applications that manage the CMS data directly from its schema, letting the platform work as expected, and at least for user registration it worked :).

This  is a very nice idea! In fact I used the same "plug-in" or "add-on" approach when writing this small web app for registration:

https://github.com/CristianCantoro/flask-registration

Do you plan to share your code?

Cristian

[jossemarGT]

Hi

Do you plan to share your code?

I'm sorry for let you hanging for too long, but the answer is yes, unfortunately the languages for each microservice will widely vary, today we have:

• User registration, login and profile https://github.com/joelgtsantos/cms-users-admin [Java] (wrote by a peer)
• Contest and Task entities as Restful API https://github.com/jossemarGT/cms-galatea [Java]
• Scoring, entry and test submission entities as Restful API (not published yet)  cms-sao [Go]

Hopefully we will be able to publish our distributed design as part of our (college) research on the internet if you are curious about it.

Regards,