Release of New Fog Version


  • hi guys, any plan to release a new version of the fog project, making all the dev work into prod? thanks

  • Moderator

    @abulhol Beside the actual release it also needs people to test development versions and report issues. There is no way all the testing can be done by the devs - like setups with storage nodes, plugins and all that. This is even more important with the current phase of moving to PHP 8.

    PHP 8 support was added in months ago but we still get issue reports lately, see 1, 2.

    I am not sure when the point is reached where most bugs are found and fixed. I keep asking people to use dev-branch so we find these bugs faster but as you can see from the issues mentioned above that reports still arrive even after months.

    If the community wants a release “now” we can do that. But I am fairly sure it won’t be as stable as you hope.


  • @zfeng +1 We are now moving our servers to Ubuntu 22.04 and rather want to install a somewhat stable release than a working-branch version that may change from day to day.

  • Moderator

    @wayne-workman said in Release of New Fog Version:

    After you get all the steps documented @Sebastian-Roth I can try to create a Jenkins pipeline file that does all this stuff, and add it to the right repo via pull request. Try to automate some of this stuff. We can probably have a Jenkins server in our aws account where we can do builds.

    I have thought about this for a bit. Not sure if it’s worth the effort. Most of these steps need to be done manually as decisions are involved (e.g. add new feature X in kernel or not). A fair amount of building and releasing new kernels and FOS inits on github is automated via buildkite already. I will describe that in the docs as well.

    So it’s really more about getting people involved who know how it all works I think.


  • After you get all the steps documented @Sebastian-Roth I can try to create a Jenkins pipeline file that does all this stuff, and add it to the right repo via pull request. Try to automate some of this stuff. We can probably have a Jenkins server in our aws account where we can do builds.


  • @sebastian-roth good to know. thanks

  • Moderator

    @zfeng Definitely a good point - made by several people in the last couple of months. Though there is hardly anyone around who knows the ins and outs of doing a FOG release. I did not have the time and obviously no one else had.

    There is hardly any knowledge about FOG releases in the community and therefore it lies in the hand of certain people - who might not have the time or drop out without notice. I remember @Wayne-Workman saying that documentation in FOG releases is needed and he’s totally right. So I started to document things: https://docs.fogproject.org/en/latest/development/fog_release.html (will be updated as we go)

    I may encourage anyone to get involved and use this topic to discuss things!!

289
Online

9.9k
Users

16.2k
Topics

149.0k
Posts