Skip to content

Conversation

@araffin
Copy link
Member

@araffin araffin commented Feb 28, 2021

Description

We are finally releasing v1.0 =)!
The plan is to have the release candidate for one/two weeks in case we spot critical bugs.

Motivation and Context

  • I have raised an issue to propose this change (required for new features and bug fixes)

closes #1

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (update in the documentation)

Checklist:

  • I've read the CONTRIBUTION guide (required)
  • I have updated the changelog accordingly (required).
  • My change requires a change to the documentation.
  • I have updated the tests accordingly (required for a bug fix or a new feature).
  • I have updated the documentation accordingly.
  • I have reformatted the code using make format (required)
  • I have checked the codestyle using make check-codestyle and make lint (required)
  • I have ensured make pytest and make type both pass. (required)
  • I have checked that the documentation builds using make doc (required)

Note: You can run most of the checks using make commit-checks.

Note: we are using a maximum length of 127 characters per line

Copy link
Collaborator

@AdamGleave AdamGleave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM -- excited to be out of beta!

@araffin araffin merged commit d0d55f3 into master Mar 1, 2021
@araffin araffin deleted the feat/release-v1.0RC0 branch March 1, 2021 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Roadmap to Stable-Baselines3 V1.0

3 participants