Project status?

[OmriSama]

The project seems completely dead. The only Ruby version being seemingly tested against is 2.3.8 which is long EOL. Code coverage is <50%, and I don't see the authors or maintainers responding to any recent issues... Is this agent going to be updated? Replaced?

[mwjones-aws]

Yes, this project is still active. We have a release planned for May 2022.

[OmriSama]

@mwjones-aws It's May 31st and there still hasn't been a release. Is it postponed?

[mwjones-aws]

Yes, now targeting end of June

[mpdude]

Heads up: End of June approaching

[philstrong]

Behind the scenes, we've been dramatically improved our release and testing process to raise the bar for our customers. Due to the amount of work involved, our new target release date is September 2022. With the improved automation and confidence in our tests, our release velocity will increase.

Appreciate the patience

[mpdude]

@philstrong, @mwjones-aws and @keithcyu,

as you are probably aware (see #301 (comment) for an example), there are a few people here who have a personal interest in making sure you will have smooth roll-outs on various and/or up-to-date platforms and distros, and who are willing to help and contribute.

Given that the agent code is already open sourced here, maybe you can also publish the files necessary to do the packaging for various distros (e. g. debian/ for .deb files)? Maybe the community can help with scripting/automation to make more frequent or snapshot releases possible.

Additionally, this would improve transparency – it's good to hear that you are actively working on this, but your efforts currently are not visible, since there has been no progress in this repo here for a year. Maybe we can change that 🍻 .

[philstrong]

Agreed, we have a visibility problem. It would be ideal to include the packaging code, so the community can create their own builds. We perform unit tests, signing and integration tests, among other things, in other repos that aren't on GitHub. In part b/c it's testing our services that interact with the agent. Having said that, we do have the ability to perform unsigned builds from our machines.

We treat this repo as a mirror of our internal git repository, we can do a better job syncing those, so it's obvious where we're making changes between releases.

[mpdude]

We treat this repo as a mirror of our internal git repository, we can do a better job syncing those, so it's obvious where we're making changes between releases.

I was already assuming this. The problem with this "throwing things over the fence once in a while" approach is that it is not easy for outside people to contribute (assuming you're interested in that): You don't see how changes flow back, and its also not easy for you to integrate outside changes and avoid merge conflicts if the community does not see the current code.

Looking forward to see what you can change to improve that 🚀

[fleaz]

Behind the scenes, we've been dramatically improved our release and testing process

No offense, but we literally heard the exact same excuse over two years ago...

#239 (comment)

[kochul2000]

AWS team should at least warn this issue at the System manager Distributor. I wasted my time with the quietly failing distributor.

[sapphirecat]

Hi, just checking in. It's been over 45 days since the last comment, and even longer since the "end of June" with no updates (neither here, nor on #301.) What's the current plan?

[fleaz]

Hi, just checking in. It's been over 45 days since the last comment, and even longer since the "end of June" with no updates (neither here, nor on #301.) What's the current plan?

our new target release date is September 2022.

Just scroll a few comments further up

[sapphirecat]

Thanks, but I would still like to know what the current status is. Should I expect a September release, or are we looking at December now?

[mwjones-aws]

We're still targeting September.

[grant-veepshosting]

@mwjones-aws Is this issue fixed in the fresh v1.4.0 release? I can't see it in the release notes anywhere.
Will there be another release in September to fix the Ubuntu 22.04 compatibility issue?

[mwjones-aws]

@grant-veepshosting v1.4.0 does not add support for Ubuntu 22. Please track #301

[fleaz]

@mwjones-aws Can't find 1.4.0 in here. What's the purpose of this repository if it doesn't represent the current state of the code?

[mwjones-aws]

We'll commit it today or tomorrow

[t0shiii]

PR for 1.4.0 release can be found here: #332

[fleaz]

We have a release planned for May 2022.

now targeting end of June

our new target release date is September 2022

And now it's 2023... 😞

[mwjones-aws]

#318 (comment)

Version 1.4.1 has been released since then. #343

[fleaz]

Version 1.4.1 has been released since then. #343

Bot neither 1.4.0 nor 1.4.1 fixed the Ruby3 incompatibility, so users are still stuck at Ubuntu 20.04 :(

[mwjones-aws]

Bot neither 1.4.0 nor 1.4.1 fixed the Ruby3 incompatibility, so users are still stuck at Ubuntu 20.04 :(

I agree. We're tracking that specific effort on #301