This is an automated email from the ASF dual-hosted git repository.
FreeAndNil pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git
The following commit(s) were added to refs/heads/master by this push:
new 14d8742b updated releasing.md
14d8742b is described below
commit 14d8742b3c39ecff842be2dd999ca622d3950c67
Author: Jan Friedrich <[email protected]>
AuthorDate: Sun Apr 19 21:47:56 2026 +0200
updated releasing.md
---
doc/RELEASING.md | 41 +++++++++++++++++++----------------------
1 file changed, 19 insertions(+), 22 deletions(-)
diff --git a/doc/RELEASING.md b/doc/RELEASING.md
index ddb4f49d..6f1eac4d 100644
--- a/doc/RELEASING.md
+++ b/doc/RELEASING.md
@@ -32,33 +32,30 @@ release version 3.2.1:
- check out the `asf-staging` branch
- create a folder which includes the version, eg `log4net-3.2.1`
4. Copy the contents of `target/site` from this repo into the folder created
in (4)
- - remember to either update or link in sdk docs from a prior release
5. Update the symlinks in the base of the docs repo, ie:
- 3.2.x -> 3.2.1
- 3.x -> 3.2.1
-6. update the `doap_log4net.rdf` to point to the new release
-7. update the `.htaccess` file
+6. update the `.htaccess` file
- the trailing RewriteRule should point to the new log4net-3.2.1 folder
-8. push the `asf-staging` branch to github and wait a bit
+7. push the `asf-staging` branch to github and wait a bit
- after a minute or two, check the updates at
https://logging.staged.apache.org/log4net
- - are you seeing the correct releases page?
- - download links should (at this point) not work
-9. create an rc-releasd at GitHub with a tag like `rc/3.2.1-rc1`
+ - are you seeing the correct release notes page?
+8. create an rc-release at GitHub with the tag created by build-release.ps1
like `rc/3.2.1-rc1`
- attach all the files from the build/artifacts folder, _including
signatures_
-10. get the artifacts in build/artifacts up to
https://downloads.apache.org/logging/log4net/
- - `svn co https://dist.apache.org/repos/dist/dev/logging -N
apache-dist-logging-dev`
- - `cd apache-dist-logging-dev`
- - `svn up log4net`
- - `svn delete *`
- - `mkdir 3.2.1`
- - copy all artifacts to the new folder
+9. get the artifacts in build/artifacts up to
https://downloads.apache.org/logging/log4net/
+ - `svn co https://dist.apache.org/repos/dist/dev/logging -N
apache-dist-logging-dev`
+ - `cd apache-dist-logging-dev`
+ - `svn up log4net`
+ - `svn delete *`
+ - `mkdir 3.2.1`
+ - copy all artifacts to the new folder
- `svn add *`
- `svn commit -m 'log4net 3.2.1'`
- check https://dist.apache.org/repos/dist/dev/logging/log4net/3.2.1/
-11. raise a vote on the log4net mailing list ([email protected]) - see
MailTemplate.txt
-12. wait
-13. when the vote has 3 or more +1's, it's time to go live!
-14. copy the apache artifacts (binary and source) to the release svn repo and
commit
+10. raise a vote on the log4net mailing list ([email protected]) - see
MailTemplate.txt
+11. wait
+12. when the vote has 3 or more +1's, it's time to go live!
+13. copy the apache artifacts (binary and source) to the release svn repo and
commit
- `svn co https://dist.apache.org/repos/dist/release/logging -N
apache-dist-logging-release`
- `cd apache-dist-logging-release`
- `svn up log4net`
@@ -66,13 +63,13 @@ release version 3.2.1:
- copy all artifacts to the new folder
- `svn add *`
- `svn commit`
-15. push the .nupkg to nuget.org
+14. push the .nupkg to nuget.org
- via `dotnet`: `dotnet nuget push <path to package> -s nuget.org -k <your
nuget api key>`
- via `nuget`: `nuget push <path to package> -Source nuget.org -ApiKey
<your nuget api key>`
-16. don't forget to make the docs live: in the logging-log4net-site folder:
+15. don't forget to make the docs live: in the logging-log4net-site folder:
- `git checkout asf-site`
- `git pull --rebase`
- `git merge asf-staging`
-17. rename the release at github, eg to `rel/3.2.1`
+16. rename the release at github, eg to `rel/3.2.1`
- double-check that the `rel` tag is created
-18. apply the next version by calling `./scripts/update-version.ps1 3.2.1
3.2.2`
\ No newline at end of file
+17. apply the next version by calling `./scripts/update-version.ps1 3.2.1
3.2.2`
\ No newline at end of file
