1.6.2 Final Release Checklist

[baconpaul]

This is the final release checklist for 1.6.2 in the next week or two.

Tagging @mortfell @jpcima @VincyZed @tank-trax

• Manual Updates 1.6.2 manual updates  #954
• Stand-alone 16 bit normalized "Create" is not working as expected in wt-tool.py #1078
• Import patches from @mortfell
• Import the claes patches oddy found
• patches with and vs And
• menu item links to https://github.com/surge-synthesizer/surge-synthesizer.github.io/wiki/Additional-Content
• Scan and reclassify or close any other issues in 1.6.2 milestone [here]
  (https://github.com/surge-synthesizer/surge/milestone/4)
• Add the Emu patches which are in presets-wavetables git channel
• Add the Emu fixes for VSCO which are in the same
• LV2 in the README
• Update website to say “LV2” under linux
• Link website to wikis
• Push 162 website updates surge-synthesizer.github.io#100 to master to effect website changes
• Finalize Changelog
• CHangeLog title explicitly mentions 1.6.2
• create release branch and push; wait for release builds
• check release builds
• update home-brew (and this time, document how to update home-brew)
• Announce On KVR (@baconpaul) and Facebook (@tank-trax)
• Say “yay” and close this issue.

For what's up after this release, #1117 explains where @baconpaul is gonna spend a lot of his fall; and also we need to scan and classify all the open issues to sort of clean up the tagging and freshness.

[jpcima]

The LV2 could receive a mention in README as well.

[baconpaul]

Great point yup.

[baconpaul]

Morning. Posting this to both #general and #surge-irc and adding it to use 1134.

My current plan is to release 1.6.2 either (depending on schedule)

• Evening Friday Sep 20
• Afternoon Monday Sep 23
• Morning Wednesday Sep 25

(all times NYC time zone). The necessary steps to do 1.6.2 are all in this issue: #1134 which links to the 1.6.2 tagged GitHub issue

That means if there’s something that has to go in 1.6.2 which isn’t on that checklist or isn’t in the issues linked to by that checklist, we will miss it. Especially @jpcima and @crystalmath I suspect we will have some more LV2 changes, which is why I’m not doing the release this weekend actually!

Next week it would be great if you were all running nightlies and testing the heck out of them. I plan to install 1.6.1.1 on my machine then run the nightly after thet as part of my test plan but more checks and eyes can only help.

And of course if we find something we can delay. But that’s my current thinking.

[gnips]

Don't forget the "About" box :)

[baconpaul]

The "About" box auto-updates at build time. If you build on a branch our CI pipeline will replace the text for us automatically! (but that's one thing to test when we check out the builds :) )

[baconpaul]

Closing this issue. It's just telling a broader user base about it now.

Thanks all!