-
Notifications
You must be signed in to change notification settings - Fork 214
Neutrino 9 release checklist #1132
Comments
@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 |
Possible wording:
Thoughts? |
I am super impatience for Neutrino 9 to be released, amazing job and definitely the best move ever. Nice job! |
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.
@edmorley all the packages should now be moved over. Also 👍 to the release wording. |
@edmorley I think the time has come to pull the trigger. Thoughts? |
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? :-) |
Also perhaps #1388? |
The trigger is not pulled yet. Any news on this? |
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! |
@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: I've updated the proposed release summary above to reflect ESLint 6: |
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 With that, we should be all done here :-) |
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:
master
, to:master
v9.0.0
commit message body (and thus inserted in the changelog)master
branch (rather thanrelease/v8
), and thatrelease/v8
is then set to deploy to https://release-v8.neutrinojs.org/ insteadrelease/v8
to:package/*/README.md
to reference the new subdomainnext
andbeta
tagsNeutrino 9
milestone on githubThe text was updated successfully, but these errors were encountered: