Jump to content
thirty bees forum

Question

5 answers to this question

Recommended Posts

  • 0
Posted

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
Posted

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.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...