You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2020/09/02 03:20:34 UTC
Re: [VOTE] Release Log4Net 2.0.9
I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release.
Ralph
> On Aug 24, 2020, at 3:27 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated.
>
> Ralph
>
>> On Aug 24, 2020, at 2:45 PM, Remko Popma <re...@gmail.com> wrote:
>>
>> Well done, everyone!
>>
>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker <bo...@gmail.com> wrote:
>>
>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>> developers happy. :D
>>>
>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl <da...@gmail.com> wrote:
>>>
>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>>
>>>>
>>>>
>>>> Thanks for all the help (:
>>>>
>>>>
>>>>
>>>> -d
>>>>
>>>>
>>>>
>>>> On 2020/08/23 19:13:36, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>> Yes, please go ahead and finish the release. The PMC approved this
>>>>
>>>> during our release vote. :)
>>>>
>>>>
>>>>
>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>>>>
>>>>>
>>>>
>>>>> There can’t be. That is what the release vote was for.
>>>>
>>>>>
>>>>
>>>>> Ralph
>>>>
>>>>>
>>>>
>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>>>>
>>>>>>
>>>>
>>>>>> Thanks Dominik
>>>>
>>>>>>
>>>>
>>>>>> Are there any objections to me pushing the 2.0.9 package that had
>>> been
>>>> approved and uploaded to https://downloads.apache.org/logging/log4net/
>>> to
>>>> nuget.org?
>>>>
>>>>>>
>>>>
>>>>>> -d
>>>>
>>>>>>
>>>>
>>>>>>
>>>>
>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
>>>>
>>>>>>>
>>>>
>>>>>>> Davyd, I added you as a collaborator. This should grant you the
>>>> privilege
>>>>
>>>>>>> to manage packages. You can now submit new and update or unlist
>>>> existing
>>>>
>>>>>>> packages.
>>>>
>>>>>>>
>>>>
>>>>>>> It would be great to have at least one other member of the pmc
>>> listed
>>>> as
>>>>
>>>>>>> administrator. The following documents the matrix of permissions.
>>>> Note that
>>>>
>>>>>>> the amount of administrative tasks should be very limited:
>>>>
>>>>>>>
>>>>
>>>>>>>
>>>>
>>> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
>>>>
>>>>>>>
>>>>
>>>>>>> Cheers
>>>>
>>>>>>> --
>>>>
>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
>>>> find
>>>>
>>>>>>> them.
>>>>
>>>>>>>
>>>>
>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
>>>>
>>>>>>>>
>>>>
>>>>>>>> Oh ok, well, mine is davydm (:
>>>>
>>>>>>>>
>>>>
>>>>>>>> -d
>>>>
>>>>>>>>
>>>>
>>>>>>>>
>>>>
>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
>>>>
>>>>>>>>
>>>>
>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
>>>> username,
>>>>
>>>>>>>>> apologies.
>>>>
>>>>>>>>>
>>>>
>>>>>>>>> --
>>>>
>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
>>> to
>>>> find
>>>>
>>>>>>>>> them.
>>>>
>>>>>>>>>
>>>>
>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> I know I'm quite new, but I'm happy to push approved packages.
>>> My
>>>>
>>>>>>>>>> Microsoft
>>>>
>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>> -d
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>>> Hi
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> I recall that we were forced to transform the nuget account
>>>>
>>>>>>>>>> Apache.Logging (
>>>>
>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
>>> personal
>>>>
>>>>>>>> account
>>>>
>>>>>>>>>> into
>>>>
>>>>>>>>>>> an organization. I am currently the only member and
>>>> administrator of
>>>>
>>>>>>>> that
>>>>
>>>>>>>>>>> organization. Please share with me (may also be in private)
>>> the
>>>> nuget
>>>>
>>>>>>>>>>> account (most probably the email of your microsoft account) if
>>>> you
>>>>
>>>>>>>> want
>>>>
>>>>>>>>>> me
>>>>
>>>>>>>>>>> to add you to the organization. Any member of the pmc may also
>>>> become
>>>>
>>>>>>>>>>> administrator of that group if he wishes to.
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> While I try to process your requests as fast as possible,
>>>> please give
>>>>
>>>>>>>> me
>>>>
>>>>>>>>>>> some days. I am at the beach with the family and tend to swim
>>>> and
>>>>
>>>>>>>> dive in
>>>>
>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> Best regards
>>>>
>>>>>>>>>>> Dominik
>>>>
>>>>>>>>>>> --
>>>>
>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>> happens
>>>> to
>>>>
>>>>>>>> find
>>>>
>>>>>>>>>>> them.
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
>>>>
>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org <
>>>>
>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a work
>>> or
>>>>
>>>>>>>> school
>>>>
>>>>>>>>>>>> email.
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
>>>>
>>>>>>>> ralph.goers@dslextreme.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>> This gets better and better. I was able to decrypt the file
>>>> but the
>>>>
>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
>>>>
>>>>>>>>>>>> “NuGet.org password login in no longer
>>>>
>>>>>>>> supported.
>>>>
>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
>>>>
>>>>>>>> ralph.goers@dslextreme.com
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
>>> same
>>>>
>>>>>>>> problem
>>>>
>>>>>>>>>> in
>>>>
>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
>>>> instructions have
>>>>
>>>>>>>>>>>> changed.
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
>>>>
>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>> I figured out that the document is now at
>>> home.apache.org
>>>> <
>>>>
>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
>>>> any good.
>>>>
>>>>>>>>>> gpg
>>>>
>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
>>>> surprising
>>>>
>>>>>>>>>> since
>>>>
>>>>>>>>>>>> my key wasn’t used to sign the document.
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
>>>>
>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> Dominik,
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> The README file says that the keys can be found at
>>>>
>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
>>>>
>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>. That
>>>> url
>>>>
>>>>>>>>>> returns
>>>>
>>>>>>>>>>>> a 404. Any idea where it moved to?
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
>>>>
>>>>>>>> dpsenner@gmail.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
>>> private
>>>>
>>>>>>>> repos of
>>>>
>>>>>>>>>>>> logging
>>>>
>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
>>>> recipients
>>>>
>>>>>>>>>> with
>>>>
>>>>>>>>>>>> their
>>>>
>>>>>>>>>>>>>>>>> gpg key.
>>>>
>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>>>
>>>>>>>> happens to
>>>>
>>>>>>>>>>>> find
>>>>
>>>>>>>>>>>>>>>>> them.
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
>>>>
>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> Great!
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
>>>> final step
>>>>
>>>>>>>>>> that
>>>>
>>>>>>>>>>>> most
>>>>
>>>>>>>>>>>>>>>>>> users are going to be interested in.
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
>>>> ideas on
>>>>
>>>>>>>>>> how
>>>>
>>>>>>>>>>>> to
>>>>
>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
>>>> that area,
>>>>
>>>>>>>>>> I'm
>>>>
>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
>>>> changes to
>>>>
>>>>>>>> the
>>>>
>>>>>>>>>>>> Release
>>>>
>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
>>> into a
>>>>
>>>>>>>> release,
>>>>
>>>>>>>>>>>> would a
>>>>
>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> -d
>>>>
>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
>>> long
>>>> we
>>>>
>>>>>>>> should
>>>>
>>>>>>>>>>>> wait
>>>>
>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I see
>>>> updated
>>>>
>>>>>>>>>>>>>>>>>> artifacts on
>>>> https://downloads.apache.org/logging/log4net/
>>>>
>>>>>>>> other
>>>>
>>>>>>>>>>>> than
>>>>
>>>>>>>>>>>>>>>>>> the release notes.
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>> +1 to that!
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
>>> the
>>>> web
>>>>
>>>>>>>> site
>>>>
>>>>>>>>>> to
>>>>
>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
>>>> all
>>>>
>>>>>>>> changes
>>>>
>>>>>>>>>>>> you
>>>>
>>>>>>>>>>>>>>>>>> have
>>>>
>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
>>> future
>>>>
>>>>>>>> releases
>>>>
>>>>>>>>>>>> for the
>>>>
>>>>>>>>>>>>>>>>>> next
>>>>
>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
>>>> than it
>>>>
>>>>>>>>>> needs
>>>>
>>>>>>>>>>>> to be
>>>>
>>>>>>>>>>>>>>>>>> (:
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>> -d
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
>>>> into the
>>>>
>>>>>>>>>>>> binaries
>>>>
>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include "apache"
>>>> in the
>>>>
>>>>>>>>>> name.
>>>>
>>>>>>>>>>>> I've
>>>>
>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the KEYS
>>>> file
>>>>
>>>>>>>> for
>>>>
>>>>>>>>>>>> log4net,
>>>>
>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
>>> with
>>>> the
>>>>
>>>>>>>>>>>> project-wide
>>>>
>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
>>>> outdated
>>>>
>>>>>>>>>>>> README.html in
>>>>
>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
>>>> notes, but
>>>>
>>>>>>>> we
>>>>
>>>>>>>>>> can
>>>>
>>>>>>>>>>>>>>>>>>>>>> address that next.
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
>>>> can
>>>>
>>>>>>>> address
>>>>
>>>>>>>>>>>> before
>>>>
>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
>>>> zip is
>>>>
>>>>>>>>>>>> missing the
>>>>
>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
>>>> way to
>>>>
>>>>>>>>>>>> include that
>>>>
>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
>>>> metadata, it
>>>>
>>>>>>>>>>>> explicitly
>>>>
>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
>>>> members.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release signing
>>>>
>>>>>>>>>> afterwards as
>>>>
>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>>>>> suggests.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this? It
>>>> has
>>>>
>>>>>>>> been
>>>>
>>>>>>>>>> more
>>>>
>>>>>>>>>>>>>>>>>> than 72
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
>>> bear
>>>> with
>>>>
>>>>>>>> me
>>>>
>>>>>>>>>> if I
>>>>
>>>>>>>>>>>>>>>>>> fluff it:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
>>>> 2.0.9
>>>>
>>>>>>>> from
>>>>
>>>>>>>>>> PR
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>> https://github.com/apache/logging-log4net/pull/61
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
>>> are
>>>> at:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>
>>>>
>>> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
>>>>
>>>>>>>>>>>>>>>>>> tag rel/
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream, but
>>>> this
>>>>
>>>>>>>> tag
>>>>
>>>>>>>>>> is
>>>>
>>>>>>>>>>>>>>>>>> exactly the
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
>>>> above,
>>>>
>>>>>>>> which
>>>>
>>>>>>>>>>>> was
>>>>
>>>>>>>>>>>>>>>>>>>>>>> accepted into
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
>>> everyone
>>>> is ok
>>>>
>>>>>>>>>> with
>>>>
>>>>>>>>>>>>>>>>>> what's there,
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to publish
>>>> to
>>>>
>>>>>>>> nuget
>>>>
>>>>>>>>>> do
>>>>
>>>>>>>>>>>> so.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
>>>> like to
>>>>
>>>>>>>>>>>> tackle the
>>>>
>>>>>>>>>>>>>>>>>> CVE that
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
>>>> once --
>>>>
>>>>>>>> it's
>>>>
>>>>>>>>>> a
>>>>
>>>>>>>>>>>>>>>>>> simple change
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
>>>> branch
>>>>
>>>>>>>> some
>>>>
>>>>>>>>>> time
>>>>
>>>>>>>>>>>>>>>>>> ago, so
>>>>
>>>>>>>>>>>>>>>>>>>>>>> there
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
>>>> release
>>>>
>>>>>>>>>> pronto,
>>>>
>>>>>>>>>>>> with
>>>>
>>>>>>>>>>>>>>>>>> only
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
>>> else
>>>> was
>>>>
>>>>>>>>>> already
>>>>
>>>>>>>>>>>>>>>>>> solved in
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
>>> perhaps
>>>> close
>>>>
>>>>>>>> out
>>>>
>>>>>>>>>>>> that
>>>>
>>>>>>>>>>>>>>>>>> branch to
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>
>>>>
>>>>>
>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Matt Sicker
>>>>
>>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>
>
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Davyd McColl <da...@gmail.com>.
Thanks
-d
On September 5, 2020 21:16:23 Ralph Goers <ra...@dslextreme.com> wrote:
> The changes looked good to me so I went ahead and merged them to the
> asf-site branch so now they are on the live site.
>
> Ralph
>
>> On Sep 4, 2020, at 11:51 PM, Davyd McColl <da...@gmail.com> wrote:
>>
>> Hi Ralph
>>
>> Sorry for wasting your time. I stupidly fixed up some of the the site in
>> the SVN tree last time, and then re-generated before commiting to the
>> github site, so it was still in a 1/2 state and I guess I was looking at
>> the wrong thing in my browser when I checked ):
>>
>> I've updated again and validated that the *2.0.9* links point at the right
>> place; pushed to asf-staging & checked on
>> http://logging.staged.apache.org/log4net.
>>
>> -d
>> On 2020/09/05 08:12:19, Ralph Goers <ra...@dslextreme.com> wrote:
>> OK, I’ve looked at http://logging.staged.apache.org/log4net. The download
>> page still doesn’t look correct. The heading still says 2.0.8 although the
>> source zip is 2.0.9 as it should be. The binary artifacts display as 2.0.8
>> but the links point to 2.0.9. Log4j controls all of this with a variable in
>> the pom.xml file.
>>
>> Ralph
>>
>>
>>> On Sep 2, 2020, at 11:01 PM, Davyd McColl wrote:
>>>
>>> Ralph, I've updated apache/logging-log4net-site#asf-staging with the latest
>>> build artifacts from the apache/logging-log4net repo, please validate when
>>> you have time.
>>>
>>> Matt, I don't think I have access to push binary artifacts -- and, if I do,
>>> I don't know where (I'm quite sure Ralph did that for me last time, tho
>>> I'll need to understand better at some point so as to be less of a PITA);
>>> at least I understand now that the SVN repo for the logging site is
>>> deprecated and the new place I should be putting generated site material is
>>> as above (apache/logging-log4net-site#asf-staging)
>>>
>>> -d
>>>
>>>
>>> On 2020/09/02 17:01:15, Matt Sicker wrote:
>>> Subversion is still used for publishing release artifacts. The
>>> previous Subversion-based system for publishing the website itself has
>>> been migrated to git. Without using git-lfs, I don't see us migrating
>>> from svn to git for release distribution for quite some time (svn
>>> seems better suited for archiving binary files like that).
>>>
>>
>>
>
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Ralph Goers <ra...@dslextreme.com>.
The changes looked good to me so I went ahead and merged them to the asf-site branch so now they are on the live site.
Ralph
> On Sep 4, 2020, at 11:51 PM, Davyd McColl <da...@gmail.com> wrote:
>
> Hi Ralph
>
> Sorry for wasting your time. I stupidly fixed up some of the the site in the SVN tree last time, and then re-generated before commiting to the github site, so it was still in a 1/2 state and I guess I was looking at the wrong thing in my browser when I checked ):
>
> I've updated again and validated that the *2.0.9* links point at the right place; pushed to asf-staging & checked on http://logging.staged.apache.org/log4net.
>
> -d
> On 2020/09/05 08:12:19, Ralph Goers <ra...@dslextreme.com> wrote:
> OK, I’ve looked at http://logging.staged.apache.org/log4net. The download page still doesn’t look correct. The heading still says 2.0.8 although the source zip is 2.0.9 as it should be. The binary artifacts display as 2.0.8 but the links point to 2.0.9. Log4j controls all of this with a variable in the pom.xml file.
>
> Ralph
>
>
>> On Sep 2, 2020, at 11:01 PM, Davyd McColl wrote:
>>
>> Ralph, I've updated apache/logging-log4net-site#asf-staging with the latest build artifacts from the apache/logging-log4net repo, please validate when you have time.
>>
>> Matt, I don't think I have access to push binary artifacts -- and, if I do, I don't know where (I'm quite sure Ralph did that for me last time, tho I'll need to understand better at some point so as to be less of a PITA); at least I understand now that the SVN repo for the logging site is deprecated and the new place I should be putting generated site material is as above (apache/logging-log4net-site#asf-staging)
>>
>> -d
>>
>>
>> On 2020/09/02 17:01:15, Matt Sicker wrote:
>> Subversion is still used for publishing release artifacts. The
>> previous Subversion-based system for publishing the website itself has
>> been migrated to git. Without using git-lfs, I don't see us migrating
>> from svn to git for release distribution for quite some time (svn
>> seems better suited for archiving binary files like that).
>>
>
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Davyd McColl <da...@gmail.com>.
Hi Ralph
Sorry for wasting your time. I stupidly fixed up some of the the site in the SVN tree last time, and then re-generated before commiting to the github site, so it was still in a 1/2 state and I guess I was looking at the wrong thing in my browser when I checked ):
I've updated again and validated that the *2.0.9* links point at the right place; pushed to asf-staging & checked on http://logging.staged.apache.org/log4net.
-d
On 2020/09/05 08:12:19, Ralph Goers <ra...@dslextreme.com> wrote:
OK, I’ve looked at http://logging.staged.apache.org/log4net. The download page still doesn’t look correct. The heading still says 2.0.8 although the source zip is 2.0.9 as it should be. The binary artifacts display as 2.0.8 but the links point to 2.0.9. Log4j controls all of this with a variable in the pom.xml file.
Ralph
> On Sep 2, 2020, at 11:01 PM, Davyd McColl wrote:
>
> Ralph, I've updated apache/logging-log4net-site#asf-staging with the latest build artifacts from the apache/logging-log4net repo, please validate when you have time.
>
> Matt, I don't think I have access to push binary artifacts -- and, if I do, I don't know where (I'm quite sure Ralph did that for me last time, tho I'll need to understand better at some point so as to be less of a PITA); at least I understand now that the SVN repo for the logging site is deprecated and the new place I should be putting generated site material is as above (apache/logging-log4net-site#asf-staging)
>
> -d
>
>
> On 2020/09/02 17:01:15, Matt Sicker wrote:
> Subversion is still used for publishing release artifacts. The
> previous Subversion-based system for publishing the website itself has
> been migrated to git. Without using git-lfs, I don't see us migrating
> from svn to git for release distribution for quite some time (svn
> seems better suited for archiving binary files like that).
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Ralph Goers <ra...@dslextreme.com>.
OK, I’ve looked at http://logging.staged.apache.org/log4net. The download page still doesn’t look correct. The heading still says 2.0.8 although the source zip is 2.0.9 as it should be. The binary artifacts display as 2.0.8 but the links point to 2.0.9. Log4j controls all of this with a variable in the pom.xml file.
Ralph
> On Sep 2, 2020, at 11:01 PM, Davyd McColl <da...@gmail.com> wrote:
>
> Ralph, I've updated apache/logging-log4net-site#asf-staging with the latest build artifacts from the apache/logging-log4net repo, please validate when you have time.
>
> Matt, I don't think I have access to push binary artifacts -- and, if I do, I don't know where (I'm quite sure Ralph did that for me last time, tho I'll need to understand better at some point so as to be less of a PITA); at least I understand now that the SVN repo for the logging site is deprecated and the new place I should be putting generated site material is as above (apache/logging-log4net-site#asf-staging)
>
> -d
>
>
> On 2020/09/02 17:01:15, Matt Sicker <bo...@gmail.com> wrote:
> Subversion is still used for publishing release artifacts. The
> previous Subversion-based system for publishing the website itself has
> been migrated to git. Without using git-lfs, I don't see us migrating
> from svn to git for release distribution for quite some time (svn
> seems better suited for archiving binary files like that).
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Matt Sicker <bo...@gmail.com>.
The release repository is only writable by PMC members. You won’t have to
worry about that until then. :)
On Thu, Sep 3, 2020 at 01:01 Davyd McColl <da...@gmail.com> wrote:
> Ralph, I've updated apache/logging-log4net-site#asf-staging with the
> latest build artifacts from the apache/logging-log4net repo, please
> validate when you have time.
>
>
>
> Matt, I don't think I have access to push binary artifacts -- and, if I
> do, I don't know where (I'm quite sure Ralph did that for me last time, tho
> I'll need to understand better at some point so as to be less of a PITA);
> at least I understand now that the SVN repo for the logging site is
> deprecated and the new place I should be putting generated site material is
> as above (apache/logging-log4net-site#asf-staging)
>
>
>
> -d
>
>
>
>
>
> On 2020/09/02 17:01:15, Matt Sicker <bo...@gmail.com> wrote:
>
> Subversion is still used for publishing release artifacts. The
>
> previous Subversion-based system for publishing the website itself has
>
> been migrated to git. Without using git-lfs, I don't see us migrating
>
> from svn to git for release distribution for quite some time (svn
>
> seems better suited for archiving binary files like that).
>
>
>
> On Wed, 2 Sep 2020 at 04:17, Davyd McColl wrote:
>
> >
>
> > I'm not following ):
>
> >
>
> > Previously, when I updated SVN, you said that it wasn't the way to do it.
>
> >
>
> > Is there a doc somewhere that someone new like me can follow for this?
> I'm just wasting your time here.
>
> >
>
> > -d
>
> > On 2020/09/02 09:34:23, Apache wrote:
>
> > Unfortunately the staging and release locations for the release
> artifacts are still using s not. But everything else is now in git. So in a
> release you should publish the web site to the asf-staging branch of the
> site repo and publish the artifacts to the dev location of the SVN dist
> repo. Once they are approved they can be published. You should have
> permission to publish the web site already.
>
> >
>
> > I will try to verify your changes tomorrow.
>
> >
>
> > Ralph
>
> >
>
> > > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote:
>
> > >
>
> > > Hi Ralph
>
> > >
>
> > > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and
> obviously forgot to push with tags ):
>
> > >
>
> > > I've updated the source files for the site:
>
> > > - removed the mirror references
>
> > > - updated the links for 2.0.9
>
> > > - updated the link to point to the html instead of the cgi
>
> > >
>
> > > I've also updated the README in the project to take out the dormant
> status commentary.
>
> > >
>
> > > Please review & update the live site if you're happy.
>
> > >
>
> > > Previously, as I understand it, the point of the SVN staging area was
> to provide built artifacts for the website. Since that's not in play any
> more, I was wondering how that's going to happen now? Someone will have to
> build before pushing. If you'd like, I could add the target folder that is
> built into git so that it's just a matter of copying files.
>
> > >
>
> > > I've also added an npm script around building the site, which checks
> if you have maven available & builds if possible -- perhaps this makes it
> easier for the next new person (:
>
> > >
>
> > > -d
>
> > >
>
> > > On 2020/09/02 05:20:50, Ralph Goers wrote:
>
> > > I also just noticed that the git repo has no tag to represent 2.0.9.
> Without a tag essentially there is no release.
>
> > >
>
> > > Ralph
>
> > >
>
> > >> On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote:
>
> > >>
>
> > >> The release isn’t done yet. The web site still reflects 2.0.8.
> Release announcements can’t be sent out until that is updated.
>
> > >>
>
> > >> Ralph
>
> > >>
>
> > >>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
>
> > >>>
>
> > >>> Well done, everyone!
>
> > >>>
>
> > >>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>
> > >>>
>
> > >>>> Thanks again for managing the release! I’m sure you’ve just made a
> lot of
>
> > >>>> developers happy. :D
>
> > >>>>
>
> > >>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>
> > >>>>
>
> > >>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>> Thanks for all the help (:
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>> -d
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>> On 2020/08/23 19:13:36, Matt Sicker wrote:
>
> > >>>>>
>
> > >>>>> Yes, please go ahead and finish the release. The PMC approved this
>
> > >>>>>
>
> > >>>>> during our release vote. :)
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>
> > >>>>>
>
> > >>>>>>
>
> > >>>>>
>
> > >>>>>> There can’t be. That is what the release vote was for.
>
> > >>>>>
>
> > >>>>>>
>
> > >>>>>
>
> > >>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>
>
> > >>>>>
>
> > >>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>
> > >>>>>
>
> > >>>>>>>
>
> > >>>>>
>
> > >>>>>>> Thanks Dominik
>
> > >>>>>
>
> > >>>>>>>
>
> > >>>>>
>
> > >>>>>>> Are there any objections to me pushing the 2.0.9 package that had
>
> > >>>> been
>
> > >>>>> approved and uploaded to
> https://downloads.apache.org/logging/log4net/
>
> > >>>> to
>
> > >>>>> nuget.org?
>
> > >>>>>
>
> > >>>>>>>
>
> > >>>>>
>
> > >>>>>>> -d
>
> > >>>>>
>
> > >>>>>>>
>
> > >>>>>
>
> > >>>>>>>
>
> > >>>>>
>
> > >>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
>
> > >>>>>
>
> > >>>>>>>>
>
> > >>>>>
>
> > >>>>>>>> Davyd, I added you as a collaborator. This should grant you the
>
> > >>>>> privilege
>
> > >>>>>
>
> > >>>>>>>> to manage packages. You can now submit new and update or unlist
>
> > >>>>> existing
>
> > >>>>>
>
> > >>>>>>>> packages.
>
> > >>>>>
>
> > >>>>>>>>
>
> > >>>>>
>
> > >>>>>>>> It would be great to have at least one other member of the pmc
>
> > >>>> listed
>
> > >>>>> as
>
> > >>>>>
>
> > >>>>>>>> administrator. The following documents the matrix of
> permissions.
>
> > >>>>> Note that
>
> > >>>>>
>
> > >>>>>>>> the amount of administrative tasks should be very limited:
>
> > >>>>>
>
> > >>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>
>
> > >>>>>
>
> > >>>>
> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
>
> > >>>>>
>
> > >>>>>>>>
>
> > >>>>>
>
> > >>>>>>>> Cheers
>
> > >>>>>
>
> > >>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
> to
>
> > >>>>> find
>
> > >>>>>
>
> > >>>>>>>> them.
>
> > >>>>>
>
> > >>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>> Oh ok, well, mine is davydm (:
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>> -d
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
>
> > >>>>> username,
>
> > >>>>>
>
> > >>>>>>>>>> apologies.
>
> > >>>>>
>
> > >>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
> happens
>
> > >>>> to
>
> > >>>>> find
>
> > >>>>>
>
> > >>>>>>>>>> them.
>
> > >>>>>
>
> > >>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
>
> > >>>>>
>
> > >>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>> I know I'm quite new, but I'm happy to push approved
> packages.
>
> > >>>> My
>
> > >>>>>
>
> > >>>>>>>>>>> Microsoft
>
> > >>>>>
>
> > >>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>> -d
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>> Hi
>
> > >>>>>
>
> > >>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>> I recall that we were forced to transform the nuget account
>
> > >>>>>
>
> > >>>>>>>>>>> Apache.Logging (
>
> > >>>>>
>
> > >>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
>
> > >>>> personal
>
> > >>>>>
>
> > >>>>>>>>> account
>
> > >>>>>
>
> > >>>>>>>>>>> into
>
> > >>>>>
>
> > >>>>>>>>>>>> an organization. I am currently the only member and
>
> > >>>>> administrator of
>
> > >>>>>
>
> > >>>>>>>>> that
>
> > >>>>>
>
> > >>>>>>>>>>>> organization. Please share with me (may also be in private)
>
> > >>>> the
>
> > >>>>> nuget
>
> > >>>>>
>
> > >>>>>>>>>>>> account (most probably the email of your microsoft account)
> if
>
> > >>>>> you
>
> > >>>>>
>
> > >>>>>>>>> want
>
> > >>>>>
>
> > >>>>>>>>>>> me
>
> > >>>>>
>
> > >>>>>>>>>>>> to add you to the organization. Any member of the pmc may
> also
>
> > >>>>> become
>
> > >>>>>
>
> > >>>>>>>>>>>> administrator of that group if he wishes to.
>
> > >>>>>
>
> > >>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>> While I try to process your requests as fast as possible,
>
> > >>>>> please give
>
> > >>>>>
>
> > >>>>>>>>> me
>
> > >>>>>
>
> > >>>>>>>>>>>> some days. I am at the beach with the family and tend to
> swim
>
> > >>>>> and
>
> > >>>>>
>
> > >>>>>>>>> dive in
>
> > >>>>>
>
> > >>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
>
> > >>>>>
>
> > >>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>> Best regards
>
> > >>>>>
>
> > >>>>>>>>>>>> Dominik
>
> > >>>>>
>
> > >>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>
> > >>>> happens
>
> > >>>>> to
>
> > >>>>>
>
> > >>>>>>>>> find
>
> > >>>>>
>
> > >>>>>>>>>>>> them.
>
> > >>>>>
>
> > >>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
>
> > >>>>>
>
> > >>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org
> <
>
> > >>>>>
>
> > >>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a
> work
>
> > >>>> or
>
> > >>>>>
>
> > >>>>>>>>> school
>
> > >>>>>
>
> > >>>>>>>>>>>>> email.
>
> > >>>>>
>
> > >>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
>
> > >>>>>
>
> > >>>>>>>>> ralph.goers@dslextreme.com>
>
> > >>>>>
>
> > >>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>> This gets better and better. I was able to decrypt the
> file
>
> > >>>>> but the
>
> > >>>>>
>
> > >>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
>
> > >>>>>
>
> > >>>>>>>>>>>>> “NuGet.org password login in no longer
>
> > >>>>>
>
> > >>>>>>>>> supported.
>
> > >>>>>
>
> > >>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
>
> > >>>>>
>
> > >>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
>
> > >>>>>
>
> > >>>>>>>>> ralph.goers@dslextreme.com
>
> > >>>>>
>
> > >>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
>
> > >>>> same
>
> > >>>>>
>
> > >>>>>>>>> problem
>
> > >>>>>
>
> > >>>>>>>>>>> in
>
> > >>>>>
>
> > >>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
>
> > >>>>> instructions have
>
> > >>>>>
>
> > >>>>>>>>>>>>> changed.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
>
> > >>>>>
>
> > >>>>>>>>>>> ralph.goers@dslextreme.com>
>
> > >>>>>
>
> > >>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>> I figured out that the document is now at
>
> > >>>> home.apache.org
>
> > >>>>> <
>
> > >>>>>
>
> > >>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
>
> > >>>>> any good.
>
> > >>>>>
>
> > >>>>>>>>>>> gpg
>
> > >>>>>
>
> > >>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
>
> > >>>>> surprising
>
> > >>>>>
>
> > >>>>>>>>>>> since
>
> > >>>>>
>
> > >>>>>>>>>>>>> my key wasn’t used to sign the document.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
>
> > >>>>>
>
> > >>>>>>>>>>> ralph.goers@dslextreme.com>
>
> > >>>>>
>
> > >>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>> Dominik,
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>> The README file says that the keys can be found at
>
> > >>>>>
>
> > >>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
>
> > >>>>>
>
> > >>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>.
> That
>
> > >>>>> url
>
> > >>>>>
>
> > >>>>>>>>>>> returns
>
> > >>>>>
>
> > >>>>>>>>>>>>> a 404. Any idea where it moved to?
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
>
> > >>>>>
>
> > >>>>>>>>> dpsenner@gmail.com>
>
> > >>>>>
>
> > >>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
>
> > >>>> private
>
> > >>>>>
>
> > >>>>>>>>> repos of
>
> > >>>>>
>
> > >>>>>>>>>>>>> logging
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
>
> > >>>>> recipients
>
> > >>>>>
>
> > >>>>>>>>>>> with
>
> > >>>>>
>
> > >>>>>>>>>>>>> their
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> gpg key.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone
> who
>
> > >>>>>
>
> > >>>>>>>>> happens to
>
> > >>>>>
>
> > >>>>>>>>>>>>> find
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> them.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
>
> > >>>>>
>
> > >>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> Great!
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
>
> > >>>>> final step
>
> > >>>>>
>
> > >>>>>>>>>>> that
>
> > >>>>>
>
> > >>>>>>>>>>>>> most
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> users are going to be interested in.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
>
> > >>>>> ideas on
>
> > >>>>>
>
> > >>>>>>>>>>> how
>
> > >>>>>
>
> > >>>>>>>>>>>>> to
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
>
> > >>>>> that area,
>
> > >>>>>
>
> > >>>>>>>>>>> I'm
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
>
> > >>>>> changes to
>
> > >>>>>
>
> > >>>>>>>>> the
>
> > >>>>>
>
> > >>>>>>>>>>>>> Release
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
>
> > >>>> into a
>
> > >>>>>
>
> > >>>>>>>>> release,
>
> > >>>>>
>
> > >>>>>>>>>>>>> would a
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> -d
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
>
> > >>>> long
>
> > >>>>> we
>
> > >>>>>
>
> > >>>>>>>>> should
>
> > >>>>>
>
> > >>>>>>>>>>>>> wait
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I
> see
>
> > >>>>> updated
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> artifacts on
>
> > >>>>> https://downloads.apache.org/logging/log4net/
>
> > >>>>>
>
> > >>>>>>>>> other
>
> > >>>>>
>
> > >>>>>>>>>>>>> than
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> the release notes.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>> +1 to that!
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
>
> > >>>> the
>
> > >>>>> web
>
> > >>>>>
>
> > >>>>>>>>> site
>
> > >>>>>
>
> > >>>>>>>>>>> to
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
>
> > >>>>> all
>
> > >>>>>
>
> > >>>>>>>>> changes
>
> > >>>>>
>
> > >>>>>>>>>>>>> you
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> have
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
>
> > >>>> future
>
> > >>>>>
>
> > >>>>>>>>> releases
>
> > >>>>>
>
> > >>>>>>>>>>>>> for the
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> next
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
>
> > >>>>> than it
>
> > >>>>>
>
> > >>>>>>>>>>> needs
>
> > >>>>>
>
> > >>>>>>>>>>>>> to be
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> (:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>> -d
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
>
> > >>>>> into the
>
> > >>>>>
>
> > >>>>>>>>>>>>> binaries
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include
> "apache"
>
> > >>>>> in the
>
> > >>>>>
>
> > >>>>>>>>>>> name.
>
> > >>>>>
>
> > >>>>>>>>>>>>> I've
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the
> KEYS
>
> > >>>>> file
>
> > >>>>>
>
> > >>>>>>>>> for
>
> > >>>>>
>
> > >>>>>>>>>>>>> log4net,
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
>
> > >>>> with
>
> > >>>>> the
>
> > >>>>>
>
> > >>>>>>>>>>>>> project-wide
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
>
> > >>>>> outdated
>
> > >>>>>
>
> > >>>>>>>>>>>>> README.html in
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
>
> > >>>>> notes, but
>
> > >>>>>
>
> > >>>>>>>>> we
>
> > >>>>>
>
> > >>>>>>>>>>> can
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> address that next.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
>
> > >>>>> can
>
> > >>>>>
>
> > >>>>>>>>> address
>
> > >>>>>
>
> > >>>>>>>>>>>>> before
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
>
> > >>>>> zip is
>
> > >>>>>
>
> > >>>>>>>>>>>>> missing the
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
>
> > >>>>> way to
>
> > >>>>>
>
> > >>>>>>>>>>>>> include that
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
>
> > >>>>> metadata, it
>
> > >>>>>
>
> > >>>>>>>>>>>>> explicitly
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
>
> > >>>>> members.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma
> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
>
> > >>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release
> signing
>
> > >>>>>
>
> > >>>>>>>>>>> afterwards as
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> suggests.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this?
> It
>
> > >>>>> has
>
> > >>>>>
>
> > >>>>>>>>> been
>
> > >>>>>
>
> > >>>>>>>>>>> more
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> than 72
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
>
> > >>>> bear
>
> > >>>>> with
>
> > >>>>>
>
> > >>>>>>>>> me
>
> > >>>>>
>
> > >>>>>>>>>>> if I
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> fluff it:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
>
> > >>>>> 2.0.9
>
> > >>>>>
>
> > >>>>>>>>> from
>
> > >>>>>
>
> > >>>>>>>>>>> PR
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>> https://github.com/apache/logging-log4net/pull/61
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
>
> > >>>> are
>
> > >>>>> at:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>
> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>
>
> > >>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> tag rel/
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream,
> but
>
> > >>>>> this
>
> > >>>>>
>
> > >>>>>>>>> tag
>
> > >>>>>
>
> > >>>>>>>>>>> is
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> exactly the
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
>
> > >>>>> above,
>
> > >>>>>
>
> > >>>>>>>>> which
>
> > >>>>>
>
> > >>>>>>>>>>>>> was
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> accepted into
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
>
> > >>>> everyone
>
> > >>>>> is ok
>
> > >>>>>
>
> > >>>>>>>>>>> with
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> what's there,
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to
> publish
>
> > >>>>> to
>
> > >>>>>
>
> > >>>>>>>>> nuget
>
> > >>>>>
>
> > >>>>>>>>>>> do
>
> > >>>>>
>
> > >>>>>>>>>>>>> so.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
>
> > >>>>> like to
>
> > >>>>>
>
> > >>>>>>>>>>>>> tackle the
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> CVE that
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
>
> > >>>>> once --
>
> > >>>>>
>
> > >>>>>>>>> it's
>
> > >>>>>
>
> > >>>>>>>>>>> a
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> simple change
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
>
> > >>>>> branch
>
> > >>>>>
>
> > >>>>>>>>> some
>
> > >>>>>
>
> > >>>>>>>>>>> time
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> ago, so
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> there
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
>
> > >>>>> release
>
> > >>>>>
>
> > >>>>>>>>>>> pronto,
>
> > >>>>>
>
> > >>>>>>>>>>>>> with
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> only
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
>
> > >>>> else
>
> > >>>>> was
>
> > >>>>>
>
> > >>>>>>>>>>> already
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> solved in
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
>
> > >>>> perhaps
>
> > >>>>> close
>
> > >>>>>
>
> > >>>>>>>>> out
>
> > >>>>>
>
> > >>>>>>>>>>>>> that
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> branch to
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> --
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>>>
>
> > >>>>>
>
> > >>>>>>>>>
>
> > >>>>>
>
> > >>>>>>
>
> > >>>>>
>
> > >>>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>>
>
> > >>>>> --
>
> > >>>>>
>
> > >>>>> Matt Sicker
>
> > >>>>>
>
> > >>>>> --
>
> > >>>> Matt Sicker
>
> > >>>>
>
> > >>
>
> > >>
>
> > >>
>
> > >
>
> > >
>
> >
>
> >
>
>
>
>
>
> --
>
> Matt Sicker
>
> --
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Davyd McColl <da...@gmail.com>.
Ralph, I've updated apache/logging-log4net-site#asf-staging with the latest build artifacts from the apache/logging-log4net repo, please validate when you have time.
Matt, I don't think I have access to push binary artifacts -- and, if I do, I don't know where (I'm quite sure Ralph did that for me last time, tho I'll need to understand better at some point so as to be less of a PITA); at least I understand now that the SVN repo for the logging site is deprecated and the new place I should be putting generated site material is as above (apache/logging-log4net-site#asf-staging)
-d
On 2020/09/02 17:01:15, Matt Sicker <bo...@gmail.com> wrote:
Subversion is still used for publishing release artifacts. The
previous Subversion-based system for publishing the website itself has
been migrated to git. Without using git-lfs, I don't see us migrating
from svn to git for release distribution for quite some time (svn
seems better suited for archiving binary files like that).
On Wed, 2 Sep 2020 at 04:17, Davyd McColl wrote:
>
> I'm not following ):
>
> Previously, when I updated SVN, you said that it wasn't the way to do it.
>
> Is there a doc somewhere that someone new like me can follow for this? I'm just wasting your time here.
>
> -d
> On 2020/09/02 09:34:23, Apache wrote:
> Unfortunately the staging and release locations for the release artifacts are still using s not. But everything else is now in git. So in a release you should publish the web site to the asf-staging branch of the site repo and publish the artifacts to the dev location of the SVN dist repo. Once they are approved they can be published. You should have permission to publish the web site already.
>
> I will try to verify your changes tomorrow.
>
> Ralph
>
> > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote:
> >
> > Hi Ralph
> >
> > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously forgot to push with tags ):
> >
> > I've updated the source files for the site:
> > - removed the mirror references
> > - updated the links for 2.0.9
> > - updated the link to point to the html instead of the cgi
> >
> > I've also updated the README in the project to take out the dormant status commentary.
> >
> > Please review & update the live site if you're happy.
> >
> > Previously, as I understand it, the point of the SVN staging area was to provide built artifacts for the website. Since that's not in play any more, I was wondering how that's going to happen now? Someone will have to build before pushing. If you'd like, I could add the target folder that is built into git so that it's just a matter of copying files.
> >
> > I've also added an npm script around building the site, which checks if you have maven available & builds if possible -- perhaps this makes it easier for the next new person (:
> >
> > -d
> >
> > On 2020/09/02 05:20:50, Ralph Goers wrote:
> > I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release.
> >
> > Ralph
> >
> >> On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote:
> >>
> >> The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated.
> >>
> >> Ralph
> >>
> >>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
> >>>
> >>> Well done, everyone!
> >>>
> >>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
> >>>
> >>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
> >>>> developers happy. :D
> >>>>
> >>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
> >>>>
> >>>>> Ok, log4net 2.0.9 is up on nuget.org (:
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks for all the help (:
> >>>>>
> >>>>>
> >>>>>
> >>>>> -d
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 2020/08/23 19:13:36, Matt Sicker wrote:
> >>>>>
> >>>>> Yes, please go ahead and finish the release. The PMC approved this
> >>>>>
> >>>>> during our release vote. :)
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
> >>>>>
> >>>>>>
> >>>>>
> >>>>>> There can’t be. That is what the release vote was for.
> >>>>>
> >>>>>>
> >>>>>
> >>>>>> Ralph
> >>>>>
> >>>>>>
> >>>>>
> >>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>> Thanks Dominik
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>> Are there any objections to me pushing the 2.0.9 package that had
> >>>> been
> >>>>> approved and uploaded to https://downloads.apache.org/logging/log4net/
> >>>> to
> >>>>> nuget.org?
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>> -d
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>> Davyd, I added you as a collaborator. This should grant you the
> >>>>> privilege
> >>>>>
> >>>>>>>> to manage packages. You can now submit new and update or unlist
> >>>>> existing
> >>>>>
> >>>>>>>> packages.
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>> It would be great to have at least one other member of the pmc
> >>>> listed
> >>>>> as
> >>>>>
> >>>>>>>> administrator. The following documents the matrix of permissions.
> >>>>> Note that
> >>>>>
> >>>>>>>> the amount of administrative tasks should be very limited:
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>>
> >>>>>
> >>>> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>> Cheers
> >>>>>
> >>>>>>>> --
> >>>>>
> >>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
> >>>>> find
> >>>>>
> >>>>>>>> them.
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>> Oh ok, well, mine is davydm (:
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>> -d
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
> >>>>> username,
> >>>>>
> >>>>>>>>>> apologies.
> >>>>>
> >>>>>>>>>>
> >>>>>
> >>>>>>>>>> --
> >>>>>
> >>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
> >>>> to
> >>>>> find
> >>>>>
> >>>>>>>>>> them.
> >>>>>
> >>>>>>>>>>
> >>>>>
> >>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
> >>>>>
> >>>>>>>>>>
> >>>>>
> >>>>>>>>>>> I know I'm quite new, but I'm happy to push approved packages.
> >>>> My
> >>>>>
> >>>>>>>>>>> Microsoft
> >>>>>
> >>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> Hi
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> I recall that we were forced to transform the nuget account
> >>>>>
> >>>>>>>>>>> Apache.Logging (
> >>>>>
> >>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
> >>>> personal
> >>>>>
> >>>>>>>>> account
> >>>>>
> >>>>>>>>>>> into
> >>>>>
> >>>>>>>>>>>> an organization. I am currently the only member and
> >>>>> administrator of
> >>>>>
> >>>>>>>>> that
> >>>>>
> >>>>>>>>>>>> organization. Please share with me (may also be in private)
> >>>> the
> >>>>> nuget
> >>>>>
> >>>>>>>>>>>> account (most probably the email of your microsoft account) if
> >>>>> you
> >>>>>
> >>>>>>>>> want
> >>>>>
> >>>>>>>>>>> me
> >>>>>
> >>>>>>>>>>>> to add you to the organization. Any member of the pmc may also
> >>>>> become
> >>>>>
> >>>>>>>>>>>> administrator of that group if he wishes to.
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> While I try to process your requests as fast as possible,
> >>>>> please give
> >>>>>
> >>>>>>>>> me
> >>>>>
> >>>>>>>>>>>> some days. I am at the beach with the family and tend to swim
> >>>>> and
> >>>>>
> >>>>>>>>> dive in
> >>>>>
> >>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> Best regards
> >>>>>
> >>>>>>>>>>>> Dominik
> >>>>>
> >>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
> >>>> happens
> >>>>> to
> >>>>>
> >>>>>>>>> find
> >>>>>
> >>>>>>>>>>>> them.
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
> >>>>>
> >>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org <
> >>>>>
> >>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a work
> >>>> or
> >>>>>
> >>>>>>>>> school
> >>>>>
> >>>>>>>>>>>>> email.
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
> >>>>>
> >>>>>>>>> ralph.goers@dslextreme.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>> This gets better and better. I was able to decrypt the file
> >>>>> but the
> >>>>>
> >>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
> >>>>>
> >>>>>>>>>>>>> “NuGet.org password login in no longer
> >>>>>
> >>>>>>>>> supported.
> >>>>>
> >>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
> >>>>>
> >>>>>>>>> ralph.goers@dslextreme.com
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
> >>>> same
> >>>>>
> >>>>>>>>> problem
> >>>>>
> >>>>>>>>>>> in
> >>>>>
> >>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
> >>>>> instructions have
> >>>>>
> >>>>>>>>>>>>> changed.
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
> >>>>>
> >>>>>>>>>>> ralph.goers@dslextreme.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>> I figured out that the document is now at
> >>>> home.apache.org
> >>>>> <
> >>>>>
> >>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
> >>>>> any good.
> >>>>>
> >>>>>>>>>>> gpg
> >>>>>
> >>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
> >>>>> surprising
> >>>>>
> >>>>>>>>>>> since
> >>>>>
> >>>>>>>>>>>>> my key wasn’t used to sign the document.
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
> >>>>>
> >>>>>>>>>>> ralph.goers@dslextreme.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> Dominik,
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> The README file says that the keys can be found at
> >>>>>
> >>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
> >>>>>
> >>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>. That
> >>>>> url
> >>>>>
> >>>>>>>>>>> returns
> >>>>>
> >>>>>>>>>>>>> a 404. Any idea where it moved to?
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
> >>>>>
> >>>>>>>>> dpsenner@gmail.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
> >>>> private
> >>>>>
> >>>>>>>>> repos of
> >>>>>
> >>>>>>>>>>>>> logging
> >>>>>
> >>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
> >>>>> recipients
> >>>>>
> >>>>>>>>>>> with
> >>>>>
> >>>>>>>>>>>>> their
> >>>>>
> >>>>>>>>>>>>>>>>>> gpg key.
> >>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
> >>>>>
> >>>>>>>>> happens to
> >>>>>
> >>>>>>>>>>>>> find
> >>>>>
> >>>>>>>>>>>>>>>>>> them.
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
> >>>>>
> >>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> Great!
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
> >>>>> final step
> >>>>>
> >>>>>>>>>>> that
> >>>>>
> >>>>>>>>>>>>> most
> >>>>>
> >>>>>>>>>>>>>>>>>>> users are going to be interested in.
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
> >>>>> ideas on
> >>>>>
> >>>>>>>>>>> how
> >>>>>
> >>>>>>>>>>>>> to
> >>>>>
> >>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
> >>>>> that area,
> >>>>>
> >>>>>>>>>>> I'm
> >>>>>
> >>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
> >>>>> changes to
> >>>>>
> >>>>>>>>> the
> >>>>>
> >>>>>>>>>>>>> Release
> >>>>>
> >>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
> >>>> into a
> >>>>>
> >>>>>>>>> release,
> >>>>>
> >>>>>>>>>>>>> would a
> >>>>>
> >>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
> >>>> long
> >>>>> we
> >>>>>
> >>>>>>>>> should
> >>>>>
> >>>>>>>>>>>>> wait
> >>>>>
> >>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I see
> >>>>> updated
> >>>>>
> >>>>>>>>>>>>>>>>>>> artifacts on
> >>>>> https://downloads.apache.org/logging/log4net/
> >>>>>
> >>>>>>>>> other
> >>>>>
> >>>>>>>>>>>>> than
> >>>>>
> >>>>>>>>>>>>>>>>>>> the release notes.
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>> +1 to that!
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
> >>>> the
> >>>>> web
> >>>>>
> >>>>>>>>> site
> >>>>>
> >>>>>>>>>>> to
> >>>>>
> >>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
> >>>>> all
> >>>>>
> >>>>>>>>> changes
> >>>>>
> >>>>>>>>>>>>> you
> >>>>>
> >>>>>>>>>>>>>>>>>>> have
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
> >>>> future
> >>>>>
> >>>>>>>>> releases
> >>>>>
> >>>>>>>>>>>>> for the
> >>>>>
> >>>>>>>>>>>>>>>>>>> next
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
> >>>>> than it
> >>>>>
> >>>>>>>>>>> needs
> >>>>>
> >>>>>>>>>>>>> to be
> >>>>>
> >>>>>>>>>>>>>>>>>>> (:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
> >>>>> into the
> >>>>>
> >>>>>>>>>>>>> binaries
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include "apache"
> >>>>> in the
> >>>>>
> >>>>>>>>>>> name.
> >>>>>
> >>>>>>>>>>>>> I've
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the KEYS
> >>>>> file
> >>>>>
> >>>>>>>>> for
> >>>>>
> >>>>>>>>>>>>> log4net,
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
> >>>> with
> >>>>> the
> >>>>>
> >>>>>>>>>>>>> project-wide
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
> >>>>> outdated
> >>>>>
> >>>>>>>>>>>>> README.html in
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
> >>>>> notes, but
> >>>>>
> >>>>>>>>> we
> >>>>>
> >>>>>>>>>>> can
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> address that next.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
> >>>>> can
> >>>>>
> >>>>>>>>> address
> >>>>>
> >>>>>>>>>>>>> before
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
> >>>>> zip is
> >>>>>
> >>>>>>>>>>>>> missing the
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
> >>>>> way to
> >>>>>
> >>>>>>>>>>>>> include that
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
> >>>>> metadata, it
> >>>>>
> >>>>>>>>>>>>> explicitly
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
> >>>>> members.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
> >>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release signing
> >>>>>
> >>>>>>>>>>> afterwards as
> >>>>>
> >>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> suggests.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this? It
> >>>>> has
> >>>>>
> >>>>>>>>> been
> >>>>>
> >>>>>>>>>>> more
> >>>>>
> >>>>>>>>>>>>>>>>>>> than 72
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
> >>>> bear
> >>>>> with
> >>>>>
> >>>>>>>>> me
> >>>>>
> >>>>>>>>>>> if I
> >>>>>
> >>>>>>>>>>>>>>>>>>> fluff it:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
> >>>>> 2.0.9
> >>>>>
> >>>>>>>>> from
> >>>>>
> >>>>>>>>>>> PR
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>> https://github.com/apache/logging-log4net/pull/61
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
> >>>> are
> >>>>> at:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
> >>>>>
> >>>>>>>>>>>>>>>>>>> tag rel/
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream, but
> >>>>> this
> >>>>>
> >>>>>>>>> tag
> >>>>>
> >>>>>>>>>>> is
> >>>>>
> >>>>>>>>>>>>>>>>>>> exactly the
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
> >>>>> above,
> >>>>>
> >>>>>>>>> which
> >>>>>
> >>>>>>>>>>>>> was
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> accepted into
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
> >>>> everyone
> >>>>> is ok
> >>>>>
> >>>>>>>>>>> with
> >>>>>
> >>>>>>>>>>>>>>>>>>> what's there,
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to publish
> >>>>> to
> >>>>>
> >>>>>>>>> nuget
> >>>>>
> >>>>>>>>>>> do
> >>>>>
> >>>>>>>>>>>>> so.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
> >>>>> like to
> >>>>>
> >>>>>>>>>>>>> tackle the
> >>>>>
> >>>>>>>>>>>>>>>>>>> CVE that
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
> >>>>> once --
> >>>>>
> >>>>>>>>> it's
> >>>>>
> >>>>>>>>>>> a
> >>>>>
> >>>>>>>>>>>>>>>>>>> simple change
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
> >>>>> branch
> >>>>>
> >>>>>>>>> some
> >>>>>
> >>>>>>>>>>> time
> >>>>>
> >>>>>>>>>>>>>>>>>>> ago, so
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> there
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
> >>>>> release
> >>>>>
> >>>>>>>>>>> pronto,
> >>>>>
> >>>>>>>>>>>>> with
> >>>>>
> >>>>>>>>>>>>>>>>>>> only
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
> >>>> else
> >>>>> was
> >>>>>
> >>>>>>>>>>> already
> >>>>>
> >>>>>>>>>>>>>>>>>>> solved in
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
> >>>> perhaps
> >>>>> close
> >>>>>
> >>>>>>>>> out
> >>>>>
> >>>>>>>>>>>>> that
> >>>>>
> >>>>>>>>>>>>>>>>>>> branch to
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>
> >>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Matt Sicker
> >>>>>
> >>>>> --
> >>>> Matt Sicker
> >>>>
> >>
> >>
> >>
> >
> >
>
>
--
Matt Sicker
Re: [VOTE] Release Log4Net 2.0.9
Posted by Matt Sicker <bo...@gmail.com>.
Subversion is still used for publishing release artifacts. The
previous Subversion-based system for publishing the website itself has
been migrated to git. Without using git-lfs, I don't see us migrating
from svn to git for release distribution for quite some time (svn
seems better suited for archiving binary files like that).
On Wed, 2 Sep 2020 at 04:17, Davyd McColl <da...@gmail.com> wrote:
>
> I'm not following ):
>
> Previously, when I updated SVN, you said that it wasn't the way to do it.
>
> Is there a doc somewhere that someone new like me can follow for this? I'm just wasting your time here.
>
> -d
> On 2020/09/02 09:34:23, Apache <ra...@dslextreme.com> wrote:
> Unfortunately the staging and release locations for the release artifacts are still using s not. But everything else is now in git. So in a release you should publish the web site to the asf-staging branch of the site repo and publish the artifacts to the dev location of the SVN dist repo. Once they are approved they can be published. You should have permission to publish the web site already.
>
> I will try to verify your changes tomorrow.
>
> Ralph
>
> > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote:
> >
> > Hi Ralph
> >
> > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously forgot to push with tags ):
> >
> > I've updated the source files for the site:
> > - removed the mirror references
> > - updated the links for 2.0.9
> > - updated the link to point to the html instead of the cgi
> >
> > I've also updated the README in the project to take out the dormant status commentary.
> >
> > Please review & update the live site if you're happy.
> >
> > Previously, as I understand it, the point of the SVN staging area was to provide built artifacts for the website. Since that's not in play any more, I was wondering how that's going to happen now? Someone will have to build before pushing. If you'd like, I could add the target folder that is built into git so that it's just a matter of copying files.
> >
> > I've also added an npm script around building the site, which checks if you have maven available & builds if possible -- perhaps this makes it easier for the next new person (:
> >
> > -d
> >
> > On 2020/09/02 05:20:50, Ralph Goers wrote:
> > I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release.
> >
> > Ralph
> >
> >> On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote:
> >>
> >> The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated.
> >>
> >> Ralph
> >>
> >>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
> >>>
> >>> Well done, everyone!
> >>>
> >>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
> >>>
> >>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
> >>>> developers happy. :D
> >>>>
> >>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
> >>>>
> >>>>> Ok, log4net 2.0.9 is up on nuget.org (:
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks for all the help (:
> >>>>>
> >>>>>
> >>>>>
> >>>>> -d
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 2020/08/23 19:13:36, Matt Sicker wrote:
> >>>>>
> >>>>> Yes, please go ahead and finish the release. The PMC approved this
> >>>>>
> >>>>> during our release vote. :)
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
> >>>>>
> >>>>>>
> >>>>>
> >>>>>> There can’t be. That is what the release vote was for.
> >>>>>
> >>>>>>
> >>>>>
> >>>>>> Ralph
> >>>>>
> >>>>>>
> >>>>>
> >>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>> Thanks Dominik
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>> Are there any objections to me pushing the 2.0.9 package that had
> >>>> been
> >>>>> approved and uploaded to https://downloads.apache.org/logging/log4net/
> >>>> to
> >>>>> nuget.org?
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>> -d
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>>
> >>>>>
> >>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>> Davyd, I added you as a collaborator. This should grant you the
> >>>>> privilege
> >>>>>
> >>>>>>>> to manage packages. You can now submit new and update or unlist
> >>>>> existing
> >>>>>
> >>>>>>>> packages.
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>> It would be great to have at least one other member of the pmc
> >>>> listed
> >>>>> as
> >>>>>
> >>>>>>>> administrator. The following documents the matrix of permissions.
> >>>>> Note that
> >>>>>
> >>>>>>>> the amount of administrative tasks should be very limited:
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>>
> >>>>>
> >>>> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>> Cheers
> >>>>>
> >>>>>>>> --
> >>>>>
> >>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
> >>>>> find
> >>>>>
> >>>>>>>> them.
> >>>>>
> >>>>>>>>
> >>>>>
> >>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>> Oh ok, well, mine is davydm (:
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>> -d
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
> >>>>> username,
> >>>>>
> >>>>>>>>>> apologies.
> >>>>>
> >>>>>>>>>>
> >>>>>
> >>>>>>>>>> --
> >>>>>
> >>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
> >>>> to
> >>>>> find
> >>>>>
> >>>>>>>>>> them.
> >>>>>
> >>>>>>>>>>
> >>>>>
> >>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
> >>>>>
> >>>>>>>>>>
> >>>>>
> >>>>>>>>>>> I know I'm quite new, but I'm happy to push approved packages.
> >>>> My
> >>>>>
> >>>>>>>>>>> Microsoft
> >>>>>
> >>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> Hi
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> I recall that we were forced to transform the nuget account
> >>>>>
> >>>>>>>>>>> Apache.Logging (
> >>>>>
> >>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
> >>>> personal
> >>>>>
> >>>>>>>>> account
> >>>>>
> >>>>>>>>>>> into
> >>>>>
> >>>>>>>>>>>> an organization. I am currently the only member and
> >>>>> administrator of
> >>>>>
> >>>>>>>>> that
> >>>>>
> >>>>>>>>>>>> organization. Please share with me (may also be in private)
> >>>> the
> >>>>> nuget
> >>>>>
> >>>>>>>>>>>> account (most probably the email of your microsoft account) if
> >>>>> you
> >>>>>
> >>>>>>>>> want
> >>>>>
> >>>>>>>>>>> me
> >>>>>
> >>>>>>>>>>>> to add you to the organization. Any member of the pmc may also
> >>>>> become
> >>>>>
> >>>>>>>>>>>> administrator of that group if he wishes to.
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> While I try to process your requests as fast as possible,
> >>>>> please give
> >>>>>
> >>>>>>>>> me
> >>>>>
> >>>>>>>>>>>> some days. I am at the beach with the family and tend to swim
> >>>>> and
> >>>>>
> >>>>>>>>> dive in
> >>>>>
> >>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> Best regards
> >>>>>
> >>>>>>>>>>>> Dominik
> >>>>>
> >>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
> >>>> happens
> >>>>> to
> >>>>>
> >>>>>>>>> find
> >>>>>
> >>>>>>>>>>>> them.
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
> >>>>>
> >>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org <
> >>>>>
> >>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a work
> >>>> or
> >>>>>
> >>>>>>>>> school
> >>>>>
> >>>>>>>>>>>>> email.
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
> >>>>>
> >>>>>>>>> ralph.goers@dslextreme.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>> This gets better and better. I was able to decrypt the file
> >>>>> but the
> >>>>>
> >>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
> >>>>>
> >>>>>>>>>>>>> “NuGet.org password login in no longer
> >>>>>
> >>>>>>>>> supported.
> >>>>>
> >>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
> >>>>>
> >>>>>>>>> ralph.goers@dslextreme.com
> >>>>>
> >>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
> >>>> same
> >>>>>
> >>>>>>>>> problem
> >>>>>
> >>>>>>>>>>> in
> >>>>>
> >>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
> >>>>> instructions have
> >>>>>
> >>>>>>>>>>>>> changed.
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
> >>>>>
> >>>>>>>>>>> ralph.goers@dslextreme.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>> I figured out that the document is now at
> >>>> home.apache.org
> >>>>> <
> >>>>>
> >>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
> >>>>> any good.
> >>>>>
> >>>>>>>>>>> gpg
> >>>>>
> >>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
> >>>>> surprising
> >>>>>
> >>>>>>>>>>> since
> >>>>>
> >>>>>>>>>>>>> my key wasn’t used to sign the document.
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
> >>>>>
> >>>>>>>>>>> ralph.goers@dslextreme.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> Dominik,
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> The README file says that the keys can be found at
> >>>>>
> >>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
> >>>>>
> >>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>. That
> >>>>> url
> >>>>>
> >>>>>>>>>>> returns
> >>>>>
> >>>>>>>>>>>>> a 404. Any idea where it moved to?
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
> >>>>>
> >>>>>>>>> dpsenner@gmail.com>
> >>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
> >>>> private
> >>>>>
> >>>>>>>>> repos of
> >>>>>
> >>>>>>>>>>>>> logging
> >>>>>
> >>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
> >>>>> recipients
> >>>>>
> >>>>>>>>>>> with
> >>>>>
> >>>>>>>>>>>>> their
> >>>>>
> >>>>>>>>>>>>>>>>>> gpg key.
> >>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
> >>>>>
> >>>>>>>>> happens to
> >>>>>
> >>>>>>>>>>>>> find
> >>>>>
> >>>>>>>>>>>>>>>>>> them.
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
> >>>>>
> >>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> Great!
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
> >>>>> final step
> >>>>>
> >>>>>>>>>>> that
> >>>>>
> >>>>>>>>>>>>> most
> >>>>>
> >>>>>>>>>>>>>>>>>>> users are going to be interested in.
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
> >>>>> ideas on
> >>>>>
> >>>>>>>>>>> how
> >>>>>
> >>>>>>>>>>>>> to
> >>>>>
> >>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
> >>>>> that area,
> >>>>>
> >>>>>>>>>>> I'm
> >>>>>
> >>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
> >>>>> changes to
> >>>>>
> >>>>>>>>> the
> >>>>>
> >>>>>>>>>>>>> Release
> >>>>>
> >>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
> >>>> into a
> >>>>>
> >>>>>>>>> release,
> >>>>>
> >>>>>>>>>>>>> would a
> >>>>>
> >>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
> >>>> long
> >>>>> we
> >>>>>
> >>>>>>>>> should
> >>>>>
> >>>>>>>>>>>>> wait
> >>>>>
> >>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I see
> >>>>> updated
> >>>>>
> >>>>>>>>>>>>>>>>>>> artifacts on
> >>>>> https://downloads.apache.org/logging/log4net/
> >>>>>
> >>>>>>>>> other
> >>>>>
> >>>>>>>>>>>>> than
> >>>>>
> >>>>>>>>>>>>>>>>>>> the release notes.
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>> +1 to that!
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
> >>>> the
> >>>>> web
> >>>>>
> >>>>>>>>> site
> >>>>>
> >>>>>>>>>>> to
> >>>>>
> >>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
> >>>>> all
> >>>>>
> >>>>>>>>> changes
> >>>>>
> >>>>>>>>>>>>> you
> >>>>>
> >>>>>>>>>>>>>>>>>>> have
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
> >>>> future
> >>>>>
> >>>>>>>>> releases
> >>>>>
> >>>>>>>>>>>>> for the
> >>>>>
> >>>>>>>>>>>>>>>>>>> next
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
> >>>>> than it
> >>>>>
> >>>>>>>>>>> needs
> >>>>>
> >>>>>>>>>>>>> to be
> >>>>>
> >>>>>>>>>>>>>>>>>>> (:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
> >>>>> into the
> >>>>>
> >>>>>>>>>>>>> binaries
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include "apache"
> >>>>> in the
> >>>>>
> >>>>>>>>>>> name.
> >>>>>
> >>>>>>>>>>>>> I've
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the KEYS
> >>>>> file
> >>>>>
> >>>>>>>>> for
> >>>>>
> >>>>>>>>>>>>> log4net,
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
> >>>> with
> >>>>> the
> >>>>>
> >>>>>>>>>>>>> project-wide
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
> >>>>> outdated
> >>>>>
> >>>>>>>>>>>>> README.html in
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
> >>>>> notes, but
> >>>>>
> >>>>>>>>> we
> >>>>>
> >>>>>>>>>>> can
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> address that next.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
> >>>>> can
> >>>>>
> >>>>>>>>> address
> >>>>>
> >>>>>>>>>>>>> before
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
> >>>>> zip is
> >>>>>
> >>>>>>>>>>>>> missing the
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
> >>>>> way to
> >>>>>
> >>>>>>>>>>>>> include that
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
> >>>>> metadata, it
> >>>>>
> >>>>>>>>>>>>> explicitly
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
> >>>>> members.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
> >>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release signing
> >>>>>
> >>>>>>>>>>> afterwards as
> >>>>>
> >>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> suggests.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this? It
> >>>>> has
> >>>>>
> >>>>>>>>> been
> >>>>>
> >>>>>>>>>>> more
> >>>>>
> >>>>>>>>>>>>>>>>>>> than 72
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
> >>>> bear
> >>>>> with
> >>>>>
> >>>>>>>>> me
> >>>>>
> >>>>>>>>>>> if I
> >>>>>
> >>>>>>>>>>>>>>>>>>> fluff it:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
> >>>>> 2.0.9
> >>>>>
> >>>>>>>>> from
> >>>>>
> >>>>>>>>>>> PR
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>> https://github.com/apache/logging-log4net/pull/61
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
> >>>> are
> >>>>> at:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
> >>>>>
> >>>>>>>>>>>>>>>>>>> tag rel/
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream, but
> >>>>> this
> >>>>>
> >>>>>>>>> tag
> >>>>>
> >>>>>>>>>>> is
> >>>>>
> >>>>>>>>>>>>>>>>>>> exactly the
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
> >>>>> above,
> >>>>>
> >>>>>>>>> which
> >>>>>
> >>>>>>>>>>>>> was
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> accepted into
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
> >>>> everyone
> >>>>> is ok
> >>>>>
> >>>>>>>>>>> with
> >>>>>
> >>>>>>>>>>>>>>>>>>> what's there,
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to publish
> >>>>> to
> >>>>>
> >>>>>>>>> nuget
> >>>>>
> >>>>>>>>>>> do
> >>>>>
> >>>>>>>>>>>>> so.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
> >>>>> like to
> >>>>>
> >>>>>>>>>>>>> tackle the
> >>>>>
> >>>>>>>>>>>>>>>>>>> CVE that
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
> >>>>> once --
> >>>>>
> >>>>>>>>> it's
> >>>>>
> >>>>>>>>>>> a
> >>>>>
> >>>>>>>>>>>>>>>>>>> simple change
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
> >>>>> branch
> >>>>>
> >>>>>>>>> some
> >>>>>
> >>>>>>>>>>> time
> >>>>>
> >>>>>>>>>>>>>>>>>>> ago, so
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> there
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
> >>>>> release
> >>>>>
> >>>>>>>>>>> pronto,
> >>>>>
> >>>>>>>>>>>>> with
> >>>>>
> >>>>>>>>>>>>>>>>>>> only
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
> >>>> else
> >>>>> was
> >>>>>
> >>>>>>>>>>> already
> >>>>>
> >>>>>>>>>>>>>>>>>>> solved in
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
> >>>> perhaps
> >>>>> close
> >>>>>
> >>>>>>>>> out
> >>>>>
> >>>>>>>>>>>>> that
> >>>>>
> >>>>>>>>>>>>>>>>>>> branch to
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>>> --
> >>>>>
> >>>>>>>>>>>>>>>>>>> Matt Sicker
> >>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>>>
> >>>>>
> >>>>>>>>>>>
> >>>>>
> >>>>>>>>>
> >>>>>
> >>>>>>
> >>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Matt Sicker
> >>>>>
> >>>>> --
> >>>> Matt Sicker
> >>>>
> >>
> >>
> >>
> >
> >
>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Davyd McColl <da...@gmail.com>.
I'm not following ):
Previously, when I updated SVN, you said that it wasn't the way to do it.
Is there a doc somewhere that someone new like me can follow for this? I'm just wasting your time here.
-d
On 2020/09/02 09:34:23, Apache <ra...@dslextreme.com> wrote:
Unfortunately the staging and release locations for the release artifacts are still using s not. But everything else is now in git. So in a release you should publish the web site to the asf-staging branch of the site repo and publish the artifacts to the dev location of the SVN dist repo. Once they are approved they can be published. You should have permission to publish the web site already.
I will try to verify your changes tomorrow.
Ralph
> On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote:
>
> Hi Ralph
>
> The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously forgot to push with tags ):
>
> I've updated the source files for the site:
> - removed the mirror references
> - updated the links for 2.0.9
> - updated the link to point to the html instead of the cgi
>
> I've also updated the README in the project to take out the dormant status commentary.
>
> Please review & update the live site if you're happy.
>
> Previously, as I understand it, the point of the SVN staging area was to provide built artifacts for the website. Since that's not in play any more, I was wondering how that's going to happen now? Someone will have to build before pushing. If you'd like, I could add the target folder that is built into git so that it's just a matter of copying files.
>
> I've also added an npm script around building the site, which checks if you have maven available & builds if possible -- perhaps this makes it easier for the next new person (:
>
> -d
>
> On 2020/09/02 05:20:50, Ralph Goers wrote:
> I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release.
>
> Ralph
>
>> On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote:
>>
>> The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated.
>>
>> Ralph
>>
>>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
>>>
>>> Well done, everyone!
>>>
>>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>>
>>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>>> developers happy. :D
>>>>
>>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>>
>>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>>>
>>>>>
>>>>>
>>>>> Thanks for all the help (:
>>>>>
>>>>>
>>>>>
>>>>> -d
>>>>>
>>>>>
>>>>>
>>>>> On 2020/08/23 19:13:36, Matt Sicker wrote:
>>>>>
>>>>> Yes, please go ahead and finish the release. The PMC approved this
>>>>>
>>>>> during our release vote. :)
>>>>>
>>>>>
>>>>>
>>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>>>>>
>>>>>>
>>>>>
>>>>>> There can’t be. That is what the release vote was for.
>>>>>
>>>>>>
>>>>>
>>>>>> Ralph
>>>>>
>>>>>>
>>>>>
>>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>>>>>
>>>>>>>
>>>>>
>>>>>>> Thanks Dominik
>>>>>
>>>>>>>
>>>>>
>>>>>>> Are there any objections to me pushing the 2.0.9 package that had
>>>> been
>>>>> approved and uploaded to https://downloads.apache.org/logging/log4net/
>>>> to
>>>>> nuget.org?
>>>>>
>>>>>>>
>>>>>
>>>>>>> -d
>>>>>
>>>>>>>
>>>>>
>>>>>>>
>>>>>
>>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
>>>>>
>>>>>>>>
>>>>>
>>>>>>>> Davyd, I added you as a collaborator. This should grant you the
>>>>> privilege
>>>>>
>>>>>>>> to manage packages. You can now submit new and update or unlist
>>>>> existing
>>>>>
>>>>>>>> packages.
>>>>>
>>>>>>>>
>>>>>
>>>>>>>> It would be great to have at least one other member of the pmc
>>>> listed
>>>>> as
>>>>>
>>>>>>>> administrator. The following documents the matrix of permissions.
>>>>> Note that
>>>>>
>>>>>>>> the amount of administrative tasks should be very limited:
>>>>>
>>>>>>>>
>>>>>
>>>>>>>>
>>>>>
>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
>>>>>
>>>>>>>>
>>>>>
>>>>>>>> Cheers
>>>>>
>>>>>>>> --
>>>>>
>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
>>>>> find
>>>>>
>>>>>>>> them.
>>>>>
>>>>>>>>
>>>>>
>>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>> Oh ok, well, mine is davydm (:
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>> -d
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
>>>>> username,
>>>>>
>>>>>>>>>> apologies.
>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>> --
>>>>>
>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
>>>> to
>>>>> find
>>>>>
>>>>>>>>>> them.
>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> I know I'm quite new, but I'm happy to push approved packages.
>>>> My
>>>>>
>>>>>>>>>>> Microsoft
>>>>>
>>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> Hi
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> I recall that we were forced to transform the nuget account
>>>>>
>>>>>>>>>>> Apache.Logging (
>>>>>
>>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
>>>> personal
>>>>>
>>>>>>>>> account
>>>>>
>>>>>>>>>>> into
>>>>>
>>>>>>>>>>>> an organization. I am currently the only member and
>>>>> administrator of
>>>>>
>>>>>>>>> that
>>>>>
>>>>>>>>>>>> organization. Please share with me (may also be in private)
>>>> the
>>>>> nuget
>>>>>
>>>>>>>>>>>> account (most probably the email of your microsoft account) if
>>>>> you
>>>>>
>>>>>>>>> want
>>>>>
>>>>>>>>>>> me
>>>>>
>>>>>>>>>>>> to add you to the organization. Any member of the pmc may also
>>>>> become
>>>>>
>>>>>>>>>>>> administrator of that group if he wishes to.
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> While I try to process your requests as fast as possible,
>>>>> please give
>>>>>
>>>>>>>>> me
>>>>>
>>>>>>>>>>>> some days. I am at the beach with the family and tend to swim
>>>>> and
>>>>>
>>>>>>>>> dive in
>>>>>
>>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> Best regards
>>>>>
>>>>>>>>>>>> Dominik
>>>>>
>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>>> happens
>>>>> to
>>>>>
>>>>>>>>> find
>>>>>
>>>>>>>>>>>> them.
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
>>>>>
>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org <
>>>>>
>>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a work
>>>> or
>>>>>
>>>>>>>>> school
>>>>>
>>>>>>>>>>>>> email.
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
>>>>>
>>>>>>>>> ralph.goers@dslextreme.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>> This gets better and better. I was able to decrypt the file
>>>>> but the
>>>>>
>>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
>>>>>
>>>>>>>>>>>>> “NuGet.org password login in no longer
>>>>>
>>>>>>>>> supported.
>>>>>
>>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
>>>>>
>>>>>>>>> ralph.goers@dslextreme.com
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
>>>> same
>>>>>
>>>>>>>>> problem
>>>>>
>>>>>>>>>>> in
>>>>>
>>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
>>>>> instructions have
>>>>>
>>>>>>>>>>>>> changed.
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
>>>>>
>>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>> I figured out that the document is now at
>>>> home.apache.org
>>>>> <
>>>>>
>>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
>>>>> any good.
>>>>>
>>>>>>>>>>> gpg
>>>>>
>>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
>>>>> surprising
>>>>>
>>>>>>>>>>> since
>>>>>
>>>>>>>>>>>>> my key wasn’t used to sign the document.
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
>>>>>
>>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> Dominik,
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> The README file says that the keys can be found at
>>>>>
>>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
>>>>>
>>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>. That
>>>>> url
>>>>>
>>>>>>>>>>> returns
>>>>>
>>>>>>>>>>>>> a 404. Any idea where it moved to?
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
>>>>>
>>>>>>>>> dpsenner@gmail.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
>>>> private
>>>>>
>>>>>>>>> repos of
>>>>>
>>>>>>>>>>>>> logging
>>>>>
>>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
>>>>> recipients
>>>>>
>>>>>>>>>>> with
>>>>>
>>>>>>>>>>>>> their
>>>>>
>>>>>>>>>>>>>>>>>> gpg key.
>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>>>>
>>>>>>>>> happens to
>>>>>
>>>>>>>>>>>>> find
>>>>>
>>>>>>>>>>>>>>>>>> them.
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
>>>>>
>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> Great!
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
>>>>> final step
>>>>>
>>>>>>>>>>> that
>>>>>
>>>>>>>>>>>>> most
>>>>>
>>>>>>>>>>>>>>>>>>> users are going to be interested in.
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
>>>>> ideas on
>>>>>
>>>>>>>>>>> how
>>>>>
>>>>>>>>>>>>> to
>>>>>
>>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
>>>>> that area,
>>>>>
>>>>>>>>>>> I'm
>>>>>
>>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
>>>>> changes to
>>>>>
>>>>>>>>> the
>>>>>
>>>>>>>>>>>>> Release
>>>>>
>>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
>>>> into a
>>>>>
>>>>>>>>> release,
>>>>>
>>>>>>>>>>>>> would a
>>>>>
>>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
>>>> long
>>>>> we
>>>>>
>>>>>>>>> should
>>>>>
>>>>>>>>>>>>> wait
>>>>>
>>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I see
>>>>> updated
>>>>>
>>>>>>>>>>>>>>>>>>> artifacts on
>>>>> https://downloads.apache.org/logging/log4net/
>>>>>
>>>>>>>>> other
>>>>>
>>>>>>>>>>>>> than
>>>>>
>>>>>>>>>>>>>>>>>>> the release notes.
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>> +1 to that!
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
>>>> the
>>>>> web
>>>>>
>>>>>>>>> site
>>>>>
>>>>>>>>>>> to
>>>>>
>>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
>>>>> all
>>>>>
>>>>>>>>> changes
>>>>>
>>>>>>>>>>>>> you
>>>>>
>>>>>>>>>>>>>>>>>>> have
>>>>>
>>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
>>>> future
>>>>>
>>>>>>>>> releases
>>>>>
>>>>>>>>>>>>> for the
>>>>>
>>>>>>>>>>>>>>>>>>> next
>>>>>
>>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
>>>>> than it
>>>>>
>>>>>>>>>>> needs
>>>>>
>>>>>>>>>>>>> to be
>>>>>
>>>>>>>>>>>>>>>>>>> (:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
>>>>> into the
>>>>>
>>>>>>>>>>>>> binaries
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include "apache"
>>>>> in the
>>>>>
>>>>>>>>>>> name.
>>>>>
>>>>>>>>>>>>> I've
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the KEYS
>>>>> file
>>>>>
>>>>>>>>> for
>>>>>
>>>>>>>>>>>>> log4net,
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
>>>> with
>>>>> the
>>>>>
>>>>>>>>>>>>> project-wide
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
>>>>> outdated
>>>>>
>>>>>>>>>>>>> README.html in
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
>>>>> notes, but
>>>>>
>>>>>>>>> we
>>>>>
>>>>>>>>>>> can
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> address that next.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
>>>>> can
>>>>>
>>>>>>>>> address
>>>>>
>>>>>>>>>>>>> before
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
>>>>> zip is
>>>>>
>>>>>>>>>>>>> missing the
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
>>>>> way to
>>>>>
>>>>>>>>>>>>> include that
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
>>>>> metadata, it
>>>>>
>>>>>>>>>>>>> explicitly
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
>>>>> members.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release signing
>>>>>
>>>>>>>>>>> afterwards as
>>>>>
>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> suggests.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this? It
>>>>> has
>>>>>
>>>>>>>>> been
>>>>>
>>>>>>>>>>> more
>>>>>
>>>>>>>>>>>>>>>>>>> than 72
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
>>>> bear
>>>>> with
>>>>>
>>>>>>>>> me
>>>>>
>>>>>>>>>>> if I
>>>>>
>>>>>>>>>>>>>>>>>>> fluff it:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
>>>>> 2.0.9
>>>>>
>>>>>>>>> from
>>>>>
>>>>>>>>>>> PR
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>> https://github.com/apache/logging-log4net/pull/61
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
>>>> are
>>>>> at:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>
>>>>>
>>>> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
>>>>>
>>>>>>>>>>>>>>>>>>> tag rel/
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream, but
>>>>> this
>>>>>
>>>>>>>>> tag
>>>>>
>>>>>>>>>>> is
>>>>>
>>>>>>>>>>>>>>>>>>> exactly the
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
>>>>> above,
>>>>>
>>>>>>>>> which
>>>>>
>>>>>>>>>>>>> was
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> accepted into
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
>>>> everyone
>>>>> is ok
>>>>>
>>>>>>>>>>> with
>>>>>
>>>>>>>>>>>>>>>>>>> what's there,
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to publish
>>>>> to
>>>>>
>>>>>>>>> nuget
>>>>>
>>>>>>>>>>> do
>>>>>
>>>>>>>>>>>>> so.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
>>>>> like to
>>>>>
>>>>>>>>>>>>> tackle the
>>>>>
>>>>>>>>>>>>>>>>>>> CVE that
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
>>>>> once --
>>>>>
>>>>>>>>> it's
>>>>>
>>>>>>>>>>> a
>>>>>
>>>>>>>>>>>>>>>>>>> simple change
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
>>>>> branch
>>>>>
>>>>>>>>> some
>>>>>
>>>>>>>>>>> time
>>>>>
>>>>>>>>>>>>>>>>>>> ago, so
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> there
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
>>>>> release
>>>>>
>>>>>>>>>>> pronto,
>>>>>
>>>>>>>>>>>>> with
>>>>>
>>>>>>>>>>>>>>>>>>> only
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
>>>> else
>>>>> was
>>>>>
>>>>>>>>>>> already
>>>>>
>>>>>>>>>>>>>>>>>>> solved in
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
>>>> perhaps
>>>>> close
>>>>>
>>>>>>>>> out
>>>>>
>>>>>>>>>>>>> that
>>>>>
>>>>>>>>>>>>>>>>>>> branch to
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>
>>>>>
>>>>>>
>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Matt Sicker
>>>>>
>>>>> --
>>>> Matt Sicker
>>>>
>>
>>
>>
>
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Apache <ra...@dslextreme.com>.
Unfortunately the staging and release locations for the release artifacts are still using s not. But everything else is now in git. So in a release you should publish the web site to the asf-staging branch of the site repo and publish the artifacts to the dev location of the SVN dist repo. Once they are approved they can be published. You should have permission to publish the web site already.
I will try to verify your changes tomorrow.
Ralph
> On Sep 1, 2020, at 11:11 PM, Davyd McColl <da...@gmail.com> wrote:
>
> Hi Ralph
>
> The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously forgot to push with tags ):
>
> I've updated the source files for the site:
> - removed the mirror references
> - updated the links for 2.0.9
> - updated the link to point to the html instead of the cgi
>
> I've also updated the README in the project to take out the dormant status commentary.
>
> Please review & update the live site if you're happy.
>
> Previously, as I understand it, the point of the SVN staging area was to provide built artifacts for the website. Since that's not in play any more, I was wondering how that's going to happen now? Someone will have to build before pushing. If you'd like, I could add the target folder that is built into git so that it's just a matter of copying files.
>
> I've also added an npm script around building the site, which checks if you have maven available & builds if possible -- perhaps this makes it easier for the next new person (:
>
> -d
>
> On 2020/09/02 05:20:50, Ralph Goers <ra...@dslextreme.com> wrote:
> I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release.
>
> Ralph
>
>> On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote:
>>
>> The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated.
>>
>> Ralph
>>
>>>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
>>>
>>> Well done, everyone!
>>>
>>>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>>
>>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>>> developers happy. :D
>>>>
>>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>>
>>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>>>
>>>>>
>>>>>
>>>>> Thanks for all the help (:
>>>>>
>>>>>
>>>>>
>>>>> -d
>>>>>
>>>>>
>>>>>
>>>>> On 2020/08/23 19:13:36, Matt Sicker wrote:
>>>>>
>>>>> Yes, please go ahead and finish the release. The PMC approved this
>>>>>
>>>>> during our release vote. :)
>>>>>
>>>>>
>>>>>
>>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>>>>>
>>>>>>
>>>>>
>>>>>> There can’t be. That is what the release vote was for.
>>>>>
>>>>>>
>>>>>
>>>>>> Ralph
>>>>>
>>>>>>
>>>>>
>>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>>>>>
>>>>>>>
>>>>>
>>>>>>> Thanks Dominik
>>>>>
>>>>>>>
>>>>>
>>>>>>> Are there any objections to me pushing the 2.0.9 package that had
>>>> been
>>>>> approved and uploaded to https://downloads.apache.org/logging/log4net/
>>>> to
>>>>> nuget.org?
>>>>>
>>>>>>>
>>>>>
>>>>>>> -d
>>>>>
>>>>>>>
>>>>>
>>>>>>>
>>>>>
>>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
>>>>>
>>>>>>>>
>>>>>
>>>>>>>> Davyd, I added you as a collaborator. This should grant you the
>>>>> privilege
>>>>>
>>>>>>>> to manage packages. You can now submit new and update or unlist
>>>>> existing
>>>>>
>>>>>>>> packages.
>>>>>
>>>>>>>>
>>>>>
>>>>>>>> It would be great to have at least one other member of the pmc
>>>> listed
>>>>> as
>>>>>
>>>>>>>> administrator. The following documents the matrix of permissions.
>>>>> Note that
>>>>>
>>>>>>>> the amount of administrative tasks should be very limited:
>>>>>
>>>>>>>>
>>>>>
>>>>>>>>
>>>>>
>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
>>>>>
>>>>>>>>
>>>>>
>>>>>>>> Cheers
>>>>>
>>>>>>>> --
>>>>>
>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
>>>>> find
>>>>>
>>>>>>>> them.
>>>>>
>>>>>>>>
>>>>>
>>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>> Oh ok, well, mine is davydm (:
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>> -d
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
>>>>> username,
>>>>>
>>>>>>>>>> apologies.
>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>> --
>>>>>
>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
>>>> to
>>>>> find
>>>>>
>>>>>>>>>> them.
>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> I know I'm quite new, but I'm happy to push approved packages.
>>>> My
>>>>>
>>>>>>>>>>> Microsoft
>>>>>
>>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> Hi
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> I recall that we were forced to transform the nuget account
>>>>>
>>>>>>>>>>> Apache.Logging (
>>>>>
>>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
>>>> personal
>>>>>
>>>>>>>>> account
>>>>>
>>>>>>>>>>> into
>>>>>
>>>>>>>>>>>> an organization. I am currently the only member and
>>>>> administrator of
>>>>>
>>>>>>>>> that
>>>>>
>>>>>>>>>>>> organization. Please share with me (may also be in private)
>>>> the
>>>>> nuget
>>>>>
>>>>>>>>>>>> account (most probably the email of your microsoft account) if
>>>>> you
>>>>>
>>>>>>>>> want
>>>>>
>>>>>>>>>>> me
>>>>>
>>>>>>>>>>>> to add you to the organization. Any member of the pmc may also
>>>>> become
>>>>>
>>>>>>>>>>>> administrator of that group if he wishes to.
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> While I try to process your requests as fast as possible,
>>>>> please give
>>>>>
>>>>>>>>> me
>>>>>
>>>>>>>>>>>> some days. I am at the beach with the family and tend to swim
>>>>> and
>>>>>
>>>>>>>>> dive in
>>>>>
>>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> Best regards
>>>>>
>>>>>>>>>>>> Dominik
>>>>>
>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>>> happens
>>>>> to
>>>>>
>>>>>>>>> find
>>>>>
>>>>>>>>>>>> them.
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
>>>>>
>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org <
>>>>>
>>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a work
>>>> or
>>>>>
>>>>>>>>> school
>>>>>
>>>>>>>>>>>>> email.
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
>>>>>
>>>>>>>>> ralph.goers@dslextreme.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>> This gets better and better. I was able to decrypt the file
>>>>> but the
>>>>>
>>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
>>>>>
>>>>>>>>>>>>> “NuGet.org password login in no longer
>>>>>
>>>>>>>>> supported.
>>>>>
>>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
>>>>>
>>>>>>>>> ralph.goers@dslextreme.com
>>>>>
>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
>>>> same
>>>>>
>>>>>>>>> problem
>>>>>
>>>>>>>>>>> in
>>>>>
>>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
>>>>> instructions have
>>>>>
>>>>>>>>>>>>> changed.
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
>>>>>
>>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>> I figured out that the document is now at
>>>> home.apache.org
>>>>> <
>>>>>
>>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
>>>>> any good.
>>>>>
>>>>>>>>>>> gpg
>>>>>
>>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
>>>>> surprising
>>>>>
>>>>>>>>>>> since
>>>>>
>>>>>>>>>>>>> my key wasn’t used to sign the document.
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
>>>>>
>>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> Dominik,
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> The README file says that the keys can be found at
>>>>>
>>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
>>>>>
>>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>. That
>>>>> url
>>>>>
>>>>>>>>>>> returns
>>>>>
>>>>>>>>>>>>> a 404. Any idea where it moved to?
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
>>>>>
>>>>>>>>> dpsenner@gmail.com>
>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
>>>> private
>>>>>
>>>>>>>>> repos of
>>>>>
>>>>>>>>>>>>> logging
>>>>>
>>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
>>>>> recipients
>>>>>
>>>>>>>>>>> with
>>>>>
>>>>>>>>>>>>> their
>>>>>
>>>>>>>>>>>>>>>>>> gpg key.
>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>>>>
>>>>>>>>> happens to
>>>>>
>>>>>>>>>>>>> find
>>>>>
>>>>>>>>>>>>>>>>>> them.
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
>>>>>
>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> Great!
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
>>>>> final step
>>>>>
>>>>>>>>>>> that
>>>>>
>>>>>>>>>>>>> most
>>>>>
>>>>>>>>>>>>>>>>>>> users are going to be interested in.
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
>>>>> ideas on
>>>>>
>>>>>>>>>>> how
>>>>>
>>>>>>>>>>>>> to
>>>>>
>>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
>>>>> that area,
>>>>>
>>>>>>>>>>> I'm
>>>>>
>>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
>>>>> changes to
>>>>>
>>>>>>>>> the
>>>>>
>>>>>>>>>>>>> Release
>>>>>
>>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
>>>> into a
>>>>>
>>>>>>>>> release,
>>>>>
>>>>>>>>>>>>> would a
>>>>>
>>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
>>>> long
>>>>> we
>>>>>
>>>>>>>>> should
>>>>>
>>>>>>>>>>>>> wait
>>>>>
>>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I see
>>>>> updated
>>>>>
>>>>>>>>>>>>>>>>>>> artifacts on
>>>>> https://downloads.apache.org/logging/log4net/
>>>>>
>>>>>>>>> other
>>>>>
>>>>>>>>>>>>> than
>>>>>
>>>>>>>>>>>>>>>>>>> the release notes.
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>> +1 to that!
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
>>>> the
>>>>> web
>>>>>
>>>>>>>>> site
>>>>>
>>>>>>>>>>> to
>>>>>
>>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
>>>>> all
>>>>>
>>>>>>>>> changes
>>>>>
>>>>>>>>>>>>> you
>>>>>
>>>>>>>>>>>>>>>>>>> have
>>>>>
>>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
>>>> future
>>>>>
>>>>>>>>> releases
>>>>>
>>>>>>>>>>>>> for the
>>>>>
>>>>>>>>>>>>>>>>>>> next
>>>>>
>>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
>>>>> than it
>>>>>
>>>>>>>>>>> needs
>>>>>
>>>>>>>>>>>>> to be
>>>>>
>>>>>>>>>>>>>>>>>>> (:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
>>>>> into the
>>>>>
>>>>>>>>>>>>> binaries
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include "apache"
>>>>> in the
>>>>>
>>>>>>>>>>> name.
>>>>>
>>>>>>>>>>>>> I've
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the KEYS
>>>>> file
>>>>>
>>>>>>>>> for
>>>>>
>>>>>>>>>>>>> log4net,
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
>>>> with
>>>>> the
>>>>>
>>>>>>>>>>>>> project-wide
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
>>>>> outdated
>>>>>
>>>>>>>>>>>>> README.html in
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
>>>>> notes, but
>>>>>
>>>>>>>>> we
>>>>>
>>>>>>>>>>> can
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> address that next.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
>>>>> can
>>>>>
>>>>>>>>> address
>>>>>
>>>>>>>>>>>>> before
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
>>>>> zip is
>>>>>
>>>>>>>>>>>>> missing the
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
>>>>> way to
>>>>>
>>>>>>>>>>>>> include that
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
>>>>> metadata, it
>>>>>
>>>>>>>>>>>>> explicitly
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
>>>>> members.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release signing
>>>>>
>>>>>>>>>>> afterwards as
>>>>>
>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> suggests.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this? It
>>>>> has
>>>>>
>>>>>>>>> been
>>>>>
>>>>>>>>>>> more
>>>>>
>>>>>>>>>>>>>>>>>>> than 72
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
>>>> bear
>>>>> with
>>>>>
>>>>>>>>> me
>>>>>
>>>>>>>>>>> if I
>>>>>
>>>>>>>>>>>>>>>>>>> fluff it:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
>>>>> 2.0.9
>>>>>
>>>>>>>>> from
>>>>>
>>>>>>>>>>> PR
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>> https://github.com/apache/logging-log4net/pull/61
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
>>>> are
>>>>> at:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>
>>>>>
>>>> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
>>>>>
>>>>>>>>>>>>>>>>>>> tag rel/
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream, but
>>>>> this
>>>>>
>>>>>>>>> tag
>>>>>
>>>>>>>>>>> is
>>>>>
>>>>>>>>>>>>>>>>>>> exactly the
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
>>>>> above,
>>>>>
>>>>>>>>> which
>>>>>
>>>>>>>>>>>>> was
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> accepted into
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
>>>> everyone
>>>>> is ok
>>>>>
>>>>>>>>>>> with
>>>>>
>>>>>>>>>>>>>>>>>>> what's there,
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to publish
>>>>> to
>>>>>
>>>>>>>>> nuget
>>>>>
>>>>>>>>>>> do
>>>>>
>>>>>>>>>>>>> so.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
>>>>> like to
>>>>>
>>>>>>>>>>>>> tackle the
>>>>>
>>>>>>>>>>>>>>>>>>> CVE that
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
>>>>> once --
>>>>>
>>>>>>>>> it's
>>>>>
>>>>>>>>>>> a
>>>>>
>>>>>>>>>>>>>>>>>>> simple change
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
>>>>> branch
>>>>>
>>>>>>>>> some
>>>>>
>>>>>>>>>>> time
>>>>>
>>>>>>>>>>>>>>>>>>> ago, so
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> there
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
>>>>> release
>>>>>
>>>>>>>>>>> pronto,
>>>>>
>>>>>>>>>>>>> with
>>>>>
>>>>>>>>>>>>>>>>>>> only
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
>>>> else
>>>>> was
>>>>>
>>>>>>>>>>> already
>>>>>
>>>>>>>>>>>>>>>>>>> solved in
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
>>>> perhaps
>>>>> close
>>>>>
>>>>>>>>> out
>>>>>
>>>>>>>>>>>>> that
>>>>>
>>>>>>>>>>>>>>>>>>> branch to
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>
>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>>>
>>>>>
>>>>>>>>>>>
>>>>>
>>>>>>>>>
>>>>>
>>>>>>
>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Matt Sicker
>>>>>
>>>>> --
>>>> Matt Sicker
>>>>
>>
>>
>>
>
>
Re: [VOTE] Release Log4Net 2.0.9
Posted by Davyd McColl <da...@gmail.com>.
Hi Ralph
The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously forgot to push with tags ):
I've updated the source files for the site:
- removed the mirror references
- updated the links for 2.0.9
- updated the link to point to the html instead of the cgi
I've also updated the README in the project to take out the dormant status commentary.
Please review & update the live site if you're happy.
Previously, as I understand it, the point of the SVN staging area was to provide built artifacts for the website. Since that's not in play any more, I was wondering how that's going to happen now? Someone will have to build before pushing. If you'd like, I could add the target folder that is built into git so that it's just a matter of copying files.
I've also added an npm script around building the site, which checks if you have maven available & builds if possible -- perhaps this makes it easier for the next new person (:
-d
On 2020/09/02 05:20:50, Ralph Goers <ra...@dslextreme.com> wrote:
I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release.
Ralph
> On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote:
>
> The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated.
>
> Ralph
>
>> On Aug 24, 2020, at 2:45 PM, Remko Popma wrote:
>>
>> Well done, everyone!
>>
>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>
>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>> developers happy. :D
>>>
>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>
>>>> Ok, log4net 2.0.9 is up on nuget.org (:
>>>>
>>>>
>>>>
>>>> Thanks for all the help (:
>>>>
>>>>
>>>>
>>>> -d
>>>>
>>>>
>>>>
>>>> On 2020/08/23 19:13:36, Matt Sicker wrote:
>>>>
>>>> Yes, please go ahead and finish the release. The PMC approved this
>>>>
>>>> during our release vote. :)
>>>>
>>>>
>>>>
>>>> On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>>>>
>>>>>
>>>>
>>>>> There can’t be. That is what the release vote was for.
>>>>
>>>>>
>>>>
>>>>> Ralph
>>>>
>>>>>
>>>>
>>>>>> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>>>>
>>>>>>
>>>>
>>>>>> Thanks Dominik
>>>>
>>>>>>
>>>>
>>>>>> Are there any objections to me pushing the 2.0.9 package that had
>>> been
>>>> approved and uploaded to https://downloads.apache.org/logging/log4net/
>>> to
>>>> nuget.org?
>>>>
>>>>>>
>>>>
>>>>>> -d
>>>>
>>>>>>
>>>>
>>>>>>
>>>>
>>>>>>> On August 23, 2020 09:59:02 Dominik Psenner wrote:
>>>>
>>>>>>>
>>>>
>>>>>>> Davyd, I added you as a collaborator. This should grant you the
>>>> privilege
>>>>
>>>>>>> to manage packages. You can now submit new and update or unlist
>>>> existing
>>>>
>>>>>>> packages.
>>>>
>>>>>>>
>>>>
>>>>>>> It would be great to have at least one other member of the pmc
>>> listed
>>>> as
>>>>
>>>>>>> administrator. The following documents the matrix of permissions.
>>>> Note that
>>>>
>>>>>>> the amount of administrative tasks should be very limited:
>>>>
>>>>>>>
>>>>
>>>>>>>
>>>>
>>> https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
>>>>
>>>>>>>
>>>>
>>>>>>> Cheers
>>>>
>>>>>>> --
>>>>
>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens to
>>>> find
>>>>
>>>>>>> them.
>>>>
>>>>>>>
>>>>
>>>>>>>> On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
>>>>
>>>>>>>>
>>>>
>>>>>>>> Oh ok, well, mine is davydm (:
>>>>
>>>>>>>>
>>>>
>>>>>>>> -d
>>>>
>>>>>>>>
>>>>
>>>>>>>>
>>>>
>>>>>>>>> On August 22, 2020 20:49:59 Dominik Psenner wrote:
>>>>
>>>>>>>>
>>>>
>>>>>>>>> Apparently it cant be the email but must be the nuget accounts
>>>> username,
>>>>
>>>>>>>>> apologies.
>>>>
>>>>>>>>>
>>>>
>>>>>>>>> --
>>>>
>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who happens
>>> to
>>>> find
>>>>
>>>>>>>>> them.
>>>>
>>>>>>>>>
>>>>
>>>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> I know I'm quite new, but I'm happy to push approved packages.
>>> My
>>>>
>>>>>>>>>> Microsoft
>>>>
>>>>>>>>>> account for nuget is this email address (davydm@gmail.com)
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>> -d
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>> On August 22, 2020 19:46:45 Dominik Psenner wrote:
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>>>> Hi
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> I recall that we were forced to transform the nuget account
>>>>
>>>>>>>>>> Apache.Logging (
>>>>
>>>>>>>>>>> https://www.nuget.org/profiles/Apache.Logging) from a
>>> personal
>>>>
>>>>>>>> account
>>>>
>>>>>>>>>> into
>>>>
>>>>>>>>>>> an organization. I am currently the only member and
>>>> administrator of
>>>>
>>>>>>>> that
>>>>
>>>>>>>>>>> organization. Please share with me (may also be in private)
>>> the
>>>> nuget
>>>>
>>>>>>>>>>> account (most probably the email of your microsoft account) if
>>>> you
>>>>
>>>>>>>> want
>>>>
>>>>>>>>>> me
>>>>
>>>>>>>>>>> to add you to the organization. Any member of the pmc may also
>>>> become
>>>>
>>>>>>>>>>> administrator of that group if he wishes to.
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> While I try to process your requests as fast as possible,
>>>> please give
>>>>
>>>>>>>> me
>>>>
>>>>>>>>>>> some days. I am at the beach with the family and tend to swim
>>>> and
>>>>
>>>>>>>> dive in
>>>>
>>>>>>>>>>> moments when I do not build sandcastles with the kids. ;-)
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> Best regards
>>>>
>>>>>>>>>>> Dominik
>>>>
>>>>>>>>>>> --
>>>>
>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>> happens
>>>> to
>>>>
>>>>>>>> find
>>>>
>>>>>>>>>>> them.
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>> On Sat, Aug 22, 2020, 02:01 Ralph Goers
>>>>
>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>>> And, FWIW, Nuget won’t let me register with my apache.org <
>>>>
>>>>>>>>>>>> http://apache.org/> email address saying it can’t be a work
>>> or
>>>>
>>>>>>>> school
>>>>
>>>>>>>>>>>> email.
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>> On Aug 21, 2020, at 4:46 PM, Ralph Goers <
>>>>
>>>>>>>> ralph.goers@dslextreme.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>> This gets better and better. I was able to decrypt the file
>>>> but the
>>>>
>>>>>>>>>>>> credentials don’t work. The Nuget.org site says
>>>>
>>>>>>>>>>>> “NuGet.org password login in no longer
>>>>
>>>>>>>> supported.
>>>>
>>>>>>>>>>>> Please use a Microsoft account to sign into NuGet gallery.”
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>> On Aug 21, 2020, at 4:37 PM, Ralph Goers <
>>>>
>>>>>>>> ralph.goers@dslextreme.com
>>>>
>>>>>>>>>>>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>> Going back through my old emails I see Dominik had the
>>> same
>>>>
>>>>>>>> problem
>>>>
>>>>>>>>>> in
>>>>
>>>>>>>>>>>> 2016. I forgot to update my files and now I see the
>>>> instructions have
>>>>
>>>>>>>>>>>> changed.
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers <
>>>>
>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>> I figured out that the document is now at
>>> home.apache.org
>>>> <
>>>>
>>>>>>>>>>>> http://home.apache.org/>. Unfortunately, that didn’t do me
>>>> any good.
>>>>
>>>>>>>>>> gpg
>>>>
>>>>>>>>>>>> -d is failing with “No secret key”. That doesn’t seem too
>>>> surprising
>>>>
>>>>>>>>>> since
>>>>
>>>>>>>>>>>> my key wasn’t used to sign the document.
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers <
>>>>
>>>>>>>>>> ralph.goers@dslextreme.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> Dominik,
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> The README file says that the keys can be found at
>>>>
>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc <
>>>>
>>>>>>>>>>>> https://people.apache.org/keys/group/logging-pmc.asc>. That
>>>> url
>>>>
>>>>>>>>>> returns
>>>>
>>>>>>>>>>>> a 404. Any idea where it moved to?
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> On Aug 17, 2020, at 9:39 AM, Dominik Psenner <
>>>>
>>>>>>>> dpsenner@gmail.com>
>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> I guess that would be a nuget publish.
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> The credentials to that account are stored in the
>>> private
>>>>
>>>>>>>> repos of
>>>>
>>>>>>>>>>>> logging
>>>>
>>>>>>>>>>>>>>>>> pmc. Most members of the pmc should be in the set of
>>>> recipients
>>>>
>>>>>>>>>> with
>>>>
>>>>>>>>>>>> their
>>>>
>>>>>>>>>>>>>>>>> gpg key.
>>>>
>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>> Sent from my phone. Typos are a kind gift to anyone who
>>>>
>>>>>>>> happens to
>>>>
>>>>>>>>>>>> find
>>>>
>>>>>>>>>>>>>>>>> them.
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>> On Mon, Aug 17, 2020, 08:56 Davyd McColl
>>>>
>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> Great!
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> How do we get the nupkg to nuget.org? This is the
>>>> final step
>>>>
>>>>>>>>>> that
>>>>
>>>>>>>>>>>> most
>>>>
>>>>>>>>>>>>>>>>>> users are going to be interested in.
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> Having a look at what's at the url you posted, I have
>>>> ideas on
>>>>
>>>>>>>>>> how
>>>>
>>>>>>>>>>>> to
>>>>
>>>>>>>>>>>>>>>>>> streamline future releases, so the next time I'm in
>>>> that area,
>>>>
>>>>>>>>>> I'm
>>>>
>>>>>>>>>>>>>>>>>> definitely implementing those ideas. I don't see
>>>> changes to
>>>>
>>>>>>>> the
>>>>
>>>>>>>>>>>> Release
>>>>
>>>>>>>>>>>>>>>>>> Notes area -- if I were to try to streamline that
>>> into a
>>>>
>>>>>>>> release,
>>>>
>>>>>>>>>>>> would a
>>>>
>>>>>>>>>>>>>>>>>> CHANGELOG file be useful? Or is there a better way?
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> -d
>>>>
>>>>>>>>>>>>>>>>>> On 2020/08/16 23:26:07, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>> I committed them to dist already. I don't know how
>>> long
>>>> we
>>>>
>>>>>>>> should
>>>>
>>>>>>>>>>>> wait
>>>>
>>>>>>>>>>>>>>>>>> for any mirroring to catch up, though on my end, I see
>>>> updated
>>>>
>>>>>>>>>>>>>>>>>> artifacts on
>>>> https://downloads.apache.org/logging/log4net/
>>>>
>>>>>>>> other
>>>>
>>>>>>>>>>>> than
>>>>
>>>>>>>>>>>>>>>>>> the release notes.
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>> +1 to that!
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>> Let me know when these are published. I can update
>>> the
>>>> web
>>>>
>>>>>>>> site
>>>>
>>>>>>>>>> to
>>>>
>>>>>>>>>>>>>>>>>> reflect that it is no longer dormant.
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> Thanks so much for your help in releasing this!
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>> I'll make changes to the automated build to affect
>>>> all
>>>>
>>>>>>>> changes
>>>>
>>>>>>>>>>>> you
>>>>
>>>>>>>>>>>>>>>>>> have
>>>>
>>>>>>>>>>>>>>>>>>>>> made (and perhaps will make) automatically to
>>> future
>>>>
>>>>>>>> releases
>>>>
>>>>>>>>>>>> for the
>>>>
>>>>>>>>>>>>>>>>>> next
>>>>
>>>>>>>>>>>>>>>>>>>>> release. Apologies for making this more difficult
>>>> than it
>>>>
>>>>>>>>>> needs
>>>>
>>>>>>>>>>>> to be
>>>>
>>>>>>>>>>>>>>>>>> (:
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>> -d
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>> Just a simple copy of the LICENSE and NOTICE file
>>>> into the
>>>>
>>>>>>>>>>>> binaries
>>>>
>>>>>>>>>>>>>>>>>>>>>> zip, and a rename of the files to include "apache"
>>>> in the
>>>>
>>>>>>>>>> name.
>>>>
>>>>>>>>>>>> I've
>>>>
>>>>>>>>>>>>>>>>>>>>>> uploaded them to dist along with updating the KEYS
>>>> file
>>>>
>>>>>>>> for
>>>>
>>>>>>>>>>>> log4net,
>>>>
>>>>>>>>>>>>>>>>>>>>>> though that should probably be merged together
>>> with
>>>> the
>>>>
>>>>>>>>>>>> project-wide
>>>>
>>>>>>>>>>>>>>>>>>>>>> KEYS file in the parent directory. There's an
>>>> outdated
>>>>
>>>>>>>>>>>> README.html in
>>>>
>>>>>>>>>>>>>>>>>>>>>> the directory still containing the old release
>>>> notes, but
>>>>
>>>>>>>> we
>>>>
>>>>>>>>>> can
>>>>
>>>>>>>>>>>>>>>>>>>>>> address that next.
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>> One issue I found in one of the artifacts that I
>>>> can
>>>>
>>>>>>>> address
>>>>
>>>>>>>>>>>> before
>>>>
>>>>>>>>>>>>>>>>>>>>>>> uploading since it wasn't signed is the binaries
>>>> zip is
>>>>
>>>>>>>>>>>> missing the
>>>>
>>>>>>>>>>>>>>>>>>>>>>> LICENSE file. I'm not sure if there's a standard
>>>> way to
>>>>
>>>>>>>>>>>> include that
>>>>
>>>>>>>>>>>>>>>>>>>>>>> in the nupkg file, but I did see that in its
>>>> metadata, it
>>>>
>>>>>>>>>>>> explicitly
>>>>
>>>>>>>>>>>>>>>>>>>>>>> says the code is Apache2 licensed at least.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I'll sign and publish the artifacts today.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Remko. That makes 3 +1 votes from PMC
>>>> members.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> +1 Remko.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker
>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> +1 from me. We can handle the release signing
>>>>
>>>>>>>>>> afterwards as
>>>>
>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>>>>> suggests.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can other PMC members please review this? It
>>>> has
>>>>
>>>>>>>> been
>>>>
>>>>>>>>>> more
>>>>
>>>>>>>>>>>>>>>>>> than 72
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> hours.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ralph
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi all, I've never done this before, so
>>> bear
>>>> with
>>>>
>>>>>>>> me
>>>>
>>>>>>>>>> if I
>>>>
>>>>>>>>>>>>>>>>>> fluff it:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is a proposed vote to release log4net
>>>> 2.0.9
>>>>
>>>>>>>> from
>>>>
>>>>>>>>>> PR
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>> https://github.com/apache/logging-log4net/pull/61
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Release artifacts (including source zip)
>>> are
>>>> at:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>
>>>>
>>> https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063235/artifacts
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source can be checked out from
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
>>>>
>>>>>>>>>>>>>>>>>> tag rel/
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.0.9. I can't push tags to the upstream, but
>>>> this
>>>>
>>>>>>>> tag
>>>>
>>>>>>>>>> is
>>>>
>>>>>>>>>>>>>>>>>> exactly the
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> same commit as the last in the PR mentioned
>>>> above,
>>>>
>>>>>>>> which
>>>>
>>>>>>>>>>>> was
>>>>
>>>>>>>>>>>>>>>>>>>>>>> accepted into
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> master a few days ago.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please check out the artifacts & if
>>> everyone
>>>> is ok
>>>>
>>>>>>>>>> with
>>>>
>>>>>>>>>>>>>>>>>> what's there,
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> please can someone with the rights to publish
>>>> to
>>>>
>>>>>>>> nuget
>>>>
>>>>>>>>>> do
>>>>
>>>>>>>>>>>> so.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Once I've seen how this process works, I'd
>>>> like to
>>>>
>>>>>>>>>>>> tackle the
>>>>
>>>>>>>>>>>>>>>>>> CVE that
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> has been brought up on this list more than
>>>> once --
>>>>
>>>>>>>> it's
>>>>
>>>>>>>>>> a
>>>>
>>>>>>>>>>>>>>>>>> simple change
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> which was already committed to the develop
>>>> branch
>>>>
>>>>>>>> some
>>>>
>>>>>>>>>> time
>>>>
>>>>>>>>>>>>>>>>>> ago, so
>>>>
>>>>>>>>>>>>>>>>>>>>>>> there
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> are a couple of options here:
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. cherry-pick that commit & do a 2.0.10
>>>> release
>>>>
>>>>>>>>>> pronto,
>>>>
>>>>>>>>>>>> with
>>>>
>>>>>>>>>>>>>>>>>> only
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> that change
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. trawl the develop branch to see what
>>> else
>>>> was
>>>>
>>>>>>>>>> already
>>>>
>>>>>>>>>>>>>>>>>> solved in
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> there, and get that out as 2.0.10, and
>>> perhaps
>>>> close
>>>>
>>>>>>>> out
>>>>
>>>>>>>>>>>> that
>>>>
>>>>>>>>>>>>>>>>>> branch to
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> avoid future confusion.
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for your time
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -d
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>>> --
>>>>
>>>>>>>>>>>>>>>>>> Matt Sicker
>>>>
>>>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>>>
>>>>
>>>>>>>>>>
>>>>
>>>>>>>>
>>>>
>>>>>
>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Matt Sicker
>>>>
>>>> --
>>> Matt Sicker
>>>
>
>
>