Hi everyone, Easybuild releases typically contain new software support (newer versions of previously supported software, newly supported software) and improvements to the frame work. I think separating those and having more frequent releases for supported software could be of large benefit to the user community. Issues encountered while developing new features would not hold up the release of straight forward and unproblematic package releases and updates.
I have briefly discussed this with Kenneth and he thinks it would be a good idea, but would need some help regarding the “sub-releases”. Ideally two volunteers with suitable skill set (git, python, EasyBuild). From Kenneth’s input: "The major issue that needs to be solved is that the whole process should be scripted/automated as much as possible, to minimize overhead. * 'stable' branch is forked into a '<version>' branch * all new/changed easyconfigs in '<version>' branch (compared to 'master') are tested using framework 'master' + easyblocks <version> * this should be fully scripted (I already have part of this in place) * while waiting for test result: compose release notes (basically a "grep merge" in "git log" output + some massaging) * if all tests pass: run script that creates release from framework master + <version> branch for easyblocks/easyconfigs * i.e. publish it on PyPI, tag releases in GitHub * announce release ... Ideally, someone else than me should tackle this, after I help that person out with setting up the workflow (probably by setting up the script in an 'eb-release' repository on GitHub). The first 'subrelease' like this could be done after EasyBuild v3.0 (i.e. one more release after 3.0 this year).” Best wishes Joachim
