>From what I looked, all you need to do is to follow apache release process:
http://www.apache.org/dev/release-publishing.html and have the signatures... However, the binary distribution generation seems to be using nant. I believe there are better ways to do it currently. as far as I know the .NET framework has evolved a lot since them and there are better ways to do this now. Only question I have is how these binaries were signed before? Manually? I couldn't find any scripting to the signatures. On Tue, Jun 18, 2019 at 2:51 AM <[email protected]> wrote: > > Hi Tim or Jim > > > > > Just want to nudge this so you have a chance to respond. > > > > > Best > > > Mike > > > > > Get Outlook for Android > > > > > > > > On Wed, Jun 12, 2019 at 9:48 AM +0100, <[email protected]> > wrote: > > > > > > > > > > > Hi All, > > > > > I am looking to run 1.8.0 release of the API which simply adds netstandard2.0 > build. > > > > > @Jim Gomes or @Timothy Bish, i realise you both historically have run > releases. > > > > > Could i ask for some assistance in my first time releasing .net to ensure i > sign correctly and release inline with how you've done this before? > > > > > Best > > > Mike > > > > > > > > > > > > > Get Outlook for Android > > > > > > > > -- Clebert Suconic
