Skip to Content.
Sympa Menu

comanage-users - [comanage-users] COmanage Release Cadence

Subject: COmanage Users List

List archive

[comanage-users] COmanage Release Cadence

Chronological Thread 
  • From: Benn Oshrin <>
  • To: "" <>
  • Subject: [comanage-users] COmanage Release Cadence
  • Date: Tue, 13 Nov 2018 11:35:57 -0500
  • Ironport-phdr: 9a23:0cd71RVuYWzPJ4xBEYr60Z85C+nV8LGtZVwlr6E/grcLSJyIuqrYZRWDvKdThVPEFb/W9+hDw7KP9fy4BipYud6oizMrSNR0TRgLiMEbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpTEdFQ/iOgVrO+/7BpDdj9it1+C15pbffxhEiCCybL9uLhi6txndutULioZ+N6g9zQfErGFVcOpM32NoIlyTnxf45siu+ZNo7jpdtfE8+cNeSKv2Z6s3Q6BWAzQgKGA1+dbktQLfQguV53sTSXsZnxxVCAXY9h76X5Pxsizntuph3SSRIMP7QawoVTmk8qxmTgLjhiUaOD4j6GzZitF+grxYrhyvqRNwzJLbbo6OOfpifK7QZ88WSXZPU8tTUSFKH4Oyb5EID+oEJetVspfyp10IrRCjHAesH+PvyiVJhn/wwKY31P8uHh/A3AwmGNIDq3XUrNPpNKgMS+C1yrfHzSndY/9Mxzjy9ZXIfwknrPqRXrxwadLcxVchGg/fjVidp5bpMy2J2ukJqWSW7eRtWfqshmI9pAx8oyKjy8Ush4XTm44Z1FbJ/jhjzokvP923Ukt7bMakEJROsyGaMJN7QswlQ2FspSk11LsGtYSgcygL0pQo2x7fZ+adc4eW5hLsTuaQLS19hH1/ebK/gwq98Ui6xe36UMm7zlJKrjFfntnKqH8NywTf6smBSvRj4keswSiD2g7J5uxHL004j7TXJ4Ilz7IqlJcev1zPHirsl0X3iK+WeF8k+u+t6+n/ebrpuJmcN4lzigzlM6QunNC/DvoiMggIQWeb5fqw2Kf98kLkXbVGluc2nbXBsJDGOcQboba0DBNS0oYm8Rm/CS2p0NsGknUeMVJFYwyIj5LyO1zVJPD4DOy/g0i3kDt13fzGP7vhAonTIXjZlrfuY6p951BGxAUt0N9f+opYCrQGIP3uRED8rMfYDholMwys2+rnCMty1ocZWW+XHqKZLKfSvkWO5uIzIumDfpUZuDL6K/c5/fHuiWc1mV4bfaa3wZsacHO1Eu5pLkiYe3bhgNcMHX0XsgYgVODqkkONUSJOZ3aoWaIw/yk7B5i6DYfDXo2gnaKO3CG9HpZLf25GEVCMEW3pd4WCRvwBbzmdLdFnkjwCUrisUI4h1ReytADk0bpnKPTb+jEGuZ75ytd6+vDTmAgq+TxxFcud0mWNT29unmMPQj87xLtwrlJ7yleF1qh1mP1YFdpP5/xXSAc6M4DTz/BkB9zoRA3OY8qJRE6gQtW8HT4xVs4xw8MJY0tlB9qiiRXD0DCsA7APmLyEGoU48r/H33fvPcZ90G3L1Kgnj1k6XMRPL2umibBj9wTNHYLGjViWl7useK8BwiPN8HqDzXGSvE5GSg5+TKTFXHEBaUbOsdiqrn/FGvWlDrEuNAJOxIufMaZQcfXoi0lLXvHuJI6Ybm6s0S/kDhGNz7WFY4evZn4Qxj71CU4YnhoV8GrccwUyG3HyjXjZCWlEGFTpK2T38fN/rjvvREIyyQaibkt92qCz9wJPw/GQVqVAjfo/pC49pmAsTx6G1NXMBo/Yqg==

Hi all,

One of the issues we've been thinking about within the project is our release cadence. Our last feature release was 10 months ago (v3.1.0, back in February, with two release candidates in January), and before that v2.0.0 was released in April 2017. (v3.0.0 was released in September 2017, but was mostly a UI refresh.) So basically we have a slow release cycle with each release having a bundle of new features.

We could consider changing this process. At the opposite end of the spectrum, we could cut a release for each new feature. Or perhaps as a middle ground, we could schedule (say) quarterly releases, and then whatever is ready (which could be nothing) gets included in that release. Regardless, we would continue with bug fix releases as needed for issues affecting production instances, or for security issues.

If we were to switch to a faster model, we'd release v3.2.0 ASAP (in spite of the large number of issues flagged for this release), most likely before the end of November. We'd then begin the accelerated cycle after that.

So some questions for the community...

- Has the slow release cycle been problematic for you as a deployer?
-- If not, why not? (eg: You are comfortable running from develop; you are in no rush to get new features; etc.)

- If you would prefer a faster release cycle, would you be more inclined to update to each release, or just to those with features or fixes you were interested in?

Feel free to add any further comments on this topic you might have, and to reply to me directly if you'd prefer not to reply on list.



Archive powered by MHonArc 2.6.19.

Top of Page