Expected behavior with version control when offline?
Hey guys,
As an experiment, I shutdown my Jazz server and made a few changes to a file that I have under version control.
I could see my changes pile up under a 'unresolved changes' node in my pending changes window. That was a pleasant surprise.
However, I did get a few error dialog boxes that said no server was present.
As soon as I started my server backup, I chose 'checkin-all' in the unresolved node and everything was fine.
It seems like a single dialog box with a 'do you want to work offline' message would be a more graceful experience and make it seem like being offline wasn't necessary a problem.
Thanks,
Eric.
As an experiment, I shutdown my Jazz server and made a few changes to a file that I have under version control.
I could see my changes pile up under a 'unresolved changes' node in my pending changes window. That was a pleasant surprise.
However, I did get a few error dialog boxes that said no server was present.
As soon as I started my server backup, I chose 'checkin-all' in the unresolved node and everything was fine.
It seems like a single dialog box with a 'do you want to work offline' message would be a more graceful experience and make it seem like being offline wasn't necessary a problem.
Thanks,
Eric.
3 answers
Any dialog you get when the server cannot be contacted and you didn't manually run an action is a bug, please report them.
What I mean by "manually run" is that it's acceptable that if you run the deliver action that instead of failing silently it reminds you that the server is not accessible.
And yes, this is the offline experience you'll get with Jazz SCM for 1.0. You can make changes while disconnected and simply check-in when connected again.
Jean-Michel
Jazz Source Control Team
What I mean by "manually run" is that it's acceptable that if you run the deliver action that instead of failing silently it reminds you that the server is not accessible.
And yes, this is the offline experience you'll get with Jazz SCM for 1.0. You can make changes while disconnected and simply check-in when connected again.
Jean-Michel
Jazz Source Control Team