Cake 2.0 cleanup tasks - Githubissues

cake-build / processes

Steps that are taken by Cake Team during deployment of various components

MIT License

0 stars 6 forks source link

Cake 2.0 cleanup tasks #38

Open pascalberger opened 3 years ago

pascalberger commented 3 years ago

The following tasks are required after 2.0 has been released:

[x] Deprecated Cake NuGet package on nuget.org with reference to Cake.Tool package
[x] Deprecated Cake.CoreCLR NuGet package on nuget.org with reference to Cake.Tool package
[ ] Deprecate Azure DevOps Cake Extension
[x] Unlist Cake.Portable Chocolatey package
[ ] Check homebrew process. Is there an unlist process where ID is stil reserved?

augustoproiete commented 3 years ago

When deprecating these NuGet packages, I suggest we release a new patch increment version (branched out of v1.3.0) that:

Update the description with DEPRECATED. We recommend using [Cake .NET Tool](https://cakebuild.net/docs/running-builds/runners/dotnet-tool) runner moving forward. so that it shows up in the nuget.org search
Update the icon of the package with something that calls out attention that it's deprecated - I took a stab at be below:

cake-medium-deprecated

gep13 commented 3 years ago

@augustoproiete i think this is a great idea!

pascalberger commented 3 years ago

@augustoproiete @gep13 I'm not a big fan of publishing a whole release just for changing icon and package metadata. What speaks against using just the deprecation feature of nuget.org?

augustoproiete commented 3 years ago

@pascalberger I tried to explain above: The nuget.org doesn't show that a package is deprecated in the search, so you have no way to know that it's deprecated and there's no link to the recommended package.

For example, if you search for Serilog AmazonS3 you'll find these two packages below:

The first one is deprecated using the deprecation feature of nuget.org and the second one is the package recommended as alternative moving forward.

There's nothing that shows you any of that in the search 😞

You don't see any info about deprecation until you actually navigate to the details of a specific the package - then they show you the deprecation information.

Contrast that with a search for Ookii:

IMO, it's a much better experience.

augustoproiete commented 3 years ago

BTW, would we need to do a full release even if our end-goal is to only deploy these two packages?

i.e. Wouldn't it be possible to download these two packages from nuget.org, change the metadata/icon with NuGet Package Explorer, Save As v1.3.1, sign with the DNF key, and publish only these two new packages?

pascalberger commented 2 years ago

Decision: Deprecate packages using nuget.org deprecation feature and don't replace icons / readme to avoid shipping a new release.