Re: Little "upsie" at the Wayang podling

As others have said, there’s no way to retract a release when it’s gone to Maven Central. (Many of us have noticed show-stopping bugs just after the release.) The only remedy is to make a superseding release. I don’t support adding a step where an IPMC member presses the release button.

AW: Little "upsie" at the Wayang podling

(Also fixed what my mail client thought I wanted to say, to what I said in the subject ;-) ) And I think the main problem with the leftpad was the general usage of the Maven equivalent of “LATEST” as a dependency version. So, anyone with a LATEST dependency that has built today, will have the

[RESULT] [VOTE] IP Clearance of Pekko HTTP CORS code donation

The vote passes by lazy consensus. https://lists.apache.org/thread/m7vm57jwk9r4o2knmgmtfk19dd8wrsbs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: Little "upside" at the Wayang podling

The difference here is that this release has just been made and has only been announced on the Wayang dev list. I find no evidence of it on the Wayang web site nor in the Apache announce mailing list. I understand the leftpad case but I don't think this is a similar case. Users who have upgraded

Re: Little "upside" at the Wayang podling

>So I guess we have to check how we can remove the artifacts. A central repository should not _remove_ artifacts. Rust's cargo crate can mark as yanked and prevent further dependent but remain all the existing one. Revoke artifacts can cause significant downstream effect - you may take leftpad on

AW: Little "upside" at the Wayang podling

Hi PJ, Unfortunately, I had to vote -1 on the release and there’s no way on earth it would pass Justin ;-) … So, there will be another one. So I guess we have to check how we can remove the artifacts. Chris Von: PJ Fanning Datum: Dienstag, 25. Juli 2023 um 11:47 An:

Re: [VOTE] Retire Apache Tuweni

+1 Thanks for your effort! On 25 Jul 2023 Tue at 12:30 PJ Fanning wrote: > +1 > > Best of luck with the non-ASF version of Tuweni. > > On 2023/07/24 05:31:41 Antoine Toulme wrote: > > Hello all, > > Tuweni has been incubating since 2019-03-25. > > > > Since 2022, activity has been low, and the

Re: Little "upside" at the Wayang podling

The same thing occurred in Spark 3.1.0[1], and they choose to treat it as an invalid version, which may be a good example to follow up. [1] https://spark.apache.org/news/next-official-release-spark-3.1.1.html Thanks, Cheng Pan > On Jul 25, 2023, at 17:28, Christofer Dutz wrote: > > Hi

Re: Little "upside" at the Wayang podling

It does seem like a good idea to do a 2 phase release to the Apache Nexus Repository. I think a lot of Apache projects use that approach. It means that the binary artifacts can be checked during the release voting along side the source release. Nexus allows you the drop the artifacts or to

Re: [VOTE] Retire Apache Tuweni

+1 Best of luck with the non-ASF version of Tuweni. On 2023/07/24 05:31:41 Antoine Toulme wrote: > Hello all, > Tuweni has been incubating since 2019-03-25. > > Since 2022, activity has been low, and the chances of attracting new > committers and building a vibrant community seem very slim at

Little "upside" at the Wayang podling

Hi all, yesterday the Wayang podling was following the “release documentation” of a TLP and “forgot” to do the round over the IPMC. However, they’ve already moved things to the release distro area (from where they’ve removed it after me contacting them) but in Nexus they clicked on “release”