Skip to content

Post 0.10.0 Release - Tasks and some statement #518

Closed
@wzrdtales

Description

@wzrdtales

Foreword

As I announced a bit earlier within a discussion of one issue, I decided to finally move 0.10.0 out of beta. This has several reasons. On the one hand, it has not been that much of a "beta", it was quite stable all the time, but included some drafted features, not quite ready stuff and all in all db-migrate has been quite mostly revisited all the way down. This included for example moving out the drivers and a lot of other stuff that happened during the development. And on the other hand it hinders moving forward and creates confusion.
The decision to move along at this point, should help getting features out faster and continue the development more fluent again. This means a few of changes for all future releases, in the way how they're being released.

Tasks

This opens a few tasks, that are being pursued in the next days:

  • Adding a CoC
  • Revisit the contribution guidelines
  • Adjust the build pipeline - i.e. add code styles to it
  • Officially drop support for all node <4 versions for all db-migrate versions > 0.10.x
  • Define the stabilization checkpoint 1.0.0
  • Open necessary RFCs
  • Add issue templates
  • Review DCO - Testing
  • Review parts of the documentation - help is appreciated!
  • Add probot
  • Update devDependencies up to the version barrier

Conventional Commits

All future commits that describe the feature that a developer wants to add, must in the future follow the Angular Convention. Which you can review here:

https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-angular/convention.md

This will help to have a thorough Changelog for all subsequent releases.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions