I guess as soon as I’m back from the conference, I’ll initiate the next release.
Chris Von: Craig Russell <[email protected]> Datum: Mittwoch, 3. April 2024 um 15:14 An: [email protected] <[email protected]> Betreff: Re: Preparation for next release Hey, I'm still here... Craig > On Apr 2, 2024, at 23:58, Christofer Dutz <[email protected]> wrote: > > Ok … no reply? > > Not quite sure If I should take over preparing the release as I’m not sure If > we even would have enough folks to vote. > > So, who’s here and able and willing to review a next release? > > > Chris > > > Von: Christofer Dutz <[email protected]> > Datum: Dienstag, 26. März 2024 um 10:50 > An: [email protected] <[email protected]> > Betreff: AW: Preparation for next release > Ok … so I just wanted to create a new presentation using the archetype and > noticed: > Hey … wasn’t there a release in progress? … So, what’s the status on this? > > @Mirko, you want me to do the release? > > Chris > > > Von: Christofer Dutz <[email protected]> > Datum: Dienstag, 13. Februar 2024 um 16:14 > An: [email protected] <[email protected]> > Betreff: AW: Preparation for next release > Hi Mirko, > > for some reason this email completely slipped my attention. > I just noticed in the repo, that there were release-related commits. > > Sorry for not having reacted any sooner. > > What can I help you with? > > Chris > > > > Von: Mirko Kämpf <[email protected]> > Datum: Donnerstag, 8. Februar 2024 um 16:13 > An: [email protected] <[email protected]> > Betreff: Re: Preparation for next release > Hi Christofer, > > I prepared a release of the "tools" subproject on my machine. > > Currently I am blocked by an authorization error as shown in the attached > logs. > Creation of a key for signing a release is done and I think, once we have > checked > the permissions for my account ([email protected]) we can finish this task > soon. > > Regarding a call, would it work for you at some time tomorrow between 8:00 > and 12:30 > or between 13:30 and 15:00? > > I am available. You can also send an email directly to > [email protected] > > Thanks, > Mirko > > > > [INFO] [DEBUG] Attaching for deploy: > org.apache.training:training-tools:zip:source-release:1.1.0 > [INFO] [DEBUG] Attaching for deploy: > org.apache.training:training-tools:zip.sha512:source-release:1.1.0 > [INFO] [DEBUG] Attaching for deploy: > org.apache.training:training-tools:pom.asc:1.1.0 > [INFO] [DEBUG] Attaching for deploy: > org.apache.training:training-tools:zip.asc:source-release:1.1.0 > [INFO] [DEBUG] Using transporter HttpTransporter with priority 5.0 for > https://repository.apache.org/service/local/staging/deploy/maven2 > [INFO] [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 > for https://repository.apache.org/service/local/staging/deploy/maven2 with > [email protected], password=*** > [INFO] Uploading to apache.releases.https: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/training/training-tools/1.1.0/training-tools-1.1.0.pom > [INFO] Uploading to apache.releases.https: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/training/training-tools/1.1.0/training-tools-1.1.0-source-release.zip > [INFO] Uploading to apache.releases.https: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/training/training-tools/1.1.0/training-tools-1.1.0-source-release.zip.sha512 > [INFO] Uploading to apache.releases.https: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/training/training-tools/1.1.0/training-tools-1.1.0.pom.asc > [INFO] Uploading to apache.releases.https: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/training/training-tools/1.1.0/training-tools-1.1.0-source-release.zip.asc > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Reactor Summary for Training: Tools 1.1.0: > [INFO] [INFO] > [INFO] [INFO] Training: Tools .................................... FAILURE > [ 6.381 s] > [INFO] [INFO] Training: Tools: Content Archetype ................. SKIPPED > [INFO] [INFO] Training: Tools: Content Master Resources .......... SKIPPED > [INFO] [INFO] Training: Tools: Content Master Pom ................ SKIPPED > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 6.641 s > [INFO] [INFO] Finished at: 2024-02-08T16:02:21+01:00 > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy (default-deploy) > on project training-tools: Failed to deploy artifacts: Could not transfer > artifact org.apache.training:training-tools:pom:1.1.0 from/to > apache.releases.https ( > https://repository.apache.org/service/local/staging/deploy/maven2): status > code: 401, reason phrase: Unauthorized (401) -> [Help 1] > [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy > (default-deploy) on project training-tools: Failed to deploy artifacts: *Could > not transfer artifact org.apache.training:training-tools:pom:1.1.0 from/to > apache.releases.https > (https://repository.apache.org/service/local/staging/deploy/maven2 > <https://repository.apache.org/service/local/staging/deploy/maven2>): > status code: 401, reason phrase: Unauthorized (401)* > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 > (MojoExecutor.java:333) > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute > (MojoExecutor.java:316) > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:212) > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:174) > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 > (MojoExecutor.java:75) > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor$1.run > (MojoExecutor.java:162) > [INFO] at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute > (DefaultMojosExecutionStrategy.java:39) > [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:159) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:105) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:73) > [INFO] at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:53) > [INFO] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:118) > [INFO] at org.apache.maven.DefaultMaven.doExecute > (DefaultMaven.java:261) > [INFO] at org.apache.maven.DefaultMaven.doExecute > (DefaultMaven.java:173) > [INFO] at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101) > [INFO] at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906) > > > > Am Do., 8. Feb. 2024 um 07:55 Uhr schrieb Christofer Dutz < > [email protected]>: > >> Hi Mirko, >> >> I live near Frankfurt, so similar timezone ;-) >> >> I’d be happy to join an online meeting for discussing things. >> >> Chris >> >> >> Von: Mirko Kämpf <[email protected]> >> Datum: Dienstag, 6. Februar 2024 um 22:50 >> An: [email protected] <[email protected]> >> Betreff: Preparation for next release >> Hey, Apache Training community, >> >> We are in the process of releasing a new version of the Apache Training >> project. >> >> All open PRs are closed. >> We will kick off the procedure tomorrow or on Thursday. >> >> >> *Now I will share some of my thoughts about the status and the future of >> the project.* >> Based on last year's idea: - Can we link the "training idea" to other ASF >> projects? - I tried connecting the Apache Training project with one >> particular ASF project: Apache Wayang. >> We worked on a proposal for a talk at the next ASF conference in >> Bratislava. >> The proposal has been shared here on the list and is still under review. >> >> No matter what the result will be, in case we can present, I would like to >> know a bit more about the Apache Training community goals, going forward. >> >> What do you think about a call or a "project focused conference"? >> >> Where do the people of this community live? >> Would you be available for a 1 h session in March 2024? >> If yes, what time? >> >> First, I suggest we should figure out a time slot and a day for a virtual >> meeting. >> >> By getting in touch with each other, we probably are able to collect our >> ideas (preparation phase, I volunteer to coordinate this) and then, once we >> know each other, we can clearly see what the future can bring to us. >> >> Last year, there was the one question: Should the project be retired? >> I personally said: No. This is not the right time to do this. But even >> after one year, >> I do not feel that we clearly know what direction we want to steer this >> project. >> >> My idea of "implementing the OKR process" obviously failed. Sorry, but >> it was also an interesting learning on my end. >> >> And in order to bring a bit more clarity, I would be so happy to get to >> know the people in the project which I do not yet know, and most of all, I >> would love to learn about your motivation, so that we can choose the next >> steps wisely. >> >> For now, we will organize a new release - one more step to survive. >> But after that we should find out a mid term plan and a strategy. >> >> Have a good time, and >> Cheers, >> Mirko >> >> -- >> >> Dr. rer. nat. Mirko Kämpf >> Müchelner Str. 23 >> 06259 Frankleben >> > > > -- > > Dr. rer. nat. Mirko Kämpf > Müchelner Str. 23 > 06259 Frankleben Craig L Russell [email protected]
