Skip to content

Milestones

List view

  • This is another **beta** release

    No due date
    5/5 issues closed
  • This is expected to be a **beta** release. Perhaps beta 2 maybe beta 1, depending on how 0.11 goes.

    No due date
    12/12 issues closed
  • This milestone is mainly enhancements that might get me to a reasonable beta state.

    No due date
    5/5 issues closed
  • This milestone contains enhancements which are planned before the v1.0 release.

    No due date
    8/8 issues closed
  • This milestone is for any remaining tasks (from version 0.8 or before) which should be completed before the project goes to beta.

    No due date
    9/9 issues closed
  • This release will contain further feature enhancements which will be prioritised whilst testing under a real project.

    No due date
    9/9 issues closed
  • This is a milestone carrying urgent fixes which prevent further testing of Screenplay from within an application.

    No due date
    2/2 issues closed
  • Milestone 0.7 is intended as a feature enhancement release. It also addresses some non-backwards-compatible changes which must be made before the project is suitable to go to beta.

    No due date
    8/8 issues closed
  • This milestone addresses further priorities, including issues found whilst integrating an alpha release of Screenplay in Agiil.

    No due date
    12/12 issues closed
  • This milestone aims to round off the core functionality of the library. The intent being to get it into a usable state and to stabilise the API of that core functionality. Remaining work after this milestone is hoped to be only backwards-compatible enhancements. This milestone is also the point at which I will have another test of the project within an external project - in order to identify whether there are any further improvements required in order to use it 'in the real world'.

    No due date
    4/4 issues closed
  • The main focus of this milestone (still working in alpha) is to address a number of the tickets which would break backwards-compatibility when they are addressed. Thus this could be thought of as an effort to try and shape up the API in the view of assessing it for suitability..

    No due date
    9/9 issues closed
  • This milestone represents the next level of priority issues in order to come up with another alpha release.

    No due date
    8/8 issues closed
  • This is the second alpha release, including lessons learned from the first alpha.

    No due date
    8/8 issues closed
  • This is to be the first alpha release, for some testing using other projects.

    No due date
    10/10 issues closed