This is an automated email from the ASF dual-hosted git repository.
freeandnil pushed a change to branch
Feature/111-Dropping-support-for-older-runtimes
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git
discard 80cc9a2a #111 Dropping support for older runtimes - added release
notes for 3.0.0
add d565df42 :wrench: upgrade update-version-info task and zarro
add 2f9666e2 :bookmark: update versioning to 2.0.16.0
add 66891fdd :bug: should delete old site before asking mvn to make a new
one
add 77f01660 :fire: remove changelog item - it's not done yet!
add 52ea9008 #111 Dropping support for older runtimes - added release
notes for 3.0.0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (80cc9a2a)
\
N -- N -- N
refs/heads/Feature/111-Dropping-support-for-older-runtimes (52ea9008)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.gitignore | 2 +
local-tasks/build-site.js | 53 +++++++++++-----------
...date-version-info.js => update-version-info.ts} | 25 +++++-----
log4net.build | 2 +-
log4net.shfbproj | 2 +-
package-lock.json | 36 +++++++++++----
package.json | 8 ++--
pom.xml | 2 +-
src/log4net/AssemblyInfo.cs | 46 +++++++++----------
src/log4net/AssemblyVersionInfo.cs | 4 +-
src/site/xdoc/release/release-notes.xml | 3 --
11 files changed, 103 insertions(+), 80 deletions(-)
rename local-tasks/{update-version-info.js => update-version-info.ts} (81%)
