Releasing v7

[WikiRik]

I will update this issue later with more, but there's several things we could do upon releasing v7. Mainly we need to promote the new features and the new scoped package name.

We can do that through;

• Submitting us for the monthly GitHub Release Radar; https://github.com/github/release-radar
• Contacting StackShare and other websites to update their comparison between us and other JS ORMs

What we should also do;

• Contact the maintainers for the projects mentioned in the docs (Resources / Awesome Sequelize) + README to make sure their projects can work with v7 around the release date
• Update contributing guide now with new supported versions, docs in the website repo etc
• Updating outdated information spread around the internet, like comparison with other ORMs. E.g. Prisma

Feel free to comment with more

[fzn0x]

@WikiRik I think creating a blog is good to promote new v7 features, so people can read and start using Sequelize with no hassle.

[fzn0x]

Came across and I think it's related to sequelize/website#125

[ephys]

I agree blog posts would be great. We should showcase them in our upgrade guide to motivate people to migrate

Edit: loving your new profile picture

[fzn0x]

I agree blog posts would be great. We should showcase them in our upgrade guide to motivate people to migrate

Edit: loving your new profile picture

Thank you!

[WikiRik]

On Slack @ephys mentioned the following possible roadmap for when v7 can be released;

• Merge DataTypes PR
• Merge with sequelize-typescript
• Release

"The TS migration won't be fully complete but I think I'll immediately move on to v8 to continue working on it"
Whether v8 will come out in May-June or not is still open for discussion (see #18 for more details on that)

Other things that we still want to fix before v7 from Roadmap are a bit unclear. @ephys can you update the 'Before v7' column and possibly make a separate 'Doing'/'Blocked' column for v8 if some of those things won't be fixed before v7 in your opinion?

[ephys]

Done, all blocked things are postponed to v8

[WikiRik]

The first beta of v7 is getting close which means we should start thinking about how to involve users.

First step would probably be a pinned issue explaining what it means that a beta is out and what our plans are until we release a full version. In that pinned issue we'll highlight the biggest changes we've done (TypeScript, DataTypes, package rename) and that we would like user feedback on it. We'll mention that we want to avoid breaking changes in the betas so users can start to migrate projects already without the fear of changing too much when the next beta comes out. Finally we also mention that apart from reporting bugs we also welcome specific feedback on the upgrade guides of both v6 and v7 so more people will migrate to v7.

After that we should contact maintainers from the projects mentioned here; https://sequelize.org/docs/v7/other-topics/resources/ (and possibly update that list) telling them that v7 is coming up and we'd like it if they update their projects to support v7.

Once that is in full motion, we can start on further outreach like the aforementioned blog posts and making other plans for the real release of v7.0.0.