Cake 0.38.2 Release

[gep13]

Useful information

• AppVeyor builds
• Travis builds
• Bitrise
• Azure Pipelines

Repository Pre-requisites

Automated Approach

• [x] Make sure you have a fork of Homebrew/homebrew-core.
• [x] Run the Prereqs.ps1 file, using the following as an example .\Prereqs.ps1 -GithubUsername gep13 (use your own username). This will clone a new version of all required repositories.

Let people know that things are happening...

• [x] Go to the Gitter room for Cake and inform people that a release is away to happen. Use a message similar to the following @/all We will soon start preparing for the [0.35.0 release](https://github.com/cake-build/cake/milestone/60?closed=1) of Cake. So this is a friendly reminder to pin your Cake version.
• [x] Go to the Gitter room for Cake-Contrib and inform people that a release is away to happen. Use a message similar to the following @/all We will soon start preparing for the [0.35.0 release](https://github.com/cake-build/cake/milestone/60?closed=1) of Cake. So this is a friendly reminder to pin your Cake version.
• [x] Go to the General Channel in the Slack Team for Cake-Contrib and inform peoploe that a release is away to happen. Use a message similar to the following @channel We will soon start preparing for the 0.35.0 release ( https://github.com/cake-build/cake/milestone/60?closed=1 ) of Cake. So this is a friendly reminder to pin your Cake version.
• [x] Using the Cake Twitter account, tweet to let people know that the release is away to happen. Use something like the following We are starting to prepare our next release, 0.35.0 (https://github.com/cake-build/cake/milestone/60?closed=1). This is your friendly reminder that if you haven't pinned to a specific version of Cake, you should do it now :-) https://cakebuild.net/docs/tutorials/pinning-cake-version
• [x] Retweet the above from the cake-contrib twitter account

GitHub Issues Pre-requisites

• [x] Make sure all issues within the milestone are tagged with either Bug, Feature, Improvement, Documentation, Breaking change, or Build
• [x] Make sure all issues associated with the milestone are closed
• [x] Make sure that all issues only have 1 label associated with them
• [x] Raise an issue in the Cake.AddinDiscoverer repo if there are any breaking changes so the discoverer can be modified to generate a new markdown report and also Excel report to track which addins are compatible with this new release of Cake.

When doing a release

• [x] Create branch locally to match the name of the release, for example git checkout -b release/0.35.0 develop
• [x] Update releasenotes.md to include next version number as a placeholder and save the file
• [x] Create release notes on GitHub using the ReleaseNotes task (.\build.ps1 --target=ReleaseNotes)
• [x] Update releasenotes.md with generated content (making sure to keep the formatting the same)
• [x] Build everything (./build.ps1) to make sure it works.
• [x] Commit the changes to releasenotes.md and solutioninfo.cs. Use comment like (build) Updated version and release notes.
• [x] At this point, if you want to share the work to date, and validate something, push the local release branch to GitHub
• [x] Assuming everything is ok, switch to main branch (git checkout main)
• [x] Merge release branch to the main git merge --no-ff release/0.35.0
• [x] Build everything (./build.ps1) to make sure it works (we can never be too sure).
• [x] Push main branch.
• [x] Make sure that both the AppVeyor, Bitrise Ubuntu and Bitrise OSX builds succeed before going any further.
• [x] Assuming that everything went ok, go to the draft release in GitHub and click Edit
• [x] Click the Publish Release button
• [x] This will trigger another build in AppVeyor, but this time with a tag.
• [ ] From the AppVeyor Log, take a note of the generated Hash from the Publish-HomeBrew task ENTERARCHIVEHASH
• [x] Switch to develop branch git checkout develop
• [x] Merge release branch into develop git merge --no-ff release/0.35.0
• [x] Resolve any merge conflicts
• [x] Bump the Cake Tool Version number in build.config to the latest released version, i.e. the version you just released
• [x] Build everything (./build.ps1) to make sure it works.
• [x] Commit the changes to build.ps1 and build.sh NOTE: There will be other changes to the *.json files as well, commit everything. Use commit message like (build) Updated Cake tool to version 0.35.0
• [x] Push develop branch.
• [x] Delete the local release branch that was created git branch -d release/0.35.0 (and the remote one, if pushed to GitHub git push origin --delete release/0.35.0)

After a release/hotfix

• [x] Make sure that everything has pushed correctly to nuget
  • Cake
  • Cake.Core
  • Cake.CoreCLR
  • Cake.Common
  • Cake.Testing
  • Cake.NuGet
  • Cake.Tool
• [x] Make sure that everything has pushed correctly to chocolatey
  • cake.portable NOTE: This package might be subject to moderation, and might not appear immediately
• [x] Move to homebrew repository
• [x] Create a new branch for current release git checkout -b cake-0.35.0
• [x] Open the Formula/cake.rb
• [x] Update the url (line 4) to be the new download location
• [x] Update the sha256 (line 5) to be the value that was generated earlier by the Publish-HomeBrew task
• [x] Commit the changes to cake.rb NOTE: Commit message should use the following format cake 0.35.0 NOTE: Make sure to use a lower case C as that is the preferred formatting in the Homebrew repo
• [x] Push the new branch to your fork
• [x] Open a PR against the master branch of Homebrew/homebrew-core
• [x] Move to example repository
• [x] Open the tools/packages.config file
• [x] Update the Cake version number to be the same as the version that you have just released
• [x] Build everything (./build.ps1 or ./build.sh) to make sure it works.
• [x] Commit changes. Use message similar to (build) Updated Cake tool to version 0.35.0
• [x] Push branch
• [x] Move to resources repository
• [x] Switch to the develop branch git checkout develop
• [x] Open the packages.config file
• [x] Update the Cake version number to be the same as the version that you have just released
• [x] Commit changes. Use message similar to (build) Updated Cake tool to version 0.35.0
• [x] Push branch git push
• [x] Checkout master git checkout master
• [x] Merge changes from develop branch git merge --no-ff develop
• [x] Push branch git push
• [ ] Trigger new container builds on Azure Pipelines.
• [x] Move to website repository
• [x] Create a branch for a new blog post git checkout -b 0.35.0-Blog-Post master
• [x] You can get draft blog post using the console secrets\Processes\FetchContributors
  • dotnet restore
  • dotnet run "cake-build" "cake" "v0.34.1" "d4a0b3a07caa6a3873cb0da58766ffdb7ce22e11" "\cake0.35.0\repositories\devlead\website\input\blog" "v0.35.0"
• [x] Bump the Cake Tool Version number in build.config to the latest released version, i.e. the version you just released
• [x] Commit changes to build.config file using message similar to (build) Updated Cake tool to version 0.35.0
• [x] Commit blog post using message similar to v0.35.0 Blog Post
• [x] Push branch and submit pull request
• [x] Have someone else verify the contents
• [x] Merge the Pull Request
• [x] Go to develop.cakebuild.net once you receive the Azure notification in Slack to say that the development site is deployed. Make sure that it works as expected.
• [x] Go to cakebuild.net once you receive the Azure notification in Slack to say that the development site is deployed. Make sure that it works as expected.
• [x] Go to the Cake-Contrib Gitter Room and let people know that it was released. Use something like @/all Version 0.35.0 of the Cake has just been released, https://www.nuget.org/packages/Cake.
• [x] Go to the Cake-Contrib Slack Team and in the General Room let people know that it was released. Use something like @channel Version 0.35.0 of the Cake has just been released, https://www.nuget.org/packages/Cake.
• [x] Go to the On .Net Link submission form and add link to the post
• [x] Go to reddit and submit link reddit.com/r/dotnet,
  • https://www.reddit.com/r/dotnet/comments/gzvg2q/cake_v0382_released/
• [x] Go to LinkedIn and create a new post
  • [x] Start a post
  • https://www.linkedin.com/feed/update/urn:li:activity:6676219357984497664
• [x] Go to Medium
  • [x] Log into Medium as the cake-build twitter user
  • [x] Click on the Cake logo at top right of screen, then click on Stories
  • [x] Click on Import a Store
  • [x] Enter url of blog post and click Import (if this errors out, just try it again)
  • [ ] ~~ Import failed this time so used medium Create post API to create draft with canonicalUrl ~~
  • [x] Click on see your story
  • [x] Remove the first line of the imported story
  • [x] Click Publish and enter the tagsDevOps Csharp Release Notes Dotnet Continuous Integration
  • [x] Click Publish
  • https://medium.com/@cakebuildnet/cake-v0-38-2-released-4a93e473af72
• [x] .NET Foundation Newsletter
  • [x] Create PR to latest unpublished news letter at github.com/dotnet-foundation/newsletter
  • https://github.com/dotnet-foundation/newsletter/pull/
• [x] Go to the Cake Slack Channel and share the links to Medium, LinkedIn and reddit so that other team members can share them
• [x] Go and have a drink!

[gep13]

@devlead I am going to leave this issue open to track the outstanding task for the container builds.

[gep13]

@augustoproiete just wanted to follow up with regard to this issue... it was being left open as a reminder that the process for the docker container wasn't finished yet. Is this being tracked elsewhere? Does it make sense to go back to generate docker containers for these earlier versions?

[augustoproiete]

@gep13 I'm not aware if this is tracked anywhere else ( should it be here https://github.com/cake-build/docker/issues ? )

Feel free to reopen if you think this reminder is useful. I just cleaned up in batch all the old releases except 1.0.0.

Re: Generate containers for old versions, it's been 9 months since this release and I haven't seen any requests for it yet, so doesn't seem like people need it. If it's 5 minutes to create, then sure, but more that that I'd say it's not worth it.

Either way, if we want this to be actioned, I think it has a better chance if we centralize issues in the main Cake repo where we're looking more often.