Re: [VOTE] Release Maven Resolver 1.9.12
yes, same happened in 1.9.11: this is where I found this first, while checking for Reproducible Central https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/resolver/maven-resolver/README.md Yes, dropping your local repo would be nice to avoid such unexpected state Lately, umask has been a pain to Reproducible Builds: it gives much weight to an environment aspect, with Linux distros changing their default value recently. On Resolver 1.9.12, we have now multiple options: 1. drop 1.9.12 and go to 1.9.13: looks overkill to me 2. let 1.9.12 binaries as is: reasonable 3. rebuild a new staging repository from Git tag: I'd love this one to be at least thought a little bit before saying no Explanation: Given in reality the build itself is reproducible, but the reference build has just one file broken by your desktop environment, it means that if you "mvn -Papache-release deploy" from the Git tag, you'll get a new staging repository that will contain the same binaries (in particular the same -source-release.ziip and its sha512), just with a fixed maven-resolver-named-locks-redisson-1.9.12-bundle.zip The real files that will be different are the .asc files We could later decide if we release to Maven Central from current maven-1962 or the new one Are you ready to try? (and discover one of the nice benefit of Reproducible Builds...) Regards, Hervé Le vendredi 16 juin 2023, 19:23:14 CEST Tamás Cservenák a écrit : > Found it: that above is my laptop, while I did (both) release on my desktop: > > [cstamas@urnebes ~]$ cd .m2/repository-oss/org/objenesis/objenesis/3.3/ > [cstamas@urnebes 3.3]$ ll > total 68 > -rw---. 1 cstamas cstamas 49423 2022 dec 15 objenesis-3.3.jar > -rw---. 1 cstamas cstamas40 2022 dec 15 objenesis-3.3.jar.sha1 > -rw---. 1 cstamas cstamas 3007 2022 dec 15 objenesis-3.3.pom > -rw---. 1 cstamas cstamas40 2022 dec 15 objenesis-3.3.pom.sha1 > -rw---. 1 cstamas cstamas 192 2022 dec 15 _remote.repositories > [cstamas@urnebes 3.3]$ > > Hence, the same should be true for 1.9.11 as well. Also, it seems it's time > to nuke my local repo ;) > > Thanks > T > > On Fri, Jun 16, 2023 at 7:16 PM Tamás Cservenák wrote: > > Strange > > > > [cstamas@blondie ~]$ cd .m2/repository-oss/org/objenesis/objenesis/3.3/ > > [cstamas@blondie 3.3]$ ll > > total 68 > > -rw-r--r--. 1 cstamas cstamas 49423 dec 20 17.30 objenesis-3.3.jar > > -rw-r--r--. 1 cstamas cstamas40 dec 20 17.30 objenesis-3.3.jar.sha1 > > -rw-r--r--. 1 cstamas cstamas 3007 dec 20 17.30 objenesis-3.3.pom > > -rw-r--r--. 1 cstamas cstamas40 dec 20 17.30 objenesis-3.3.pom.sha1 > > -rw-r--r--. 1 cstamas cstamas 192 dec 20 17.30 _remote.repositories > > [cstamas@blondie 3.3]$ > > > > Herve, while at this, please can you check 1.9.11 as well? IMHO there must > > be the same issue present, or if not, am even more puzzled... > > > > T > > > > On Fri, Jun 16, 2023 at 7:13 PM Hervé Boutemy > > > > wrote: > >> +1 > >> > >> notice that Reproducible Builds is NOT ok on 1 file: reference build done > >> on > >> *nix with JDK 17 and umask 022 > >> > >> the only issue is in > >> maven-resolver-named-locks-redisson-1.9.12-bundle.zip: > >> │--rw--- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar > >> │+-rw-r--r-- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar > >> it seems your local repository contains a objenesis-3.3.jar which is not > >> group > >> nor world wide readable > >> > >> Regards, > >> > >> Hervé > >> > >> Le vendredi 16 juin 2023, 15:57:43 CEST Tamás Cservenák a écrit : > >> > Howdy, > >> > >> > We solved 1 issue: > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628 > >> >> > >> > rsion=12353340 > >> > > >> > There are still some issues in JIRA: > >> > https://issues.apache.org/jira/projects/MRESOLVER/issues > >> > > >> > Staging repository: > >> > https://repository.apache.org/content/repositories/maven-1962/ > >> > >> > Source release SHA512: > >> b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924 > >> 782>> > >> > ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce > >> > > >> > Staging site: > >> > https://maven.apache.org/resolver-archives/resolver-LATEST/ > >> > > >> > Guide to testing staged releases: > >> > https://maven.apache.org/guides/development/guide-testing-releases.html > >> > > >> > Vote open for 72 hours. > >> > > >> > [ ] +1 > >> > [ ] +0 > >> > [ ] -1 > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 1.9.12
Found it: that above is my laptop, while I did (both) release on my desktop: [cstamas@urnebes ~]$ cd .m2/repository-oss/org/objenesis/objenesis/3.3/ [cstamas@urnebes 3.3]$ ll total 68 -rw---. 1 cstamas cstamas 49423 2022 dec 15 objenesis-3.3.jar -rw---. 1 cstamas cstamas40 2022 dec 15 objenesis-3.3.jar.sha1 -rw---. 1 cstamas cstamas 3007 2022 dec 15 objenesis-3.3.pom -rw---. 1 cstamas cstamas40 2022 dec 15 objenesis-3.3.pom.sha1 -rw---. 1 cstamas cstamas 192 2022 dec 15 _remote.repositories [cstamas@urnebes 3.3]$ Hence, the same should be true for 1.9.11 as well. Also, it seems it's time to nuke my local repo ;) Thanks T On Fri, Jun 16, 2023 at 7:16 PM Tamás Cservenák wrote: > Strange > > [cstamas@blondie ~]$ cd .m2/repository-oss/org/objenesis/objenesis/3.3/ > [cstamas@blondie 3.3]$ ll > total 68 > -rw-r--r--. 1 cstamas cstamas 49423 dec 20 17.30 objenesis-3.3.jar > -rw-r--r--. 1 cstamas cstamas40 dec 20 17.30 objenesis-3.3.jar.sha1 > -rw-r--r--. 1 cstamas cstamas 3007 dec 20 17.30 objenesis-3.3.pom > -rw-r--r--. 1 cstamas cstamas40 dec 20 17.30 objenesis-3.3.pom.sha1 > -rw-r--r--. 1 cstamas cstamas 192 dec 20 17.30 _remote.repositories > [cstamas@blondie 3.3]$ > > Herve, while at this, please can you check 1.9.11 as well? IMHO there must > be the same issue present, or if not, am even more puzzled... > > T > > On Fri, Jun 16, 2023 at 7:13 PM Hervé Boutemy > wrote: > >> +1 >> >> notice that Reproducible Builds is NOT ok on 1 file: reference build done >> on >> *nix with JDK 17 and umask 022 >> >> the only issue is in >> maven-resolver-named-locks-redisson-1.9.12-bundle.zip: >> │--rw--- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar >> │+-rw-r--r-- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar >> it seems your local repository contains a objenesis-3.3.jar which is not >> group >> nor world wide readable >> >> Regards, >> >> Hervé >> >> Le vendredi 16 juin 2023, 15:57:43 CEST Tamás Cservenák a écrit : >> > Howdy, >> > >> > We solved 1 issue: >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628 >> > rsion=12353340 >> > >> > There are still some issues in JIRA: >> > https://issues.apache.org/jira/projects/MRESOLVER/issues >> > >> > Staging repository: >> > https://repository.apache.org/content/repositories/maven-1962/ >> > >> > Source release SHA512: >> > >> b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782 >> > ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce >> > >> > Staging site: >> > https://maven.apache.org/resolver-archives/resolver-LATEST/ >> > >> > Guide to testing staged releases: >> > https://maven.apache.org/guides/development/guide-testing-releases.html >> > >> > Vote open for 72 hours. >> > >> > [ ] +1 >> > [ ] +0 >> > [ ] -1 >> >> >> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >>
Re: [DISCUSS] POM model version
Le mercredi 14 juin 2023, 10:07:46 CEST Guillaume Nodet a écrit : > I think this is exactly what Hervé explains was rejected years ago. The > assumption is that the POM v4 is "set in amber" and will never change, at > least for the consumer side, i.e. defining dependencies. For the build > side, it has to evolve, so the POM v5 will need a different schema url or > version. But imho the goals are: > * make sure we keep POM v4 the way it is to tools for consumers > * allow some room for POM v5 on the build side > > However, the problem I see is that when you deploy a "pom" package, i.e. a > parent POM that may be used as a parent for other projects, we clearly have > a problem for which I do not really have a clear understanding how to > solve. Let's assume this POM uses a POM v5 new feature, so that the > semantic data carried by this POM can not be written with a POM v4. Such a > POM can not be uploaded to maven central in the v4 form, so it WILL break > tools, but I don't really see any other way. > > So here's what I propose: > * further trim down the consumer POM as it was envisioned years ago in > [1] and [2] (the removed data will still be available for other tools to > consume, see below) > * we want to relax the constraints of the v4 pom schema a bit to be able > to validate the current build pom (where a few things are inferred) > * for packaged artifacts, we will upload the consumer POM v4 as the main > POM and the normalized POM v4/v5 as an attached artifact > * for the "pom" package, we will upload the normalized POM v4/v5 as the > main POM (no consumer POM) > > In the short term we could then: > * allow the definition of POM v4.x, i.e. small evolutions with a schema > compatible to v4 (i.e. mostly new elements / attributes) that will give a > bit of freedom to implement new stuff (i.e. we should start properly > versioning it and communicate to the community that they will have to adapt > their tools) > * when deploying the v4/v5 POM as the main POM (i.e. for pom packages), > we could be smart enough to see if the POM requires non v4 features and if > that's not the case, upload it as a the lower version possible (i.e. POM > v4), thereby minimizing disruption for other tools scanning central (and > allow consumption with maven 3.x) > Longer term: > * define a POM v5+ schema (with GAV as attributes, etc...) > > Thoughts ? ok for new attributes, that can simply added in POM v4.2 not ok for new elements: new elements are POM v5, with all the subtle choices to be done that you listed but I still did not have time to properly evaluate, and all the people who should really take time to evaluate. Notably those who will have to adapt publication rules to Maven Central for POM v5. Regards, Hervé > > Guillaume > > [1] https://maven.apache.org/studies/consumer-pom/maven.html > [2] https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM > > Le mer. 14 juin 2023 à 08:48, Hunter C Payne > > a écrit : > > Sorry for chiming in again but perhaps I might have an idea. The XSD > > > > schema that a POM uses is actually referenced from the POM. So in essence > > each POM carries with it what is needed to know to parse it. Perhaps in > > Maven 5 (or whichever version) we can require POM parsers to read and use > > the specific XSD schema referenced in the POM. That way you can have more > > room to try changes to the POM format. But there really should be a > > mechanism for pushing POM changes downstream and XSD seems like a good > > option for that. Sorry if this is already the plan and I'm repeating what > > is already known. > > > > Hunter > > > > On Tuesday, June 13, 2023 at 11:12:39 PM PDT, Hervé Boutemy < > > > > herve.bout...@free.fr> wrote: > > Le lundi 12 juin 2023, 01:50:56 CEST Guillaume Nodet a écrit : > > > > Don't look at Maven code to judge: the whole logic is based on "known > > > > unknown" > > > > = we don't know who parses POMs published to Maven Central, but there > > > > are > > > > > > many > > > > (it's easy to cite many, but not all). > > > > > > I can't buy that argument. You're saying that we should not assume the > > > > way > > > > > the POM is parsed, but we assume they don't parse arguments. That's > > > clearly dodgy, and false for our own parser (both are parsed and > > > rejected > > > in strict mode and silently ignored in lenient mode). > > > > I can understand that it does not match the precision of your logic based > > on > > todays code: did you look at Maven 2 code? did you look at every other > > consumer of Maven Central content? > > > > whatever you feel about it today, that's what has been defined and done > > for now > > more than 15 years, and proven working, and AFAIK checked when publishing > > to > > Maven Central > > > > If we change that, we are changing the Maven Central contract for > > everybody > > from the past and future > > > > Maven 5 is not only about Maven: it's also
Re: [VOTE] Release Maven Resolver 1.9.12
Strange [cstamas@blondie ~]$ cd .m2/repository-oss/org/objenesis/objenesis/3.3/ [cstamas@blondie 3.3]$ ll total 68 -rw-r--r--. 1 cstamas cstamas 49423 dec 20 17.30 objenesis-3.3.jar -rw-r--r--. 1 cstamas cstamas40 dec 20 17.30 objenesis-3.3.jar.sha1 -rw-r--r--. 1 cstamas cstamas 3007 dec 20 17.30 objenesis-3.3.pom -rw-r--r--. 1 cstamas cstamas40 dec 20 17.30 objenesis-3.3.pom.sha1 -rw-r--r--. 1 cstamas cstamas 192 dec 20 17.30 _remote.repositories [cstamas@blondie 3.3]$ Herve, while at this, please can you check 1.9.11 as well? IMHO there must be the same issue present, or if not, am even more puzzled... T On Fri, Jun 16, 2023 at 7:13 PM Hervé Boutemy wrote: > +1 > > notice that Reproducible Builds is NOT ok on 1 file: reference build done > on > *nix with JDK 17 and umask 022 > > the only issue is in maven-resolver-named-locks-redisson-1.9.12-bundle.zip: > │--rw--- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar > │+-rw-r--r-- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar > it seems your local repository contains a objenesis-3.3.jar which is not > group > nor world wide readable > > Regards, > > Hervé > > Le vendredi 16 juin 2023, 15:57:43 CEST Tamás Cservenák a écrit : > > Howdy, > > > > We solved 1 issue: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628 > > rsion=12353340 > > > > There are still some issues in JIRA: > > https://issues.apache.org/jira/projects/MRESOLVER/issues > > > > Staging repository: > > https://repository.apache.org/content/repositories/maven-1962/ > > > > Source release SHA512: > > > b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782 > > ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce > > > > Staging site: > > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Resolver 1.9.12
+1 notice that Reproducible Builds is NOT ok on 1 file: reference build done on *nix with JDK 17 and umask 022 the only issue is in maven-resolver-named-locks-redisson-1.9.12-bundle.zip: │--rw--- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar │+-rw-r--r-- 2.0 unx49423 b- defN 23-Jun-16 13:32 objenesis-3.3.jar it seems your local repository contains a objenesis-3.3.jar which is not group nor world wide readable Regards, Hervé Le vendredi 16 juin 2023, 15:57:43 CEST Tamás Cservenák a écrit : > Howdy, > > We solved 1 issue: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628 > rsion=12353340 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1962/ > > Source release SHA512: > b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782 > ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 1.9.12
+1 Le ven. 16 juin 2023 à 16:07, Sylwester Lachiewicz a écrit : > +1 > > pt., 16 cze 2023, 16:02 użytkownik Guillaume Nodet > napisał: > > > +1 > > > > Le ven. 16 juin 2023 à 15:58, Tamás Cservenák a > > écrit : > > > > > Howdy, > > > > > > We solved 1 issue: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353340 > > > > > > There are still some issues in JIRA: > > > https://issues.apache.org/jira/projects/MRESOLVER/issues > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/maven-1962/ > > > > > > Source release SHA512: > > > > > > > > > b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce > > > > > > Staging site: > > > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > > > > > Guide to testing staged releases: > > > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Vote open for 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > > > > -- > > > > Guillaume Nodet > > >
Re: [VOTE] Release Maven Resolver 1.9.12
+1 pt., 16 cze 2023, 16:02 użytkownik Guillaume Nodet napisał: > +1 > > Le ven. 16 juin 2023 à 15:58, Tamás Cservenák a > écrit : > > > Howdy, > > > > We solved 1 issue: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353340 > > > > There are still some issues in JIRA: > > https://issues.apache.org/jira/projects/MRESOLVER/issues > > > > Staging repository: > > https://repository.apache.org/content/repositories/maven-1962/ > > > > Source release SHA512: > > > > > b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce > > > > Staging site: > > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > -- > > Guillaume Nodet >
Re: [VOTE] Release Maven Resolver 1.9.12
+1 Le ven. 16 juin 2023 à 15:58, Tamás Cservenák a écrit : > Howdy, > > We solved 1 issue: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353340 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1962/ > > Source release SHA512: > > b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Guillaume Nodet
[VOTE] Release Maven Resolver 1.9.12
Howdy, We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353340 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repository: https://repository.apache.org/content/repositories/maven-1962/ Source release SHA512: b24cbd998e1739a89eb693b764fef9f476d53a5b1546ffb87941afcdc9c76bdcd69cbf924782ded6067388679446c25c166364cd9ac450e8ef17a70d3f1045ce Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1
[ANN] Maven Indexer 7.0.3 released
The Apache Maven team is pleased to announce the release of the Maven Indexer 7.0.3 https://maven.apache.org/maven-indexer/ Release Notes - Maven Indexer - Version 7.0.3 ** Improvement * [MINDEXER-190] - Avoid use of String#split in hot code * [MINDEXER-191] - Avoid group rebuilding during incremental updates ** Task * [MINDEXER-192] - Update build plugins ** Dependency upgrade * [MINDEXER-189] - Upgrade to Lucene 9.6.0 * [MINDEXER-193] - Update dependencies Have fun, -The Apache Maven team
[ANN] Maven Shade Plugin 3.5.0 released
The Apache Maven team is pleased to announce the release of the Maven Shade Plugin 3.5.0 https://maven.apache.org/plugins/maven-shade-plugin/ Release Notes - Maven Shade Plugin - Version 3.5.0 ** Bug * [MSHADE-443] - Fix problems with shadeSourcesContent ** New Feature * [MSHADE-400] - Self-minimisation with custom entry points ** Task * [MSHADE-438] - Update to Maven 3.2.5 * [MSHADE-450] - Upgrade to parent POM 39, reformat ** Dependency upgrade * [MSHADE-446] - Update dependencies * [MSHADE-447] - Move off forked Guice * [MSHADE-448] - Upgrade ASM to 9.5 * [MSHADE-449] - Upgrade plexus-utils to 3.5.1 Have fun, -The Apache Maven team
[ANN] Maven Resolver 1.9.11 released
The Apache Maven team is pleased to announce the release of the Maven Resolver 1.9.11 https://maven.apache.org/resolver/ Release Notes - Maven Resolver - Version 1.9.11 ** Bug * [MRESOLVER-361] - Unreliable TCP and retries on upload ** New Feature * [MRESOLVER-353] - Make aether.checksums.algorithms settable per remote repository * [MRESOLVER-370] - Lock factory should dump lock states on failure ** Task * [MRESOLVER-356] - Remove Guava (is unused) * [MRESOLVER-364] - Revert MRESOLVER-132 * [MRESOLVER-366] - Upgrade build plugins ** Dependency upgrade * [MRESOLVER-365] - Upgrade dependencies * [MRESOLVER-367] - upgrade redisson in named locks and simplify installation Have fun, -The Apache Maven team
TAC Applications for Community Over Code North America and Asia now open
Hi All, (This email goes out to all our user and dev project mailing lists, so you may receive this email more than once.) The Travel Assistance Committee has opened up applications to help get people to the following events: *Community Over Code Asia 2023 - * *August 18th to August 20th in Beijing , China* Applications for this event closes on the 6th July so time is short, please apply as soon as possible. TAC is prioritising applications from the Asia and Oceania regions. More details on this event can be found at: https://apachecon.com/acasia2023/ More information on how to apply please read: https://tac.apache.org/ *Community Over Code North America - * *October 7th to October 10th in Halifax, Canada* Applications for this event closes on the 22nd July. We expect many applications so please do apply as soon as you can. TAC is prioritising applications from the North and South America regions. More details on this event can be found at: https://communityovercode.org/ More information on how to apply please read: https://tac.apache.org/ *Have you applied to be a Speaker?* If you have applied or intend to apply as a Speaker at either of these events, and think you may require assistance for Travel and/or Accommodation - TAC advises that you do not wait until you have been notified of your speaker status and to apply early. Should you not be accepted as a speaker and still wish to attend you can amend you application to include Conference fees, or, you may withdraw your application. The call for presentations for Halifax is here: https://communityovercode.org/call-for-presentations/ and you have until the 13th of July to apply. The call for presentations for Beijing is here: https://apachecon.com/acasia2023/cfp.html and you have until the 18th June to apply. *IMPORTANT Note on Visas:* It is important that you apply for a Visa as soon as possible - do not wait until you know if you have been accepted for Travel Assistance or not, as due to current wait times for Interviews in some Countries, waiting that long may be too late, so please do apply for a Visa right away. Contact tac-ap...@tac.apache.org if you need any more information or assistance in this area. *Spread the Word!!* TAC encourages you to spread the word about Travel Assistance to get to these events, so feel free to repost as you see fit on Social Media, at work, schools, universities etc etc... Thank You and hope to see you all soon Gavin McDonald on behalf of the ASF Travel Assistance Committee.
[RESULT][VOTE] Release Maven Indexer 7.0.3
Howdy, The vote has passed with the following result: +1: Guillaume, Slawomir, Tamas, Sylwester PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central repo. Thanks T
[RESULT][VOTE] Release Maven Shade Plugin 3.5.0
Howdy, The vote has passed with the following result: +1: Slawomir, Guillaume, Romain, Olivier, Sylwester PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central repo. Thanks T
[RESULT][VOTE] Release Maven Resolver 1.9.11
Howdy, The vote has passed with the following result: +1: Sylwester, Slawomir, Guillaume PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central repo. Thanks T
