Thx for precisions.
(I skipped FAQ page because though it was a title inside menu)
I understood sales < $100 are not lost, it's the time to get paid who is aleatory for small sales.
Also, re-uploading and replacing an archive should be enabled, there are always bugs left in any programming work that needs to be corrected by an update numbered with new version.
Once you upload main extension archive, you set it to specific version. If you need to update, you need to create a new version and add new archive. It is pretty simple.
There are reasons for this.
1. We need to make sure that there is version assign for every extension, and developer follows good practice of code versioning and appropriate testing.
2. If #1 is followed properly we can notify users of updates.
3. Very frequent updates of archive will require a lot of our attention to validate .
Again, this can be changed in the future as we develop automated process for this.
I personally do not see any problem here. Every developer needs to do good testing before releasing extension.
If there are bugs, it is OK. Fix all reported bugs and release new version. Do not update archive for each bug fixed separately.
Allowing, silently updating archive is not a good approach.
Pretend, we allow this, how will you know what code base your customer has? Did he get your code before or after your fix?
This is just my point, but we are open for suggestions.
