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.
-
@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.
-
@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.
-
@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.
-
@abulhol @zfeng @testers Once again I insist in people shall help test FOG dev-branch before we do a half-cooked release.
I say this because an issue report thankfully got me to spin a minimal setup with storage node and made me stumble upon a major bug we still had in the FOGImageReplicator service on PHP 8 installs. A release with that bug would have stopped every single major setup where replication is essential.
See current dev-branch pretty much as kind of a release candidate right now (speaking of Fall 2022). We need more people to use it in their daily work and full setup to find those bugs.
-
Found and fixed another dozen or so issues related to PHP 8. This time it was not a special setup with storage node or plugins at all. Just using all the different aspects of the iPXE menu.
@testers @moderators Please keep on using dev-branch more intensely on systems with PHP 8.x and report any issues you see.
-
@sebastian-roth Thanks for your work, we are in the process of switching to the dev-branch on Ubuntu 22 now and will report any additional bugs we find.
-
People keep asking about a new release (as well on github). Though there is not much feedback about testing yet.
-
Honestly thanks to everyone doing work on this, I’ve loved using FOG for years at this point.
Is there documentation on installing the future version at all? I’m happy to throw it up on the server at work and test. We re-image devices every few days, so happy to have it sitting next to the other version.
Or is this just sitting in dev branch on github and is the same process as previous?
Thanks again.
-
@RipAU Thanks for your offer to help. Regarding your question I quote my own post from Oktober:
@sebastian-roth said in Release of New Fog Version:
Please keep on using dev-branch more intensely on systems with PHP 8.x and report any issues you see.
-
@sebastian-roth Perfect.
I’ll look at getting a test version up and running and see how it goes.
My work has made internet more clunky to get proxies working so I’ll have to test that as well.
