See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
-- Forwarded message -
From: NuGet Gallery
Date: Fri, Sep 18, 2020, 12:10
Subject: [NuGet Gallery] Message for owners of
hm, that's not great ): I'll investigate. Thanks for letting me know!
-d
On 2020/09/18 13:05:58, Dominik Psenner wrote:
See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
-- For
Ok, I've found the culprit -- there's a lot of assembly version sources which
mention 2.0.9 -- and I'm not entirely sure why some of them are in this project
(AssemblyVersionInfo.cpp, AssemblyVersionInfo.js, AssemblyVersionInfo.vb). And
there are two files which set up assembly version informati
Hi all
I have another potential release available: 2.0.11, tagged as rc/2.0.11
Changes are really minor:
- fixed assembly versioning (all assemblies should report 2.0.11.0 as their
version now)
- properly dispose of StreamWriters within logging appenders (thanks to
@NicholasNoise)
Binaries are
Hi all
I have another potential release available: 2.0.11, tagged as rc/2.0.11
Changes are really minor:
- fixed assembly versioning (all assemblies should report 2.0.11.0 as their
version now)
- properly dispose of StreamWriters within logging appenders (thanks to
@NicholasNoise)
Binaries are
Perhaps we can start by filtering which dependency updates to propose? I’d
think that maven plugins and test dependencies could be good to stay
updated with (JUnit and Mockito for example have more releases than we do).
On Fri, Sep 18, 2020 at 01:16 Ralph Goers
wrote:
> To be honest, I rarely up
Do you have links to the release artifacts? The download page links to
the live site which doesn't have the artifacts yet since they're not
released yet. :)
On Fri, 18 Sep 2020 at 09:05, Davyd McColl wrote:
>
> Hi all
>
> I have another potential release available: 2.0.11, tagged as rc/2.0.11
>
>
Hi Matt
Release artifacts are available on the GitHub release page
(https://GitHub.com/Apache/logging-log4net/releases) - expand the assets
list if it's collapsed.
I'll need someone to upload them to the downloads source as I think I don't
have access to do so (if I'm wrong, I'd love to be c
Oh sorry, I didn't notice that you uploaded them there (wasn't even
aware that it was possible to be honest).
On Fri, 18 Sep 2020 at 14:43, Davyd McColl wrote:
>
> Hi Matt
>
> Release artifacts are available on the GitHub release page
> (https://GitHub.com/Apache/logging-log4net/releases) - expan
How about your gpg key? I don't think we've imported that to the KEYS
file as far as I can tell?
On Fri, 18 Sep 2020 at 15:53, Matt Sicker wrote:
>
> Oh sorry, I didn't notice that you uploaded them there (wasn't even
> aware that it was possible to be honest).
>
> On Fri, 18 Sep 2020 at 14:43, D
+1 remko
On Sat, Sep 19, 2020 at 5:56 AM Matt Sicker wrote:
> How about your gpg key? I don't think we've imported that to the KEYS
> file as far as I can tell?
>
> On Fri, 18 Sep 2020 at 15:53, Matt Sicker wrote:
> >
> > Oh sorry, I didn't notice that you uploaded them there (wasn't even
> > a
If you upload your key to your GitHub profile, that also makes it
simple to find. For example, just add ".gpg" to your profile URL:
https://github.com/fluffynuts.gpg
On Fri, 18 Sep 2020 at 16:08, Remko Popma wrote:
>
> +1 remko
>
> On Sat, Sep 19, 2020 at 5:56 AM Matt Sicker wrote:
>
> > How abo
I've been working on smart pointer updates for log4cxx, and as part of that
effort I would also like to improve the documentation to make sure that it
is clear how to use the library. However, this brings up a question as to
how we want to create the website. Currently, the main site is generated
The main web site is built using JBake. Although it is Java based and still
uses Maven the command to build the site is just mvn install (although it
doesn’t actually do an install). All the web pages are either Markdown or
AsciiDoctor. I should also add that you don’t have to use Maven. You ca
I’d say go for whichever format is most natural for the toolset and
maintenance. I’m not tied to Maven site generation either.
On Fri, Sep 18, 2020 at 21:17 Ralph Goers
wrote:
> The main web site is built using JBake. Although it is Java based and
> still uses Maven the command to build the site
Hi Matt
Ralph mentioned last time that my key had been incorporated and that I
should sign myself (which I did), but I like the idea of making it easily
available at GitHub too. I'll do that when I get a moment.
-d
On September 18, 2020 23:11:48 Matt Sicker wrote:
If you upload your key
16 matches
Mail list logo
