Stash Latest (2.8) : 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 Stash upgrade guide.

The issues listed below are just the highlights of all those that have been resolved for the Stash 2.4 release.

21 May 2013 - Stash 2.4.2

Type Key Summary
Improvement STASH-3449 Log application version earlier, during startup
Improvement STASH-3157 Improve column width layout for project and repository listings
Bug STASH-3475 Upgrade bundled Tomcat due to security vulnerabilities
Bug STASH-3463 Invalid "Authorization" headers for basic auth result in 500 errors
Bug STASH-3460 During directory synchronization, commit errors trigger cascading rollback failures
Bug STASH-3458 ResourceBundle ClassLoader lock contention under heavy load can soft-lock the system on Java 6
Bug STASH-3452 Cannot create pull request between same branch in different repos
Bug STASH-3448 Database errors during setup and migration produce useless messages
Bug STASH-3447 2.4 RestStashUser not backwards compatible
Bug STASH-3433 Files view shows an old version of README.md
Bug STASH-3427 500 error if the user session has expired when opening the merge dialog
Bug STASH-3393 Forking Git commands fails silently on Solaris when there is not enough memory
Bug STASH-3096 WARNING: Problem with directory [/home/stash/atlassian-stash-data/lib], exists: [false], isDirectory: [false], canRead: [false]
Authenticate to retrieve your issues

8 May 2013 - Stash 2.4.1

Type Key Summary
Bug STASH-3411 Bad submodule file formatting causing 500 errors
Bug STASH-3410 ClientWebFragment NPE if an i18n bundle is available but no key given
Bug STASH-3405 2.4 Links to Stash Docs are pointing to the previous version
Authenticate to retrieve your issues

6 May 2013 - Stash 2.4.0

Type Key Summary
Story STASH-3294 Document user directory related limitations
New Feature STASH-3354 Add decorator for project settings
New Feature STASH-3249 Make rename/copy thresholds in git diff configurable
New Feature STASH-3118 Do not show login form for logged in users
New Feature STASH-3112 Change Gravatar server URL
New Feature STASH-2816 Provide configurable whitespace settings on the diff view
New Feature STASH-2784 Document specifying a custom JIRA issue key regex
New Feature STASH-2643 Repository Permissions
New Feature STASH-2495 Repository forking
Improvement STASH-3361 Restrict permissions on hook settings to repository administrators
Improvement STASH-3351 Add decorator for project tab display
Improvement STASH-3306 Single build link should be actual URL to build
Improvement STASH-3071 Permalink to pull request comments
Improvement STASH-2887 Improve Doc for 64bit TC
Development Task STASH-3145 Doc Task - Update - Running Stash as a Windows service
Development Task STASH-3045 Document process for running Stash as a 64-bit Windows service
Bug STASH-3367 Viewing old pull requests sometimes shows "Activity not found"
Bug STASH-3346 NPE with SSO plugin enabled & Crowd directory set without SSO Domain
Bug STASH-3285 Profile javascript errors for users with numeric usernames starting with zero
Bug STASH-3277 Administration menu highlight for current page is broken
Authenticate to retrieve your issues
4 more issues