FOG 1.5.10.41 and forward
-
https://news.fogproject.org/fog-1-5-10-41-officially-released/
While this maybe spur of the moment, it should officially release 1.5.10 with all relevant bug/security fixes encapsulated (among a few other features.)
This has brought a new methodology of releases in that bug/security releases should be done much more regularly.
dev-branch, historically, was a place where new development occurred (hence its name) but over the last couple of years or so it’s mainly been a bug/security thing, not really a true development approach.
This is OKAY, in my head. Why:
Well we have the master branch which is the ‘baseline’ of a verions. We have the dev-branch, which allows us to work on bugs/security issues. We have the working branches for what will eventually become master. Working is our “dev branch” but keeps proper seperation of things in my opinion.
Basically:
master -> basis for dev-branch (which merges into stable on a regular cadence - still being worked out)
working -> basis of forward developmentSo we effectively have:
production
staging
development well seperated.THis may mean on the regular automated releases, no announcement or news article will be created, and I think that’s okay.
Hopefully exciting we have a release after 1.25 years
Thank you!
-
@Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!