v7 release planning

[mcollina]

I think it's time we ship v7. This is a tracking issue of all things we should do:

• start a 6.x line
• merge next into master
• add an LTS doc Improved LTS documentation #1060
• check for deprecations we should remove removed all outstanding deprecations #1057
• migration guide / release notes
• add transport support to pino-socket pino v7 transport pino-socket#36
• add transport support to pino-mongodb Pino 7 new transport interface pino-mongodb#63
• add transport support to pino-syslog Pino 7 upgrade pino-syslog#13
• add transport support to pino-toke Pino 7 pino-toke#8
• add transport support to pino-http-print major: Pino 7 transport pino-http-print#14
• update release notes https://github.com/pinojs/pino/releases/tag/untagged-f20bdd7168d2a42595bf

After release:

• blog post https://www.nearform.com/blog/pino7-0-0-pino-transport-worker_thread-transport/
• remove part of the multistream support that was moved into pino from https://github.com/pinojs/pino-multi-stream: Updates to pino v7, as pino.multistream is already in pino. pino-multi-stream#76

[mcollina]

@jsumners @davidmarkclements @kibertoad wdyt?

[kibertoad]

@mcollina We dropped engines part from package.json, and there is no documentation entry explaining supported versions, and it's not very intuitive for people to check CI config to figure out what is supported. Are we only going to communicate the change via release notes?

[kibertoad]

Maybe we should also bump dependencies all across the board as well?

[mcollina]

@mcollina We dropped engines part from package.json, and there is no documentation entry explaining supported versions, and it's not very intuitive for people to check CI config to figure out what is supported. Are we only going to communicate the change via release notes?

Aggreed!

[mcollina]

Maybe we should also bump dependencies all across the board as well?

I think we are already up-to-date. Some of the dependencies moved to esm so they cannot be updated. We might want to consider forking or replacing instead.

[kibertoad]

@mcollina Can't we tackle the ESM requirement after v7 lands, by dropping 12 for v8 next?

[mcollina]

@mcollina Can't we tackle the ESM requirement after v7 lands, by dropping 12 for v8 next?

I would open a separate issue to discuss ESM migration. My stance on this has not changed: until there is a clear way for APMs to use ESM, we cannot migrate. Node.js v16 does not have such a mechanism, so I think we are targeting many years of cjs still.

[jsumners]

The list looks good. Probably easier to track via a project, but 🤷‍♂️

[mcollina]

Do we want to start issuing release candidates before or after the merge of next into master?

[jsumners]

After seems appropriate.

[mcollina]

@jsumners I have prepared the release notes: https://github.com/pinojs/pino/releases/edit/untagged-dbc8943e8571f30c52c1.

Let me know what you think

[jsumners]

@jsumners I have prepared the release notes: pinojs/pino/releases/edit/untagged-dbc8943e8571f30c52c1.

Let me know what you think

Superb!

[kibertoad]

@mcollina Is there a reason why we use old var syntax in release notes examples?
Also TS types might need slightly more emphasis, especially since they are a breaking change for those who used to rely on DefinitelyTyped ones. Mentioning the need to migrate and drop the redundant dependency would probably be helpful.

[jsumners]

They do mention the need to drop the old types package.

[kibertoad]

@jsumners Awww, sorry, somehow managed to miss the whole section on TypeScript, only saw it mentioned in the merged pull request list, hence my comment. Yes, it is good now.

[mcollina]

pino@7.0.0-rc.1 is out on npm.

[vladshcherbin]

Hey 👋 I've tried to use pino-papertrail with pino v7 as in transport docs example, seems to be working. Would be nice if any of maintainers could check, I'm a pino novice. Here's linked issue with example inside:

ovhemert/pino-papertrail#48

[mcollina]

I have updated the todo list at the top with a list of modules to port.

[jsumners]

pino-arborsculpture is not a transport.

[mcollina]

removed!

[Eomm]

add transport support to pino-socket

working on it

[Eomm]

add transport support to pino-mongodb

Working on it

[zgwit]

@mcollina I am glade to ship pino@v7. can i use it now?

[mcollina]

I think it would be great!

[mcollina]

I'm planning to ship v7 on Thursday, October 14th.

[jsumners]

[mcollina]

blog post is out: https://www.nearform.com/blog/pino7-0-0-pino-transport-worker_thread-transport/

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.