I have updated the release guide PR as well https://github.com/apache/incubator-xtable/pull/434, this was used to created 0.1.0-rc-1 release version.
-Vinish On 2024/07/30 13:42:23 Vinish Reddy wrote: > I have uploaded the rc-1 artifacts to the staging repository > [https://repository.apache.org/#stagingRepositories]. Can you try downloading > the jar and maybe run few basic validations from the README section ? I have > verified the jar by myself. > > You need to replace the jar with the downloaded one and maybe change execute > permissions using chmod. > java -jar incubator-xtable-utilities-0.1.0-rc1-bundled.jar --datasetConfig > datasetConfig.yaml > > Meanwhile any comments on the artifacts naming are also helpful, have ensured > all artifacts have the "incubator" prefix and user need to import the > dependency like this. > > <dependency> > <groupId>org.apache.xtable</groupId> > <artifactId>incubator-xtable-utilities</artifactId> > <version>0.1.0-rc1</version> > <classifier>bundled</classifier> > </dependency> > > Thanks, > Vinish > > On 2024/07/13 13:18:14 Stamatis Zampetakis wrote: > > I just logged INFRA-25963 asking for the creation of the Nexus > > profiles for XTable. > > > > Best, > > Stamatis > > > > [1] https://issues.apache.org/jira/browse/INFRA-25963 > > > > On Fri, Jul 12, 2024 at 11:23 AM Vinish Reddy <vin...@apache.org> wrote: > > > > > > Regarding the release, currently facing one blocker in the last step > > > where release candidate artifacts are uploaded to > > > https://repository.apache.org > > > > > > Any help from people who have done releases for incubating projects is > > > appreciated. Documented the error in the GH issue created for release. > > > https://github.com/apache/incubator-xtable/issues/486 > > > > > > "Among other things we would also need a download page" -> I will create > > > a PR for this. > > > > > > Thanks, > > > Vinish > > > > > > On 2024/07/11 20:01:29 Stamatis Zampetakis wrote: > > > > Among other things we would also need a download page in the website > > > > [1] that follows the guidelines in [2]. > > > > > > > > Best, > > > > Stamatis > > > > > > > > [1] https://xtable.apache.org/ > > > > [2] https://infra.apache.org/release-download-pages.html > > > > > > > > On Wed, Jul 10, 2024 at 12:11 PM Vinish Reddy <vin...@apache.org> wrote: > > > > > > > > > > Progress so far and Next steps: > > > > > 1. Generated keys in > > > > > https://dist.apache.org/repos/dist/dev/incubator/xtable/KEYS > > > > > 2. Validated the guide in a dry-run mode (without actually pushing > > > > > the release branch or artifacts or tarball files) > > > > > 3. Create a release candidate after merging the PR for DISCLAIMER-WIP > > > > > [https://github.com/apache/incubator-xtable/pull/487] > > > > > > > > > > On 2024/07/08 17:12:43 Vinoth Chandar wrote: > > > > > > >> I would be more inclined to go for an official ASF release using > > > > > > >> the > > > > > > "Work In Progress Disclaimer" [1]. > > > > > > > > > > > > +1 on this path. IMO non-ASF release infrastructure is additional > > > > > > work for > > > > > > the community to take on, as a stop-gap. > > > > > > > > > > > > On Mon, Jul 8, 2024 at 2:35 AM Jesus Camacho Rodriguez > > > > > > <jcama...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > I was not aware of the work-in-progress disclaimer, that sounds > > > > > > > like a good > > > > > > > idea as well! > > > > > > > > > > > > > > +1 to start moving forward with the release process as soon as > > > > > > > possible. > > > > > > > > > > > > > > Thanks, > > > > > > > Jesús > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 8, 2024 at 11:30 AM Stamatis Zampetakis > > > > > > > <zabe...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hey everyone, > > > > > > > > > > > > > > > > It would be great to have an XTable release during July. > > > > > > > > > > > > > > > > A non-ASF release does not require the blessing of the > > > > > > > > incubator PMC > > > > > > > > and must not be distributed via the ASF channels and > > > > > > > > infrastructure. > > > > > > > > > > > > > > > > I would be more inclined to go for an official ASF release > > > > > > > > using the > > > > > > > > "Work In Progress Disclaimer" [1]. It may take a few release > > > > > > > > candidate > > > > > > > > attempts till we sort things out but if we can afford a few > > > > > > > > weeks > > > > > > > > delay then this path forward may be more productive. > > > > > > > > > > > > > > > > I will do a pass over the proposed release guide later today > > > > > > > > although > > > > > > > > we don't have to wait till it's perfect. The best path forward > > > > > > > > is > > > > > > > > preparing the first release candidate and at the same time > > > > > > > > documenting > > > > > > > > the procedure and steps taken. > > > > > > > > > > > > > > > > Best, > > > > > > > > Stamatis > > > > > > > > > > > > > > > > [1] > > > > > > > > https://incubator.apache.org/policy/incubation.html#disclaimers > > > > > > > > > > > > > > > > On Mon, Jul 8, 2024 at 10:54 AM Jesus Camacho Rodriguez > > > > > > > > <jcama...@apache.org> wrote: > > > > > > > > > > > > > > > > > > Hi Vinish, > > > > > > > > > > > > > > > > > > Thanks for putting this proposal together! > > > > > > > > > > > > > > > > > > I agree that a non-ASF release is a good idea to iron out any > > > > > > > > > issues > > > > > > > that > > > > > > > > > we need to fix before having a proper ASF release. > > > > > > > > > Your timing for an ASF-compliant release in July also sounds > > > > > > > > > reasonable > > > > > > > > to > > > > > > > > > me. > > > > > > > > > I have reviewed your PR and left a few comments there based > > > > > > > > > on its > > > > > > > > contents. > > > > > > > > > > > > > > > > > > I hope others in the community join this important discussion > > > > > > > > > as well. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Jesús > > > > > > > > > > > > > > > > > > On Wed, Jul 3, 2024 at 8:29 PM Vinish Reddy Pannala < > > > > > > > > > vinishreddypann...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > > > > > > > I hope this message finds you well. > > > > > > > > > > > > > > > > > > > > Based on the guidelines > > > > > > > > > > <https://incubator.apache.org/guides/releasemanagement.html> > > > > > > > > mentioned for > > > > > > > > > > Apache incubating projects - Podlings can use non-ASF > > > > > > > > > > releases as an > > > > > > > > > > opportunity to find ASF policy violations and begin > > > > > > > > > > resolving them. I > > > > > > > > have > > > > > > > > > > put up a release guide PR for the upcoming Apache XTable > > > > > > > > > > (Incubating) > > > > > > > > > > release and propose running an interim non-ASF release to > > > > > > > > > > iron out > > > > > > > > issues. > > > > > > > > > > https://github.com/apache/incubator-xtable/pull/434 > > > > > > > > > > > > > > > > > > > > After resolving issues from the non-ASF release, I propose > > > > > > > > > > we target > > > > > > > an > > > > > > > > > > ASF-compliant release for Apache XTable (Incubating) in > > > > > > > > > > July. Please > > > > > > > > share > > > > > > > > > > your thoughts and any objections regarding this proposed > > > > > > > > > > timeline. > > > > > > > Your > > > > > > > > > > feedback is crucial to ensure we meet the necessary > > > > > > > > > > requirements and > > > > > > > > > > address any potential issues before the release. > > > > > > > > > > > > > > > > > > > > Looking forward to your input. > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > Vinish > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
