Stash 2.4 release notes
6 May 2013
Introducing Stash 2.4 – Forking in the Enterprise
Today we're pleased to announce Stash 2.4, which introduces several key features to help you manage and collaborate on your Git repositories behind the firewall – forking, a workflow popularized in open source development, along with personal repositories and per-repository permissions.
If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.
The Stash 2.4 changelog is at the bottom of this page.
Forks
Forks in Stash provide developers with a way to contribute code back to a repository for which they do not have write access. This extra control and flexibility of your development process lets you choose workflow scenarios that fit best. You can allow contractors to contribute to a project, or give developers the freedom to spike a project or prototype a feature, without risk to your core repositories.
Stash allows developers to fork a repository into any other project in Stash for which they have admin access. They can also create personal forks and then give others access by applying repository permissions.
Read more about using forks in Stash.
Repository permissions
We've added repository permissions to Stash, which along with the already existing project and branch-level permissions, give you flexible yet fine-grained control over access to your repositories.
Read more about repository permissions in Stash.
Personal repositories
You can now create personal repositories, unrelated to other projects, that you can use for such purposes as storing private snippets of work, kick-starting your own project, or contributing a bug-fix for a project that you are not a member of. By default, personal repositories are not visible to other Stash users. However, you can use repository permissions to open up access to other individuals and groups.
Your personal repositories are listed on the Repositories tab of your profile page. Every Stash user can see your profile page, but they can only see those repositories that you have given them permission to view.
Read more about personal repositories in Stash.
Deprecation of Java 6
This is to give advance notice that Stash 3.0 will not support Java 6.0, and will only support Java 7.0 and above. Stash 3.0 is expected to be released later in 2013.
API changes
Please see the API changelog for any changes made for Stash 2.4.
Small improvements
Managing your Stash account
All the details of your Stash user account are now collected on your Stash account page. Use your account page to manage aspects of your Stash account, including changing your Stash password or avatar, and adding SSH keys.
To go to your account page simply choose Manage account from your user menu in the header:
Secret whitespace query parameter
Sometimes a diff is hard to read simply because multiple lines have only had the whitespace changed. To see just the important changes, use the w=1 (--ignore-all-space) query parameter, which is the same as the git diff option. For example, the URL could look like:
https://stash-your_organisation.com/projects/STASH/repos/your_repo/commits/c573ea24e70c9d21ee?w=1#your_repo_path/DiffRequest.java
Before:
After:
Change log
This section will contain information about the Stash 2.4 minor releases as they become available. These releases will be free to all customers with active Stash software maintenance.
If you are upgrading from an earlier version of Stash, please read the Bitbucket Server upgrade guide.
The issues listed below are just the highlights of all those that have been resolved for the Stash 2.4 release.