It depends on the customers approach to configuration control.
They have a choice, you know. Ultimately they can chose not to use your product.
If the customer will accept you changing stuff every day, and they don't care, and it has no training or configuration management impact; have automatic updates.
Customers with SOE ( Standard operating environments) hate updates.
Realize that some customers are not going to accept software "calling home".
They will want to host their own updates. Their IT people will have to get involved.
This is more work for them.
Some customers will want/need to do their own QA; depends on the customer and the kind of software.
If the customer needs to do testing/work to accept/deploy the software, release some multiple of the length of the test/deploy cycle. Unless the customers are okay with interleaved deploy and test. That's where they are always testing a new version, and the roll it out.
For example: 2 weeks to test, release not more than every 8 weeks.
In result critical software, release testing may take a customer months. They are betting their business on the results and are justifiably cautious. So releases are every 6 months or so.
In safety critical software, it may take MANY months. Annual, or about every 18 months is not uncommon. Even less often is quite normal.