Thanks Wes. I have a PR up for this. https://github.com/apache/arrow/pull/3891
How do I update the wiki page? Is this source controlled somewhere? I assume we want to add a new section after https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingRubypackages for "Updating C# NuGet package". I put the instructions for building and uploading the package in the csharp/README.md file in my PR. It should be as simple as: 1. Install the latest `.NET Core SDK` from https://dotnet.microsoft.com/download. 2. ~/git/arrow/csharp$ dotnet pack -c Release -p:VersionSuffix='' 3. upload the .nupkg and .snupkg files from ~/git/arrow/csharp/artifacts/ to https://www.nuget.org/packages/manage/upload Eric -----Original Message----- From: Wes McKinney <wesmck...@gmail.com> Sent: Tuesday, March 12, 2019 9:36 AM To: dev@arrow.apache.org Subject: Re: Publishing C# NuGet package thanks Eric -- that sounds great. I think we're going to want to cut the 0.13 release candidate around 2 weeks from now, so that gives some time to get the packaging things sorted out - Wes On Thu, Mar 7, 2019 at 4:46 PM Eric Erhardt <eric.erha...@microsoft.com.invalid> wrote: > > > Some changes may need to be made to the release scripts to update C# > > metadata files. The intent it to make it so that the code artifact can be > > pushed to a package manager using the official ASF release artifact. If we > > don't get it 100% right for 0.13 then > at least we can get a preliminary > > package up there and do things 100% by the books in 0.14. > > The way you build a NuGet package is you call `dotnet pack` on the `.csproj` > file. That will build the .NET assembly (.dll) and package it into a NuGet > package (.nupkg, which is a glorified .zip file). That `.nupkg` file is then > published to the nuget.org website. > > In order to publish it to nuget.org, an account will need to be made to > publish it under. Is that something a PMC member can/will do? The intention > is for the published package to be the official "Apache Arrow" nuget package. > > The .nupkg file can optionally be signed. See > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fnuget%2Fcreate-packages%2Fsign-a-package&data=02%7C01%7CEric.Erhardt%40microsoft.com%7Ce6fd34cac9a84a6d55a208d6a6f81faa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636879981946621803&sdata=O0rddqqjMLzfkPssh3uOd1i70rgsPktaKIFD%2BdDQuTA%3D&reserved=0. > > I can create a JIRA to add all the appropriate NuGet metadata to the .csproj > in the repo. That way no file committed into the repo will need to change in > order to create the NuGet package. I can also add the instructions to create > the NuGet into the csharp README file in that PR.
