-
Notifications
You must be signed in to change notification settings - Fork 92
Release plans
Aaron S. Hawley edited this page Apr 5, 2019
·
4 revisions
The following page contains a draft proposal for future releases. It may not be current or up-to-date.
Methods exist in GitHub for the project admin to plan releases by tagging pull requests or issues and assigning them to release milestones. However, the notes below include activity outside of pull requests. A wiki page also allows others to participate in release planning.
The current proposal documents what has already been merged since the last release on 5-Apr-2019, 1.2.0, and then suggests what to do with the open pull requests and issues.
As of 5-Apr-2019, there are
- 10 open pull requests,
- 27 open issues, and
- master currently contains
- 0 enhancements
- 0 bug-fix pull requests,
- 0 refactoring pull requests, and then
- 3 administrative (build, doc, ...) pull requests.
- @ashawley: Previous releases tried to reduce the risk and the scope of any possible regression by spreading changes across multiple releases, rather than including as much as possible in any single release. For the next release, we can entertain breaking compatability because a classpath defect with sbt and the compiler was fixed in sbt 1.1.2. I propose fixing defects and making improvements, and compatibility changes will trigger a minor version increment. More significant improvements will be delayed for a major version increment 2.0.0.
- Administrative:
- Bump version in build.sbt
- Closed
- None
- Fix?
- Merged
- None
- Merge?
- Merge #110 Add Scalacheck
- 1.0.0 release notes
- 1.0.1 release notes
- 1.0.2 release notes
- 1.0.3 release notes
- 1.0.4 release notes
- 1.0.5 release notes
- 1.0.6 release notes
- 1.1.0 release notes
- 1.1.1 release notes
- 1.2.0 release notes