Looks like at the moment, I am the de facto volunteer to push the Axiom release forward.
I am new here, so I am reading the docs and the commit history of the project. I am new to the Apache release process too so please bear with me. I am getting everything together so I can send a vote email like the last one below. Should be soon. https://www.mail-archive.com/dev@ws.apache.org/msg08693.html Regards. Bobert On Fri, Jun 18, 2021 at 6:46 AM robertlazarski <robertlazar...@gmail.com> wrote: > Update: I was nominated to the Webservices project PMC and I received the > required +3 votes and no -1 votes. Thanks all. > > I confirmed my commit privileges by merging a Github dependabot pull > request regarding the latest Jetty version. I then merged every other valid > pull request. > > I have been building the latest Axiom source code from git, to generate > the local snapshots that I need for Axis2 development. I have reviewed the > recent Axiom commits. The vast majority have been dependency updates. > > I'd like to proceed with an Axiom release. The next step I believe would > be the release vote email, per the Apache foundation rules. There may be > additional steps per this project's guidelines. Please advise if so. > > If there are no other volunteers - such as Andreas who has done a > tremendous job on the most recent releases of both Axiom and Axis2 - then I > volunteer myself to step up and push the release forward. > > Regards, > Robert > > > > On Mon, Jun 7, 2021 at 4:42 AM robertlazarski <robertlazar...@gmail.com> > wrote: > >> >> >> On Fri, Jun 4, 2021 at 5:51 AM Daniel Kulp <dk...@apache.org> wrote: >> >>> Robert, >>> >>> On May 25, 2021, at 9:38 AM, robertlazarski <robertlazar...@gmail.com> >>> wrote: >>> I'd be willing to become a committer to help push an Axiom release >>> forward. >>> >>> >>> You already are a committer. You are in the ws LDAP group so you >>> should be able to make changes to Axiom, build the release, etc…. Only the >>> parts that require PMC would be an issue. >>> >>> >> Thanks for the reply. I thought I might be, however I didn't see my name >> in either of these two places. >> >> https://ws.apache.org/team-list.html >> https://ws.apache.org/axiom/team-list.html >> >> Furthermore, Axis needs to file a quarterly report to the Apache board >>> next week. Project chairs are required to subscribe to the board list, and >>> my take is that a large portion of what the board does is roll calls on low >>> activity projects. Moving projects to the attic happens every month. >>> >>> I mention that because I don't want to have to put things in the Axis >>> board report such as "we are awaiting an Axiom release but got no response >>> on their dev list". >>> >>> >>> The main issue is that the “Active” folks on WS are generally from the >>> CXF/Camel ecosystems which don’t use Axiom. A roll call would likely find >>> 3 active people as we DO do wss4j releases quite often as CXF generally >>> needs them. I do plan on doing XmlSchema and T releases soon (I’m >>> testing and updating things for Java17). Thus, getting releases of the >>> components that are shared with CXF is generally done in a timely manner as >>> they need them. Axiom (and Woden) would be much harder. >>> >>> There is the question of whether Axiom and Woden would be better served >>> by moving them from WebServices to the Axis project, but that seems a bit >>> heavy handed and something I’d prefer not doing as it can cause a variety >>> of other problems for users (like Maven coordinate changes). Since you >>> are a committer already, it would be great if you could help out on the >>> Axiom/Woden side, and maybe encourage Axis folks to start submitting pull >>> requests and such here and getting involved here. I’d love to be able to >>> vote more of them in as committers and PMC members. >>> >>> >>> Dan >>> >>> >>> >> I see. Axis2 has dependencies on XmlSchema, Neethi, Axiom and Woden. The >> problem for us at the moment is Axiom, since Axis2 will only compile on the >> latest snapshot - it won't compile on the latest official release. >> >> There is some urgency for Axis2 on an Axiom release. Our users have their >> security scanners sending them CVE alerts due to the outdated dependencies >> from our 2018 release. We are getting asked for a release on the Axis2 dev >> list and with Jira issues about once a week. >> >> Of course, we are all volunteers. Axis also has committer growth problems >> too - something we are trying to fix by focusing our new development on >> REST and JSON instead of SOAP. >> >> I created a Jira issue, AXIOM-506. However that is not required for an >> Axiom release. >> >> AFAIK, Andreas Veithen previously pushed Axiom releases. He has >> contributed quite a bit to Axis as well. It'd be great if he could >> participate in these upcoming releases however I feel we need to proceed >> one way or another. >> >> Thanks, >> Robert >> >> On Fri, May 14, 2021 at 10:44 AM robertlazarski <robertlazar...@gmail.com> >>> wrote: >>> >>>> Hello Web Services project, >>>> >>>> I am the current chair of Axis, and the Axis2 Java project is preparing >>>> for an upcoming release of 1.8. >>>> >>>> Axis2 requires snapshots builds of these Web Services projects below. >>>> Ideally, Axis2 wouldn't release with snapshots since the source of the >>>> release would compile with changing dependencies. >>>> >>>> neethi: 3.1.2-SNAPSHOT >>>> woden.version: 1.0M11-SNAPSHOT >>>> axiom.version: 1.3.0-SNAPSHOT >>>> >>>> Axis2 builds ok with neethi 3.1.1 and woden.version 1.0M10; so really >>>> we just need an Axiom release. >>>> >>>> BTW, I am trying to upgrade Axis2 to the current Glassfish release, >>>> 3.0.1. Concerning Axiom, the problem is that one of our Axis2 classes >>>> extends the Axiom DataHandlerWrapper class. >>>> >>>> I got stuck on the xjc tests, so I created AXIOM-506 that lists the >>>> steps I took. >>>> >>>> Thanks, >>>> Robert >>>> >>> >>> -- >>> Daniel Kulp >>> dk...@apache.org - http://dankulp.com/blog >>> Talend - http://talend.com <http://coders.talend.com> >>> >>>
