Hi Andrew I agree. I propose to wait a month or so now 2.6.0 has been released. If there's no request/feedback, then we should start a formal vote imho.
Thanks ! Regards JB On Sun, Mar 10, 2024 at 7:58 AM Andrew Gaul <g...@apache.org> wrote: > > On Mon, Oct 10, 2022 at 10:03:07PM +0900, Andrew Gaul wrote: > > jclouds development has slowed from 123 commits from 26 contributors in > > 2018 to just 24 from 6 contributors in 2022. This is despite growing > > downloads over the last 12 months from 50,000 to 80,000 for jclouds-core > > alone. Unfortunately the number of active committers has shrunk and we > > will soon lack quorum for future releases. This means that the project > > must move to the Apache attic. > > > > Ideally the community could step up to sustain the project, e.g., > > reviewing pull requests, fixing issues, responding to mailing list > > queries, and eventually becoming committers themselves. Does anyone > > have a multi-year interest in jclouds that wants to help out? > > > > If not, I will cut a final 2.6.0 release before retiring the project. > > Revisiting this after the 2.6.0 release two years later, I believe more > strongly than ever that we should archive jclouds. I lack the domain > knowledge and enthusiasm to maintain the project and no one else has > stepped forward. Let's give users a month to report 2.6.0 regressions > then proceed with archiving if there are no showstoppers? > > -- > Andrew Gaul > http://gaul.org/
