the.rampage.rado Posted September 16, 2018 Posted September 16, 2018 I'm eager to test the new cache fixes... :)
0 the.rampage.rado Posted September 17, 2018 Author Posted September 17, 2018 Thank you! How much time does it takes with the new automated system to push minor releases let's say every two weeks?
0 Traumflug Posted September 17, 2018 Posted September 17, 2018 Ha ha! A "minor" automated system! :-) More seriously, while it sounds pretty easy to run build.sh in the development repo, which indeed gives a release ZIP, there's plenty of correlated stuff: Reviewing all the modules for changes since the last release. Create module releases as needed. Generating translations and uploading them to Crowdin. Packaging translations on Crowdin. Creating Diffs for the updater. ... and so on. Making a release covers some 30 (manual) steps and is about a day of work. And yes, you're right, 1.0.6 is about a month old, so time to think about 1.0.7.
0 the.rampage.rado Posted September 17, 2018 Author Posted September 17, 2018 I was referring to the 1.0.x version as minor, not your automated system. Can't those items be automated as well?
0 Traumflug Posted September 17, 2018 Posted September 17, 2018 Perhaps they can get fully automated one day, but that's certainly not trivial. ... and now I'll return to writing the Git Updater, which will allow upgrading to the tip of a development branch.
Question
the.rampage.rado
I'm eager to test the new cache fixes... :)
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now