Plan and checklist for v3.1.0 release
jywarren opened this issue · comments
Hi @NARUDESIGNS - i think it's time to start preparing a new release, what do you think?
Let's look at the changes since the last release was made; it looks like the change was at 0ac18eb
as part of: #712
So, all the changes since then (Apr 13, 2021) can be included into v3.1.0 - what do you say?
https://github.com/publiclab/PublicLab.Editor/commits/main
The last time we did this in a more organized way was in #654, so let's copy the checklist out from there:
To do:
- open an issue using the "release" template with this checklist with title
Checklist and coordination for v0.0.0 major/minor/patch release(see semantic versioning) - compile release notes below from corresponding release milestone
- update version number in
package.json(ex #1695) - finalize and merge to
mainbranch (freeze merges tomainbranch until next step) - merge, build and publish
/dist/files tomainbranch (merges tomainbranch can resume for next release) if it hasn't been done in the most recent commits already - create a release on GitHub and use features description + release notes from below
- tag version number branch (i.e.
v3.0.0) - publish tagged branch to
npm(actually did frommainbranch -- @jywarren) - publish to live
github-pagesdemo (so people can see the latest version running in the demo) (from within GitPod works well) - close this issue!
- open a matching PR on
plots2for this new version # (or let Dependabot do it) - - publiclab/plots2#10711
How does this sound? When we collect release notes, we can actually use the auto-generator from the "Releases" feature which is new-ish: https://github.com/publiclab/PublicLab.Editor/releases/new
I just did one as a draft, not sure if you can see it? https://github.com/publiclab/PublicLab.Editor/releases/edit/untagged-a61a5484f15db4097723
Also, we can resolve this pinned issue pretty soon! #721 and #743 !! 🎉
So, all the changes since then (Apr 13, 2021) can be included into v3.1.0 - what do you say?
Hello, @jywarren sorry for the late response here. Where can I find all the changes since April 13th, 2021?
Forgive me I've not participated in an upgrade like this before so I'm a little lost as to what changes we'd be making, esp to the PublicLab Editor
So if you can see this link, when you create a new release it will compile a list automatically from the commit log: https://github.com/publiclab/PublicLab.Editor/releases/edit/untagged-a61a5484f15db4097723
If you try it yourself (i'm not sure you can see it but we'll discuss today) it'd be here: https://github.com/publiclab/PublicLab.Editor/releases/new
Look out for Popper library addition for error handling in HTML template: https://github.com/publiclab/PublicLab.Editor/pull/771/files
Hello, I've updated the version number here - publiclab/PublicLab.Editor#833
Excellent. Let's re-run the "release notes" auto-generation and publish the release!
Want to try doing that Paul? Then i'll show you how to publish to NPM.
Sure I'd try that now.
Let me know how npm publish goes! Doesn't have to be tonight :-)
Hi @jywarren where are we on this progress, please?
I checked the *publish branch to npm... task since we have that out of the way.
Great, i checked "open a matching PR on plots2 for this new version # (or let Dependabot do it)" - publiclab/plots2#10711
Hey @jywarren I want to complete this issue " publish to live github-pages demo (so people can see the latest version running in the demo) (from within GitPod works well)" as it seems like this will complete the whole issue. I need some help on this