Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Cadence #390

Open
alberk8 opened this issue May 30, 2024 · 6 comments
Open

Release Cadence #390

alberk8 opened this issue May 30, 2024 · 6 comments
Labels
feature New feature or enhancement request

Comments

@alberk8
Copy link

alberk8 commented May 30, 2024

Since Eclipse foundation took over this project, I don't see a whole lot of commits or development. Is there a roadmap or release cadence as to what is planned?

@alberk8 alberk8 added the feature New feature or enhancement request label May 30, 2024
@fdesbiens
Copy link

Hi @alberk8.

Right now, we are still in a transition phase. The team will address CVEs but will otherwise not tackle new feature development. We focused our efforts on finding ways to properly support future safety certifications going forward. This took way more time than expected.

You can expect an official update from the Foundation soon. Please subscribe to the general ThreadX mailing list to stay in touch. You will need an Eclipse Foundation account to subscribe.

https://accounts.eclipse.org/mailing-list/threadx

Best Regards,

@alberk8
Copy link
Author

alberk8 commented Jun 12, 2024

Thank you for the update.

@cyberxnomad
Copy link

any progress?

@tdjastrzebski
Copy link

any updates?

@fdesbiens
Copy link

Hi everyone.

I appreciate your patience. The project is in much better shape now. We started merging small fixes and improvements and are working on a public roadmap, which we intend to make available in early 2025.

I expect we will do a v6.4.2 service release in Q1 2025, barring any unforeseen issues.

My current focus is to convert the current documentation set (rtos-docs repository) from markdown to AsciiDoc. This is because we found a way to publish the current MD files to HTML but ran into difficulties in doing the same to PDF. Microsoft used a custom solution for that, and we did not inherit it. Moving to AsciiDoc will enable us to publish easily to both formats.

So, things are looking up! Happy holidays to you all.

@tdjastrzebski
Copy link

I am glad to hear that, especially since in my opinion ThreadX is a piece of very good software. Probably its major problem was that it was seen as a Microsoft product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

4 participants