It would be great if someone can post a fool-proof way of disabling bench auto-update for Self-hosted installations. This will allow some time to safely migrate or for some cases prevent migration altogether.
If below part of instructions is going to cover it, please allow some time to act before actually merging.
@snv how long do you think the staging branch will be more or less in sync with master after the merge? I believe it’s beneficial for people who are on staging at the moment to not wait too long to migrate to the new v11 master after the release. Is this correct?
Yeah, those on staging just need to change branches without the risk of major upgrade issues. Subsequently, staging will probably not be updated. But those on staging can switch whenever suitable and update to the latest master.
I was referring below post before commenting here:
So what I understand is that crontab will run even after auto_update is disabled from bench. But it will check common site config and skip update based on flag set there. A fool proof way would be to remove the job crontab itself.
I discovered that the auto-update is already broken on our servers as the job is unable to find path of bench(sample below from auto_update_log.log). Its been so for all installations we did in past one year. We use easyinstall scripts. /bin/sh: 1: /home/frappe/frappe-bench/env/bin/bench: not found
I am currently using version 11 beta and i upgraded from version 10. One of the major change i noticed with regards to existing data is salary structure. All salary structures are now submitted and locked which means they can’t be modified (at least i haven’t seen any info about being able to modify a submitted salary structure).
Another major change is you now assign salary structure from a separate doctype as against adding employees from within the salary structure itself.
There are new features added to the HR module which improves it overall so in my opinion it is worth the leap.