Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Neutrino 9 release checklist #1132

Closed
10 tasks done
edmorley opened this issue Sep 21, 2018 · 12 comments
Closed
10 tasks done

Neutrino 9 release checklist #1132

edmorley opened this issue Sep 21, 2018 · 12 comments
Assignees
Milestone

Comments

@edmorley
Copy link
Member

edmorley commented Sep 21, 2018

Neutrino 9 beta is now out (see #1129 for more info/to leave feedback).

Once we're ready to release v9 final, we'll also need to:

@edmorley edmorley added this to the v9 milestone Sep 21, 2018
@edmorley edmorley self-assigned this Nov 27, 2018
@edmorley
Copy link
Member Author

edmorley commented Nov 27, 2018

  • draft NPM deprecation messages for each of the removed packages (and probably worth revisiting packages that were removed in the past, seeing if they are all deprecated correctly/update messaging)

New packages to deprecate for Neutrino 9 (last version 8.x):

Legacy packages for which we may want to update/add deprecation messages...

Removed in Neutrino 8 (most recent version 7.x):

...all have message of form:
"This package is now deprecated for use with Neutrino v8. Please use @neutrinojs/banner with Neutrino v8."

Removed in Neutrino 6 (most recent version 5.x):

Removed in Neutrino 5 (most recent version 4.x):

Removed in Neutrino 3 (most recent version 2.x):

@edmorley
Copy link
Member Author

@eliperelman many of the deprecated packages have some versions that are not deprecated (eg beta releases). I believe this might interfere with bots like Renovate, since it treats "everything deprecated" differently to "only some versions deprecated".

I tried to fix this up, however most of the neutrino-* packages are not under the neutrinojs npmjs org. Would you be able to move them over?

@edmorley
Copy link
Member Author

edmorley commented Nov 28, 2018

draft the release summary that will be used as the v9.0.0 commit message body (and thus inserted in the changelog)

Possible wording:

v9.0.0

Neutrino 9 is our largest release ever, and includes upgrades to webpack 4,
Babel 7 and ESLint 6, along with significant performance improvements.

The biggest breaking change is the necessity to use external tools *alongside*
Neutrino, i.e. webpack, ESLint, Jest, Karma, and others' native CLIs will be
used in tandem with Neutrino rather than being used internally via their APIs.
This fixes many bugs, gives more control over how these tools are run and means
usage of new features is no longer blocked on Neutrino changes to support them.

Please see the migration guide for how to update:
https://neutrinojs.org/migration-guide/#neutrino-v8-to-v9

If you encounter any bugs, have questions or spot improvements that can be made
to the migration guide/docs - we'd love to hear from you:
https://github.com/neutrinojs/neutrino/issues

Thoughts?

@yordis
Copy link

yordis commented Nov 28, 2018

I am super impatience for Neutrino 9 to be released, amazing job and definitely the best move ever.

Nice job!

edmorley added a commit that referenced this issue Nov 28, 2018
The Git tag and subdomain don't yet exist, but we need these in place
first. (It's not possible to add the subdomain on Netlify yet, since
they don't allow double-deploying the same branch to the main site
and a subdomain.)

See #1132.
@eliperelman
Copy link
Member

@edmorley all the packages should now be moved over. Also 👍 to the release wording.

@eliperelman
Copy link
Member

@edmorley I think the time has come to pull the trigger. Thoughts?

@edmorley
Copy link
Member Author

Sorry for the delayed reply, I've been away for a few weeks this month.

Yeah I agree we should release soon. Perhaps just #1404 and then call it a day? :-)

@edmorley
Copy link
Member Author

Also perhaps #1388?

@ringods
Copy link
Contributor

ringods commented Sep 5, 2019

The trigger is not pulled yet. Any news on this?

@edclement
Copy link

I just looked at this checklist to see if there was anything I could assist with? Doesn't appear so (let me know if there is). Really looking forward to seeing v9 released so we can update eslint. Thanks!

@edmorley
Copy link
Member Author

edmorley commented Nov 4, 2019

@edclement sorry for the delayed reply; new job and no longer actively working with front-end projects (that have a need for something like Neutrino) taking it's toll.

I think we should just release imminently - once #1484 is merged there's not anything critical left:
https://github.com/neutrinojs/neutrino/milestone/6

I've updated the proposed release summary above to reflect ESLint 6:
#1132 (comment)

This was referenced Dec 13, 2019
@edmorley
Copy link
Member Author

I've set/updated the NPM package deprecation messages as follows...

Packages removed in v9:

for p in @neutrinojs{babel-minify,chunk,env,fork,hot,image-minify,loader-merge,minify,pwa,stylelint}; do npm deprecate ${p} "This package is deprecated. See: https://neutrinojs.org/migration-guide/#neutrino-v8-to-v9" --otp=NNNNNN; done

Packages removed in v8:

for p in neutrino-middleware-{banner,chunk,clean,compile-loader,copy,dev-server,env,eslint,font-loader,hot,html-loader,html-template,image-loader,loader-merge,minify,pwa,start-server,style-loader} neutrino-preset-{airbnb-base,jest,karma,mocha,node,react,web}; do npm deprecate ${p} "This package is deprecated. See: https://neutrinojs.org/migration-guide/#neutrino-v7-to-v8" --otp=NNNNNN; done

Packages removed in v6:

npm deprecate neutrino-middleware-named-modules "This package is deprecated. See: https://neutrinojs.org/migration-guide/#neutrino-v5-to-v6"

Packages removed in v5:

npm deprecate neutrino-lint-base "This package is deprecated. See: https://neutrinojs.org/migration-guide/#neutrino-v4-to-v5"

Packages removed in v3:

npm deprecate neutrino-preset-base "This package is deprecated. Please update to a newer version of Neutrino: https://neutrinojs.org/"

And then old tags have been removed from all packages using npm dist-tag rm <package> <tag-name>.

With that, we should be all done here :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

5 participants