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://docs.microsoft.com/en-us/nuget/create-packages/sign-a-package. > > 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.
