Why do you have a source release zip in Maven Central? Shouldn't we only have the official releases that are released to svn to dist.apache.org?
I would like to raise a vote about this part of the process. I guess it's sort of up to the PPMC but this seems odd to me. https://repository.apache.org/content/groups/staging/org/apache/fury/fury-parent/0.8.0/ On Mon, 7 Oct 2024 at 17:25, Shawn Yang <[email protected]> wrote: > > Yean, I uploaded to staging repository using the same commiidas rest of > fury 0.8.0 > > PJ Fanning <[email protected]>于2024年10月7日 周一10:17写道： > > > The new fury-parent release should be done using the exact same git > > commit as the rest of the 0.8.0 release. > > > > On Mon, 7 Oct 2024 at 17:16, PJ Fanning <[email protected]> wrote: > > > > > > A qualified yes. You can publish the missing fury-parent. > > > > > > Could you get someone to validate it though before releasing it? So > > > publish to staging area in Nexus (Nexus 'close') and then when > > > validated, release it. > > > > > > On Mon, 7 Oct 2024 at 16:01, Shawn Yang <[email protected]> wrote: > > > > > > > > In vote thread: > > > > https://lists.apache.org/thread/1l37kv1xtgrjh60psfjcyngfd4jctbrg we > > missed > > > > fury-parent pom.xml, this made fury 0.8.0 unusable. it has been issued > > by > > > > users in https://github.com/apache/fury/issues/1872. > > > > > > > > Since fury-parent pom.xml is just a convenience release, the source > > release > > > > is unaffected. Could we just publish this pom.xml to maven center > > directly > > > > without a fully new round vote process? Or is there a fast vote > > process for > > > > such situation? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
