[IDEA] Can you vote for "New Update System" please? Topic is solved

[SCelik]

Can we change vesta update system by including "micro updates"?

Micro Updates: Urgent fixes for individual functions or security fixes.

For example, in version 0.9.8-14 we can not restart system from panel for only "one letter change" "mysql" -> "mysqld" why we wait for next version to solve this bug?

Or quota bug. Many of us faced up with this bug. We set everything correct but we can not login to panel, or upload files to user account becouse of one little tiny bug.

We can consider:

Major Versions: Big changes..

Minor Versions: New features and service pack releases...

Revisions: Little fixes, security issues no new features (micro updates)

So it becomes 0.10.0, starting on now...

0.10.1 we found service restart fix and released immediately.

0.10.2 we found quota bug and released immediately.

0.11.0 for all above plus file manager stuff etc. (ending with 0 ones represents service packs and starting of new features) one a quarter for example?

Or 1.0.0 (Backbone changes, new revolutionary changes etc..)

Please vote: https://bugs.vestacp.com/responses/new-update-system

[mike08]

Sounds good +

[fossxplorer]

Sounds very good and voted!

[abad]

That's how it supposed to be from the start. Every software needs hotfixes which should be released asap, especially in hosting business where a bug can make you a major damage.

[skurudo]

Yep, agree with your idea.

[skurudo]

That's how it supposed to be from the start. Every software needs hotfixes which should be released asap, especially in hosting business where a bug can make you a major damage.

On the sideline talks were the options, but the development process is not as fast as we would like and left on the proposal to consider. Now it's good time to return to discuss about update system.