3 Answers, 1 is accepted
No, you did not miss anything in the docs. In BETA version we have implemented version control for a single user scenario only. Obviously team development and the ability for you to share the project with other team members is crucial and we're working hard to to enable that as soon as possible.
Please stay tuned,
Clemri
In Graphite, you can at least start a project from an external Git resource (like GitHub). If you can continue committing to it (which, as I mentioned, no idea if you can), would this suffice for the team environment?
The first BETA version of Icenium was limited to single-user scenarios. When you create a new project, a local Git repository is created for that project as well, and all commits go to that repository.
With the BETA 2 release we have added some basic features for team collaboration in Graphite. Now it is possible to push your local Git repository to a remote one (e.g. hosted in GitHub, BitBucket etc.) Other team members can clone that remote repository and continue working on it, while pushing and pulling changes on regular basis as usual.
With Version 1 we have also added some GitHub integration to Graphite.
At the present moment Mist is not mature enough in its version control integration, however that will improve in the near future, so please stay tuned. Eventually at some point Mist will be on par with Graphite in regards to version control support.
For now you can use Graphite if team collaboration is necessary. You can read more about our version control integration in Graphite here: Integrated Version Control; Version Control Providers Integration. The currently supported features in Mist are described here: Integrated Version Control In Mist.
Ivan
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.