What's new?¶

First some terminology/concepts:¶

• Local repository = A program or a library which is in your private workspace.
• Commit - A change on a program/library in your private workspace. Commit does not send your code anywhere.
• Publish- Send commits to a published repository, creating it if necessary.
• Published repository - A library or program which is published on mbed.org.
• Pull = Copy commits from another repository to your own
• Push = Copy commits to another repository from your own

Finding and using shared code¶

It's easier to find libraries and example programs, and easier to see what recent development has been done on them. Getting updates of libraries you use is now more powerful - you can see exactly what changes have been made and you can easily switch between versions of libraries. Plus, the versions of any libraries your program uses are seamlessly tracked and updated in line with your program.

• Tutorial: Basic usage

Improving code¶

If you spot a bug or an improvement in a library or program, you can always import it and make your changes. But now, it's a lot easier to contribute your fixes back to the original author. You would simply publish a fork of their library, and the author can pull your fixes directly into his compiler for review with a single click.

• Tutorial: Forking a repository
• Tutorial: Pulling changes from a fork

Sharing code¶

Publishing your code gets a lot more powerful - with full diffs, commit logs, branches and more. You still have the same auto-generated documentation, but you now also have a complete wiki with unlimited pages for each published program or library.

• Tutorial: Being an author: Publishing your code

Working together on code¶

The single greatest area of improvement is in the area of more than one person working on a codebase. We now have two main ways to do this. You can choose to pull changes from forks or to give permission for someone else to commit to your public repository.

• Tutorial: Working with multiple authors
• Tutorial: Pulling changes from a fork

Technical info¶

• Migration from the old publishing system - important notes for betatesters
• Technical background
• Rollout plan