You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@yazi.ci> on 2024/03/01 16:21:39 UTC
Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)
Davyd, assuming you have `svn` in the command line, following should get
the job done:
# Checkout the `dev` distribution repository
svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
cd logging-dist-dev
# Delete old distribution files
svn rm log4net
# Add the new distribution of the new release
mkdir -p log4net/2.0.16
cp /path/to/distribution/files log4net/2.0.16/
svn add log4net
# Commit changes
svn commit -m 'Add `log4net` version `2.0.16` distribution files'
I presume you are using Windows. Getting `svn` in the Windows shell is
explained in this SO post.
<https://stackoverflow.com/questions/2341134/command-line-svn-for-windows>
Let me know if this does/doesn't help.
Good luck!
On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl <da...@gmail.com> wrote:
> Hi Volkan
>
> That was my whole point with the question on my release vote: I have put
> things in svn, bit I'm not seeing them at the url you've posted. I assume
> I've done something wrong, but I don't know what and need someone to help.
> I must admit my svn-fu is rubbish so perhaps I just messed up there. With
> the other svn repos, I use git svn bridge, but I don't want to do that here
> because that repo us huge and filled with binaries
>
> TL;DR Halp! 😅
>
> -d
>
> On 01 March 2024 15:46:24 Volkan Yazıcı <vo...@yazi.ci> wrote:
>
>> Davyd, I am afraid it cannot qualify an official vote if the [source]
>> distribution artifacts are missing. This is the whole point of the ASF
>> release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget, etc. can
>> be the most important mediums for you and/or the project, though they are
>> irrelevant from an ASF point of view.
>>
>> Could you upload the source distribution to the `
>> https://dist.apache.org/repos/dist/dev/logging /log4net` Subversion
>> folder
>> along with checksum and signature files, please?
>>
>> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl <da...@gmail.com> wrote:
>>
>>> Hi all
>>>
>>> This is the vote to release Apache log4net version 2.0.16
>>>
>>> Website:
>>> https://logging.staged.apache.org/log4net/release/release-notes.html
>>>
>>> GitHub: https://github.com/apache/logging-log4net
>>>
>>> GitHub release (pre-release):
>>> https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1
>>>
>>> Distribution: I'm not sure -
>>> https://dist.apache.org/repos/dist/dev/logging/log4net should have
>>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing
>>> them. Any help appreciated.
>>>
>>> Please have a look at the staging site & artifacts and test (if you can
>>> - clone, `npm i`, `npm test`)
>>>
>>> [ ] +1, release the artifacts
>>>
>>> [ ] -1, don't release, because....
>>>
>>> (thanks Piotr: I copied most of your last VOTE mail!)
>>>
>>> -d
>>>
>>
Re: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)
Posted by Davyd McColl <da...@gmail.com>.
Hi Jan
I think you're right. It's been so long since I've used svn as a daily
driver - even longer since I wrote a build system in c++ that hooked into
svn and triggered workloads on commits at the server 😅. Thanks for
figuring it out.
-d
On 02 March 2024 18:50:14 Jan Friedrich <fr...@apache.org> wrote:
> Hi,
>
> I think I got it uploaded (from my machine).
>
> choco install svn
> svn co https://dist.apache.org/repos/dist/dev/logging -N
> apache-dist-logging-dev
> cd apache-dist-logging-dev
> svn up log4net
> svn delete .\log4net\binaries\*2.0.14.*
> svn add .\log4net\binaries\*
> svn add .\log4net\source\*
> svn commit -m 'v2.0.16'
>
> Take a look at
>
> https://dist.apache.org/repos/dist/dev/logging/log4net/binaries/
> https://dist.apache.org/repos/dist/dev/logging/log4net/source/
>
> @Davyd: Maybe we missed the bold lines on Friday?
>
> Regards.
>
> Jan
>
> Friday, March 1, 2024, 6:27:38 PM, you wrote:
>
>> Hi Volkan
>
>
>> Thanks for taking the time to explain (:
>
>
>> This is pretty-much what I did, as per step 16
>> of https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md -
>> unless there's a typo I've made somewhere or something like that. That's
>> why I'm confused as to why I can't see the artifacts in the right place ):
>
>
>> No need to rush on this though - monday is fine: I very likely won't do
>> anything about it until then anyway (:
>
>
>> -d
>
>> On 2024/03/01 18:21, Volkan Yazıcı wrote:
>>> Davyd, assuming you have `svn` in the command line, following should > get
>>> the job done:
>>> # Checkout the `dev` distribution repository
>>> svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
>>> cd logging-dist-dev
>>> # Delete old distribution files
>>> svn rm log4net
>>> # Add the new distribution of the new release
>>> mkdir -p log4net/2.0.16
>>> cp /path/to/distribution/files log4net/2.0.16/
>>> svn add log4net
>>> # Commit changes
>>> svn commit -m 'Add `log4net` version `2.0.16` distribution files'
>>> I presume you are using Windows. Getting `svn` in the Windows shell is >
>>> explained in this SO post. >
>>> <https://stackoverflow.com/questions/2341134/command-line-svn-for-windows>
>>> Let me know if this does/doesn't help.
>>> Good luck!
>>> On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl <da...@gmail.com> wrote:
>>> Hi Volkan
>>> That was my whole point with the question on my release vote: I
>>> have put things in svn, bit I'm not seeing them at the url you've
>>> posted. I assume I've done something wrong, but I don't know what
>>> and need someone to help. I must admit my svn-fu is rubbish so
>>> perhaps I just messed up there. With the other svn repos, I use
>>> git svn bridge, but I don't want to do that here because that repo
>>> us huge and filled with binaries
>>> TL;DR Halp! 😅
>>> -d
>>> On 01 March 2024 15:46:24 Volkan Yazıcı <vo...@yazi.ci> wrote:
>>>> Davyd, I am afraid it cannot qualify an official vote if the [source]
>>>> distribution artifacts are missing. This is the whole point of
>>>> the ASF
>>>> release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget,
>>>> etc. can
>>>> be the most important mediums for you and/or the project, though
>>>> they are
>>>> irrelevant from an ASF point of view.
>
>>>> Could you upload the source distribution to the `
>>>> https://dist.apache.org/repos/dist/dev/logging /log4net`
>>>> Subversion folder
>>>> along with checksum and signature files, please?
>>>> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl <da...@gmail.com> wrote:
>>>>> Hi all
>
>>>>> This is the vote to release Apache log4net version 2.0.16
>>>>> Website:
>>>>> https://logging.staged.apache.org/log4net/release/release-notes.html
>>>>> GitHub: https://github.com/apache/logging-log4net
>>>>> GitHub release (pre-release):
>>>>> https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1
>>>>> Distribution: I'm not sure -
>>>>> https://dist.apache.org/repos/dist/dev/logging/log4net should have
>>>>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing
>>>>> them. Any help appreciated.
>>>>> Please have a look at the staging site & artifacts and test (if
>>>>> you can
>>>>> - clone, `npm i`, `npm test`)
>>>>> [ ] +1, release the artifacts
>>>>> [ ] -1, don't release, because....
>>>>> (thanks Piotr: I copied most of your last VOTE mail!)
>>>>> -d
Re: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)
Posted by Jan Friedrich <fr...@apache.org>.
Hi,
I think I got it uploaded (from my machine).
choco install svn
svn co https://dist.apache.org/repos/dist/dev/logging -N apache-dist-logging-dev
cd apache-dist-logging-dev
svn up log4net
svn delete .\log4net\binaries\*2.0.14.*
svn add .\log4net\binaries\*
svn add .\log4net\source\*
svn commit -m 'v2.0.16'
Take a look at
https://dist.apache.org/repos/dist/dev/logging/log4net/binaries/
https://dist.apache.org/repos/dist/dev/logging/log4net/source/
@Davyd: Maybe we missed the bold lines on Friday?
Regards.
Jan
Friday, March 1, 2024, 6:27:38 PM, you wrote:
> Hi Volkan
> Thanks for taking the time to explain (:
> This is pretty-much what I did, as per step 16 of https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md - unless there's a typo I've made somewhere or something like that. That's why I'm confused as to why I can't see the artifacts in the right place ):
> No need to rush on this though - monday is fine: I very likely won't do anything about it until then anyway (:
> -d
> On 2024/03/01 18:21, Volkan Yazıcı wrote:
>> Davyd, assuming you have `svn` in the command line, following should > get the job done:
>> # Checkout the `dev` distribution repository
>> svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
>> cd logging-dist-dev
>> # Delete old distribution files
>> svn rm log4net
>> # Add the new distribution of the new release
>> mkdir -p log4net/2.0.16
>> cp /path/to/distribution/files log4net/2.0.16/
>> svn add log4net
>> # Commit changes
>> svn commit -m 'Add `log4net` version `2.0.16` distribution files'
>> I presume you are using Windows. Getting `svn` in the Windows shell is > explained in this SO post. > <https://stackoverflow.com/questions/2341134/command-line-svn-for-windows>
>> Let me know if this does/doesn't help.
>> Good luck!
>> On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl <da...@gmail.com> wrote:
>> Hi Volkan
>> That was my whole point with the question on my release vote: I
>> have put things in svn, bit I'm not seeing them at the url you've
>> posted. I assume I've done something wrong, but I don't know what
>> and need someone to help. I must admit my svn-fu is rubbish so
>> perhaps I just messed up there. With the other svn repos, I use
>> git svn bridge, but I don't want to do that here because that repo
>> us huge and filled with binaries
>> TL;DR Halp! 😅
>> -d
>> On 01 March 2024 15:46:24 Volkan Yazıcı <vo...@yazi.ci> wrote:
>>> Davyd, I am afraid it cannot qualify an official vote if the [source]
>>> distribution artifacts are missing. This is the whole point of
>>> the ASF
>>> release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget,
>>> etc. can
>>> be the most important mediums for you and/or the project, though
>>> they are
>>> irrelevant from an ASF point of view.
>>> Could you upload the source distribution to the `
>>> https://dist.apache.org/repos/dist/dev/logging /log4net`
>>> Subversion folder
>>> along with checksum and signature files, please?
>>> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl <da...@gmail.com> wrote:
>>>> Hi all
>>>> This is the vote to release Apache log4net version 2.0.16
>>>> Website:
>>>> https://logging.staged.apache.org/log4net/release/release-notes.html
>>>> GitHub: https://github.com/apache/logging-log4net
>>>> GitHub release (pre-release):
>>>> https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1
>>>> Distribution: I'm not sure -
>>>> https://dist.apache.org/repos/dist/dev/logging/log4net should have
>>>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing
>>>> them. Any help appreciated.
>>>> Please have a look at the staging site & artifacts and test (if
>>>> you can
>>>> - clone, `npm i`, `npm test`)
>>>> [ ] +1, release the artifacts
>>>> [ ] -1, don't release, because....
>>>> (thanks Piotr: I copied most of your last VOTE mail!)
>>>> -d
Re: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)
Posted by Davyd McColl <da...@gmail.com>.
Hi Volkan
Thanks for taking the time to explain (:
This is pretty-much what I did, as per step 16 of
https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md -
unless there's a typo I've made somewhere or something like that. That's
why I'm confused as to why I can't see the artifacts in the right place ):
No need to rush on this though - monday is fine: I very likely won't do
anything about it until then anyway (:
-d
On 2024/03/01 18:21, Volkan Yazıcı wrote:
> Davyd, assuming you have `svn` in the command line, following should
> get the job done:
>
> # Checkout the `dev` distribution repository
> svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
> cd logging-dist-dev
>
> # Delete old distribution files
> svn rm log4net
>
> # Add the new distribution of the new release
> mkdir -p log4net/2.0.16
> cp /path/to/distribution/files log4net/2.0.16/
> svn add log4net
>
> # Commit changes
> svn commit -m 'Add `log4net` version `2.0.16` distribution files'
>
>
> I presume you are using Windows. Getting `svn` in the Windows shell is
> explained in this SO post.
> <https://stackoverflow.com/questions/2341134/command-line-svn-for-windows>
>
> Let me know if this does/doesn't help.
>
> Good luck!
>
> On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl <da...@gmail.com> wrote:
>
> Hi Volkan
>
> That was my whole point with the question on my release vote: I
> have put things in svn, bit I'm not seeing them at the url you've
> posted. I assume I've done something wrong, but I don't know what
> and need someone to help. I must admit my svn-fu is rubbish so
> perhaps I just messed up there. With the other svn repos, I use
> git svn bridge, but I don't want to do that here because that repo
> us huge and filled with binaries
>
> TL;DR Halp! 😅
>
> -d
>
> On 01 March 2024 15:46:24 Volkan Yazıcı <vo...@yazi.ci> wrote:
>
>> Davyd, I am afraid it cannot qualify an official vote if the [source]
>> distribution artifacts are missing. This is the whole point of
>> the ASF
>> release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget,
>> etc. can
>> be the most important mediums for you and/or the project, though
>> they are
>> irrelevant from an ASF point of view.
>>
>> Could you upload the source distribution to the `
>> https://dist.apache.org/repos/dist/dev/logging /log4net`
>> Subversion folder
>> along with checksum and signature files, please?
>>
>> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl <da...@gmail.com> wrote:
>>
>>> Hi all
>>>
>>> This is the vote to release Apache log4net version 2.0.16
>>>
>>> Website:
>>> https://logging.staged.apache.org/log4net/release/release-notes.html
>>>
>>> GitHub: https://github.com/apache/logging-log4net
>>>
>>> GitHub release (pre-release):
>>> https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1
>>>
>>> Distribution: I'm not sure -
>>> https://dist.apache.org/repos/dist/dev/logging/log4net should have
>>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing
>>> them. Any help appreciated.
>>>
>>> Please have a look at the staging site & artifacts and test (if
>>> you can
>>> - clone, `npm i`, `npm test`)
>>>
>>> [ ] +1, release the artifacts
>>>
>>> [ ] -1, don't release, because....
>>>
>>> (thanks Piotr: I copied most of your last VOTE mail!)
>>>
>>> -d
>>>