-
Notifications
You must be signed in to change notification settings - Fork 153
Roadmap
This "Road Map" is under development. It is intended to be a view from 60,000 feet, giving very general idea of the features we expect to add and, at least to an extent, the order in which we expect to add them.
Version 3 is our current stable release series, with 3.14.0 being the latest release.
Although it's possible that 3.14.0 will be our last feature release in the 3.x series, I'm currently expecting that there will be one or two more. The team is currently working on this decision.
Needed Here: What features do we need in the 3.x series before we start making breaking changes for version 4.0?
Version 4.0 will be our next major release. Some of the changes are already present in our repository under the dev4.0 branch, while our master branch continues to track the 3.x series. One key decision we need to make is when to merge those changes into master, essentially putting an end to further 3.x development.
Note: Once we do that, 3.x development isn't actually impossible, but it's a bit more difficult. That's why we need to decide (see above) just what features we want in 3.x before making the switch.
These are the changes we plan, which make it necessary to have a new Major Release. Only the main changes are listed here. For a more complete list see the issues on GitHub.
- Engine API will change. Precisely how is yet to be defined.
- Existing extensions will no longer supported, due to changes in the API. Extension authors will need to create new versions.
- Certain extensions will no longer be bundled with our msi and zip packages: V2 Frameweork Driver, V2 Result Writer, Teamcity extension.
- Certain runner options will no longer be supported: --domain, --process, --inprocess. This means that the default setting of one process per assembly will initially be the only option available. See New Features for exceptions to this.
-
All Agents will be Pluggable Agents, that is, engine extensions. For each release, a set of standard agents will be included as dependencies. The agents included may change from time to time, which will require a separate install of any agents needed, which were no longer included.
Note: Modifying the list of agents bundled with the runner in such a way that tests continue to run using a different agent is not considered a breaking change and will normally be done as a feature release.