Stash 3.3 release notes

10 September 2014

Introducing Stash 3.3

Today we're very pleased to announce the release of Stash 3.3.

If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.

Please also check the End of support announcements for Stash. Add-on developers will be interested in the API changelog.

The Stash 3.3 changelog is at the bottom of this page.

Tasks for pull requests

You can now use tasks in Stash to express and track actions identified during a review. You simply attach tasks to the comments you add to the pull request. We think tasks will make it much easier for developers to see what still needs to be done, and for review owners to keep track of which pull requests need attention before they can be merged.
 


 

Read more about tasks for pull requests.

Small improvements

Tomcat 8

Stash 3.3 now bundles Tomcat 8.0.9. Tomcat 8 implements Servlet 3.1, and also switches from using blocking I/O to non-blocking I/O by default. Non-blocking I/O improves Stash's ability to scale.

Note that Stash will still run if deployed to Tomcat 7 until Stash 4, at which time a Servlet 3.1-compliant container, like Tomcat 8, will be required.

Pull request URLs are displayed in the console after pushing

To save you time, the console now displays the URL to the 'Create pull request' screen in Stash after you push a new branch (or a branch with no pull requests yet):

You'll find that the branch and repository are already correctly selected in Stash, to make life easier still.

When pull requests already exist for the branch, links to those in Stash are displayed instead.

A Stash admin can disable this behaviour as follows: click  Manage add-ons  in the Stash admin area, filter for 'bundled hooks' and click that, then disable the 'print-branch-links-hook' module.

Change log

This section will contain information about the Stash 3.3 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 the highlights of all those that have been resolved for the Stash 3.3.x releases.

21 December 2014 - Stash 3.3.5

Stash 3.3.4 was an internal release.

5 November 2014 - Stash 3.3.3

9 October 2014 - Stash 3.3.2

24 September 2014 - Stash 3.3.1

10 September 2014 - Stash 3.3.0

Redirection notice

This page will redirect to /display/BitbucketServer/Stash+3.3+release+notes .

10 September 2014

Introducing Stash 3.3

Today we're very pleased to announce the release of Stash 3.3.

If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.

Please also check the End of support announcements for Stash. Add-on developers will be interested in the API changelog.

The Stash 3.3 changelog is at the bottom of this page.

Tasks for pull requests

You can now use tasks in Stash to express and track actions identified during a review. You simply attach tasks to the comments you add to the pull request. We think tasks will make it much easier for developers to see what still needs to be done, and for review owners to keep track of which pull requests need attention before they can be merged.
 


 

Read more about tasks for pull requests.

Small improvements

Tomcat 8

Stash 3.3 now bundles Tomcat 8.0.9. Tomcat 8 implements Servlet 3.1, and also switches from using blocking I/O to non-blocking I/O by default. Non-blocking I/O improves Stash's ability to scale.

Note that Stash will still run if deployed to Tomcat 7 until Stash 4, at which time a Servlet 3.1-compliant container, like Tomcat 8, will be required.

Pull request URLs are displayed in the console after pushing

To save you time, the console now displays the URL to the 'Create pull request' screen in Stash after you push a new branch (or a branch with no pull requests yet):

You'll find that the branch and repository are already correctly selected in Stash, to make life easier still.

When pull requests already exist for the branch, links to those in Stash are displayed instead.

A Stash admin can disable this behaviour as follows: click  Manage add-ons  in the Stash admin area, filter for 'bundled hooks' and click that, then disable the 'print-branch-links-hook' module.

Change log

This section will contain information about the Stash 3.3 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 the highlights of all those that have been resolved for the Stash 3.3.x releases.

21 December 2014 - Stash 3.3.5

Stash 3.3.4 was an internal release.

5 November 2014 - Stash 3.3.3

9 October 2014 - Stash 3.3.2

24 September 2014 - Stash 3.3.1

10 September 2014 - Stash 3.3.0

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport