Hi folks I don't see any objection and a consensus on the roadmap.
Here's the next steps: 1. I will update the main branch with 5.0.0-SNAPSHOT version 2. I will enable github resources via .asf.yaml (issues, projects, discussions) 3. I will move from Jenkins to GH Actions 4. I will create GH issues and milestones populating the 5.0.0 roadmap we discussed in this thread 5. I will start to create my PRs about new features service and karaf services Regards JB On Fri, Feb 21, 2025 at 8:40 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > > Hi folks, > > I would like to share the roadmap to Karaf 4.5.0. > > Karaf 4.5.0 will contain: > - a new "simple" features service (flat/simple resolver) > - new Karaf core services as alternatives to Pax * modules (replacing > Pax Logging by karaf-logging, replace Pax URL by karaf-url (with just > the JDK HTTP Client), ... > - more Karaf distributions, opinionated about the content: minimal (as > today but without Pax * cooupliing), simple (with the simple features > service, the alternatives to Pax *, ..), standard (the same as today > but with updated versions, we will discuss to "promote" simple as > standard for Karaf 4.6.x), integration (based on standard with Camel, > ActiveMQ, ...), cloud (based on simple with opentelemetry, k8s > support, ..., by default) > > As we did for Decanter, I will use Karaf 4.5.0 milestone to switch to GitHub: > - GitHub Issues instead of Jira (the idea is not to migrate everything > from Jira to GH Issues, but to do it "manually" to do a meaningful > triage. > - GitHub Actions instead of Jenkins for CI/CD > It works well for Decanter (https://github.com/apache/karaf-decanter). > > Another work we should do is about the website. I think it would be > great to use Docusaurus to facilitate the updates and maintenance. > Website content should be updated too, including easily the > documentation on the website (thanks to md). > Any volunteers for that ? > > So, now about the ETA: > 1. Regarding "move to GitHub", if no objection, I will start the > effort today, creating .asf.yaml, GH workflows, creating GH Issues > with milestones > 2. Regarding the new "simple" features service, I already have > something. I think I can have a PR by end of next week. > 3. Regarding the new karaf services (alternatives to Pax *), I have > karaf-logging and karaf-url almost done (PRs will follow ~ 2 weeks). I > started karaf-web (powered by Tomcat, not depending on OSGi > HttpService, it's a pure Karaf Http service). I should be able to > share a draft PR. > Reasonably, we can plan Karaf 4.5.0 with all this in May. > > However, I have a question for the community: maybe, considering the > number of important changes, it makes sense to use Karaf 5.0.0 instead > of 4.5.0 ? Thoughts ? > > Thanks ! > Regards > JB
