logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Things to do before the next release
Date Wed, 14 Sep 2016 14:53:31 GMT
Hi all

right now I'm able to build .NET 2.0 up to 4.5 and .NET Core with a
single invocation of NAnt on my Win7 VM. We'll see if I find a way to
also include Mono there, alternatively I can - once again - jiggle with
two different machines and use an older version of Mono on Linux. This
is I volunteer to be the release manager.

Things that need to get done before creating the release:

* decide on the version. I propose to use for the next release
  for all artifacts and try getting the "informational version" right -
  this is Dominik's second proposal in https://lists.apache.org/thread.html/42a97e0190fde4d5c54700965624c35158569b85cba48facea5ed70f@%3Clog4net-dev.logging.apache.org%3E

* add a nuspec file and integrate creating the nuget package with the
  build process

* go through the docs and add .NET Core where appropriate. In particular
  the matrix where we show which appender is available for which
  platform needs to get adjusted.

* actually build a release candidate.
  Personally I'd build the nuget package and make it available for the
  VOTE process but not publish it to nuget until the VOTE has passed -
  just like the Java projects only publish the final artifacts to Maven

* more testing - I'd encourage everybody to build the part they are
  interested in from source and try them out

I'd postpone the ASP.NET logging provider until after the release, in
particular as I feel uneasy with accepting PR #32 without a signed CLA.

Am I missing anything? Any other comments?



View raw message