I'm not sure how well Versions is performing for the parent companies as a revenue-generating product, nor am I asking, but I do wonder if a lack of revenue from licenses is resulting in the slow update schedule. It seems to take weeks for simple little fixes to be incorporated into the application.
Personally, I have been waiting for some time for workflow+interface improvements to come to Versions, and have been told by Versions representatives that these improvements were being considered. They seem like such simple changes, and yet have been completely absent from the past several updates. For example, it should be possible to do an "Update" when in Transcript mode... why the need to switch to Browse mode, click Update, and then return to the Transcript mode? Doesn't make sense why this simple change hasn't been made yet. The Versions representatives have stated that they are refactoring the workflow so that commits and updates are not application-modal, but the user will be able to do other things while an update or commit is taking place. There should be no reason why I should not be able to browse other repositories while an update or commit is taking place. Multiple updates and commits could be queued and execute one after another. An activity pane could be used to access this queue and manage them (re-ordering, cancelling upcoming actions, etc.). Anyway, I just wanted to keep this discussion alive and let the Versions team know that there's still lots of room for improvement in v1.x of the application. I will be disappointed if some of the smaller improvements I've been waiting for are held off until a paid upgrade to v2.x. -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
