I don't have too much experience in svn. I usually follow the commands
listed in the how to release doc and it works for me. (Don't remember if
I've had to do some initial steps.) As a committer you should have write
access to all the repositories of the Parquet community.

On Wed, Apr 7, 2021 at 4:18 PM Antoine Pitrou <[email protected]> wrote:

>
> Ah!  It seems I can't push to that repo:
>
> Sending        KEYS
> Transmitting file data .svn: E195023: Commit failed (details follow):
> svn: E195023: Changing file '/home/antoine/apache/parquet-release/KEYS' is
> forbidden by the server
> svn: E175013: Access to
> '/repos/dist/!svn/txr/46918-13e8/release/parquet/KEYS' forbidden
>
>
> The URL I used for checkout is
> https://[email protected]/repos/dist/release/parquet
> Should I use another one?
>
> Regards
>
> Antoine.
>
>
>
> On Wed, 7 Apr 2021 16:00:26 +0200
> Gabor Szadovszky
> <[email protected]>
> wrote:
> > Sorry, I've missed you updated the dev repo. The downloads page mirrors
> the
> > release repo. Yet another place (besides the parquet-format and
> parquet-mr
> > repos) where we store a KEYS file for whatever reason. Please update the
> > one in the release repo.
> >
> > On Wed, Apr 7, 2021 at 3:47 PM Gabor Szadovszky <
> > [email protected]> wrote:
> >
> > > I guess it only requires some time to sync. Last time the release
> tarball
> > > required ~1hour to sync.
> > >
> > > On Wed, Apr 7, 2021 at 3:42 PM Antoine Pitrou <[email protected]>
> wrote:
> > >
> > >>
> > >> Hi Gabor,
> > >>
> > >> Ok, I updated the KEYS file in the Parquet SVN repository.
> > >> The changes do appear in
> > >> https://dist.apache.org/repos/dist/dev/parquet/KEYS -- but not in
> > >> https://downloads.apache.org/parquet/KEYS .  Is there any additional
> > >> step I should perform?
> > >>
> > >> Regards
> > >>
> > >> Antoine.
> > >>
> > >>
> > >> On Wed, 7 Apr 2021 15:19:24 +0200
> > >> Gabor Szadovszky <[email protected]> wrote:
> > >>
> > >> > Hi Antoine,
> > >> >
> > >> > Thanks for initiating this release! You need to update the listed
> KEYS
> > >> file
> > >> > with your public key otherwise we cannot validate the signature.
> (To do
> > >> > that you need to update the releases svn repo. See details in the
> how to
> > >> > release doc about the publishing.)
> > >> >
> > >> > Regards,
> > >> > Gabor
> > >> >
> > >> > On Wed, Apr 7, 2021 at 3:10 PM Antoine Pitrou <[email protected]>
>
> > >> wrote:
> > >> >
> > >> > >
> > >> > > Hi everyone,
> > >> > >
> > >> > > I propose the following RC to be released as official Apache
> Parquet
> > >> > > Format 2.9.0 release.
> > >> > >
> > >> > > The commit id is b4f0c0a643a6ec1a7def37115dd6967ba9346df7
> > >> > > * This corresponds to the tag: apache-parquet-format-2.9.0-rc0
> > >> > > *
> > >> > >
> > >>
> https://github.com/apache/parquet-format/tree/b4f0c0a643a6ec1a7def37115dd6967ba9346df7
>
> > >> > >
> > >> > > The release tarball, signature, and checksums are here:
> > >> > > *
> > >> > >
> > >>
> https://dist.apache.org/repos/dist/dev/parquet/apache-parquet-format-2.9.0-rc0/
>
> > >> > >
> > >> > > You can find the KEYS file here:
> > >> > > * https://downloads.apache.org/parquet/KEYS
> > >> > >
> > >> > > Binary artifacts are staged in Nexus here:
> > >> > > *
> > >> > >
> > >>
> https://repository.apache.org/content/groups/staging/org/apache/parquet/parquet-format/
>
> > >> > >
> > >> > > This release includes the following important fixes and
> improvements:
> > >> > >
> > >> > > * PARQUET-1996 - [Format] Add interoperable LZ4 codec, deprecate
> > >> existing
> > >> > > LZ4 codec
> > >> > > * PARQUET-2013 - [Format] Mention that converted types are
> deprecated
> > >> > >
> > >> > > ...among other changes (see CHANGES.md for full list).
> > >> > >
> > >> > > Please download, verify, and test.
> > >> > >
> > >> > > Please vote in the next 72 hours.
> > >> > >
> > >> > > [ ] +1 Release this as Apache Parquet 2.9.0
> > >> > > [ ] +0
> > >> > > [ ] -1 Do not release this because...
> > >> > >
> > >> > >
> > >> > > Regards
> > >> > >
> > >> > > Antoine.
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >>
> >
>
>
>
>

Reply via email to