Frequently Asked Questions

I want to help out with Jasmine, where should I start?

Thanks for your help! The Jasmine team only has limited time to work on Jasmine so we appreciate all the help we get from the community.

Pivotal Tracker

We have a backlog in Pivotal Tracker that we keep up to date with work the Jasmine team wants to get into Jasmine. Look at the top of the current iteration or backlog column for the prioritized list of functionality. Unfortunately, PivotalTracker doesn’t have a great way to allow for comments and questions on a story for people who aren’t already joined into the project. Hopefully the stories are mostly self-explanatory, but it not please ask a question in the associated github issue (if any), or ask a question on the developers list.

Github Issues

When github issues are reported that seem like things Jasmine could support, we will label the issue with “ready for work”. This label means that we believe there is enough information included in the conversation for someone to implement on their own. (We’re not always correct, if you have further questions, please ask).

When is the next release of Jasmine?

Because Jasmine is maintained in our free time, releases don’t always come out in a timely manner. We strive to release a minor version (versioning strategy) every few months, based on the amount of functionality that has been added since the last release. This goal could get moved if we haven’t gotten time to add functionality or merge pull requests, as the amount of new functionality since the last release may not seem large enough to warrant a new release. Additionally, though we obviously strive not to break things, when a minor release breaks some functionality, we do our best to get the issues fixed in patch releases as quickly as possible.

How does Jasmine get versioned?

Jasmine attempts as best as possible to follow semantic versioning. This means we reserve major versions (1.0, 2.0, etc.) for breaking changes or other significant work. Most Jasmine releases end up being minor releases (2.3, 2.4, etc.). These version numbers are dictated by the version of jasmine-core and when the major or minor version is bumped for jasmine-core, we also release new versions of the other primary binding libraries (jasmine-py, jasmine-gem, and jasmine-npm) that bump their depedency to the newest minor version of jasmine-core. This means that when you update your jasmine dependency, you’ll also get the newest jasmine-core. This leaves patch versions up to the particular project, so a patch release (2.4.2, 2.6.3, etc.) of jasmine-core won’t require a release of any of the binding libraries, as they could require their own patch releases.

Have a question we missed?

Please open an issue or pull request