+1
I validated the signatures and hashes. I also don’t have a .NET environment so
didn’t build or test.
Ralph
> On Jul 25, 2022, at 12:52 AM, Davyd McColl
> wrote:
>
> Hi all
>
> It's been a while, but I've finally tied together some work in a 2.0.15
> release for log4net. An rc tag is up
+1 from me - signatures and checksums look good. I didn't validate
anything else as I don't use .NET.
Note: You may want to not zip up the target/ directory, since that is
only for maven.
-Robert Middleton
On Fri, Jul 29, 2022 at 6:26 PM Ralph Goers wrote:
>
> But I just looked at
But I just looked at dist/release/log4net and the artifacts are there. This
means you have already released the artifacts publicly despite the vote having
not completed. You cannot really remove them as they propagate to mirrors
fairly quickly.
You need to create a confluence page with the
But never mind. Now that I look I see that dist/dev/log4net has a binaries and
sources directory. I am used to the way log4j does it where they are together.
So they are there.
Ralph
> On Jul 29, 2022, at 3:20 PM, Ralph Goers wrote:
>
> You publish to dist/dev for the vote. We review it
You publish to dist/dev for the vote. We review it there. You then move it to
dist/release after the vote passes. You obviously will not see them there - or
publicly in the downloads until they are moved to the release directory when
the vote passes.
The ASF requires the source zip be in the
It is on GitHub (both in git and zip at the release), but having checked out
the svn repo at https://dist.apache.org/repos/dist/release/logging/ on this
machine, I don't see the 2.0.15 artifacts that I added the other day, and that
comes back to my question about them not showing up in the d/l
I don't understand? There is an update at the staging site? What am I missing?
-d
On Jul 29 2022, at 10:37 pm, Ralph Goers wrote:
> Also, is the web site being updated for the release. While not required for a
> release we usually have a web site to review with a release.
>
> Ralph
> > On Jul
Also, is the web site being updated for the release. While not required for a
release we usually have a web site to review with a release.
Ralph
> On Jul 29, 2022, at 1:36 PM, Ralph Goers wrote:
>
> Where is the zip of the source? The ASF releases source code. Binaries are
> for the user’s
Where is the zip of the source? The ASF releases source code. Binaries are for
the user’s convenience.
Ralph
> On Jul 26, 2022, at 6:25 PM, Robert Middleton wrote:
>
> The binaries won't show up under downloads.apache.org until actually
> released(e.g. under
The binaries won't show up under downloads.apache.org until actually
released(e.g. under repos/dist/release/logging/log4net). That can of
course only happen after the release is done via this vote.
I'll take a look at it in a bit just to validate that the signatures
are good, as I know nothing
Hi all
It's been a while, but I've finally tied together some work in a 2.0.15 release
for log4net. An rc tag is up at GitHub with details:
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.15-rc1
I've pushed docs to staging as well as binaries to
11 matches
Mail list logo
