-1
Agree with the concerns above.

On Thu, Aug 1, 2024 at 2:47 PM Tim Brown <tim.brown...@gmail.com> wrote:

> -1
> We still have some artifacts that need to be updated with the incubator
> prefix such as xtable-hudi-support-extensions and
> xtable-hudi-support-utils.
>
> -Tim
>
> On Tue, Jul 30, 2024 at 3:12 PM Vinish Reddy <vin...@apache.org> wrote:
>
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version 0.1.0,
> > as follows:
> >
> > [ ] +1, Approve the release
> >
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > NOTE: This is the first ever release candidate for the project and has
> been
> > created through a new release guide. I'm utilising this first release
> > candidate to ensure the artifact names are correct and ironing out any
> > process gaps. If the artifacts are okay, I will create release candidate
> #2
> > to ensure that future releases won't have any infra/process related gaps.
> >
> > The complete staging area is available for your review, which includes:
> >
> > *GH release notes [1],
> >
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 5EFD1E91 [3],
> >
> > * all artifacts to be deployed to the Maven Central Repository [4],
> >
> > * source code tag "0.1.0-rc1" [5],
> >
> > Thanks,
> > Vinish
> >
> > [1] https://github.com/apache/incubator-xtable/issues/486
> >
> > [2]
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/xtable/incubator-xtable-0.1.0-rc1/
> >
> > [3] https://dist.apache.org/repos/dist/dev/incubator/xtable/KEYS
> >
> > [4]
> >
> >
> https://repository.apache.org/service/local/repositories/orgapachextable-1000/content/org/apache/xtable/
> > (You can access this via
> > https://repository.apache.org/index.html#stagingRepositories as well)
> >
> > [5]
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/xtable/incubator-xtable-0.1.0-rc1/incubator-xtable-0.1.0-rc1.src.tgz
> >
>

Reply via email to