Changes between Initial Version and Version 1 of Ticket #52324, comment 8
- Timestamp:
- Sep 26, 2016, 7:03:41 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #52324, comment 8
initial v1 1 I'm a h aveuser of this program and due to their past history in breaking backwards compatibility, I really would like to discuss the possibility of naming this port `syncthing-0.14` so the user has to explicitly upgrade to a new "major" version (it's 0.x is because the protocol is not set in stone yet). An automatic upgrade would make the device not able to synchronize until all other devices are upgraded at the same time, rendering the program effectively useless. Speaking as a user of this port, I would find that very disruptive/annoying.1 I'm a heavy user of this program and due to their past history in breaking backwards compatibility, I really would like to discuss the possibility of naming this port `syncthing-0.14` so the user has to explicitly upgrade to a new "major" version (it's 0.x is because the protocol is not set in stone yet). An automatic upgrade would make the device not able to synchronize until all other devices are upgraded at the same time, rendering the program effectively useless. Speaking as a user of this port, I would find that very disruptive/annoying. 2 2 3 3 Once a new "major" version is out we could release a new revision for the previous version with a note saying that users should install the new port if they want new updates. I don't think it's necessary to maintain more than the newest and the previous version. Older versions can be just made obsolete.