Roadmap : A list of prioritised issues.

[piyush-garg]

A list of prioritized for FMP. These issues are part of the backlog and we are prioritizing in our following sprints:

Features (and proposals)

• Istio Support [Epic] Istio support #1164
• Add support for service Catalog Add support for Service Catalog #1050
• Add support for Istio via enricher Add support for Istio Kubeinject via new enricher #1119
• Allow generating service without route Allow generating service without a route #1209
• Support for Multi containers in Resource fragments Support for Multi containers with Resource Fragments #968
• Plugin should support resource type Plugin should support POD resource type for yml configuration file #963

Kubernetes and OpenShift Compatibility

• Add support matrix table Add support matrix table #1207
• Fix CI Setup of FMP Fix CI setup of fabric8 maven plugin #1198
• Unable to build multimodule project FMP 3.5.34 onwards Unable to build multi-module project with fmp 3.5.34 #1184
• Unable to deploy using FMP 3.5.34 onwards on Openshift 3.5 Unable to deploy to an Opeshift 3.5 cluster using FMP 3.5.34 #1183
• Deployment does not complete with Opesnhift 3.7.1 Deployment does not complete with OpenShift 3.7.1 #1168
• Upgrade to 3.X of the model upgrade to 3.x of the kubernetes-model #1067

Tests

• Add regression tests [EPIC] Add regression/functional tests for booster projects #1103
• Fix Regression test Issues Regression test issues #1135
• Add regression test for multimodule project Add regression test for multimodule project #1197
• Decouple regression test module from Fabric8 Maven Plugin Decouple regression test module from Fabric8 Maven Plugin #1155
• Add unit test coverage [EPIC] Improve the unit test coverage #1102
• Unit test coverage for Enricher, Generator, Plugin Improve unit tests for "Plugin" module #1106, Improve unit tests for "generator" module #1105 , Improve unit tests for "Enricher" module #1104

Springboot, Vert.x, Wildfly Swarm

• Support Spring boot 2 Support spring-boot 2 health check endpoints #1206
• F8 -springboot - health check ignores context path f8-spring-boot-health-check ignores contextPath #1120

Security

Documentation

• Fix startup script for windows Fix Startup script instruction for Windows which is not providing the correct information #1100
• Add docs for samples. Add docs for samples #1502

Uncategorised (Bug Fixes )

• Minor Changes to ImageTrigger Generation Minor changes to ImageTrigger generation #1177
• Release process should test before generating tags Release is breaking on jenkins.cd.test.fabric8.io #1195
• Improve fabric8:import Improve fabric8 Import #1091
• fabric8:import fabric8:import looks for fabric8 service #1081
• Exception in Reconnect Errors while watching build in fmps Exception in reconnect errors while watching builds in fmp #1159
• Specifying Dockerfile is broken Specifying external Dockerfile broken #1097
• Init containers not working with Deployment Config InitContainers when defined within DeploymentConfig are removed from final resource created and deployed #1114
• Revert default image name back to latest Revert default image name back to "latest" for snapshots #1093

This list is just a first stab at handling and reducing the backlog that we have accumulated in FMP issues list. Please comment on this issue and let us know if you feel there are issues that we might have overlooked or need to be prioritized. We can definitely work something together.

[rhuss]

Coming back to this roadmap, is this still the plan ? (There seems to be quite of a silence since its started).

Maybe we can take a step back and reconsider the priorisation ? I.e. it would be awesome if could consolidate on this plugin and harden it for its current functionality.

On first glance, I see the following open issues and task:

• Remove unused goals Removed unused Mojos #1313
• Remove dependency on https://github.com/fabric8io/fabric8
• Extract Enricher and Generator to fabric8-build
• Fix watch Mojo fabric8:watch is broken #1069
• Keep nodePort stable on deployment Service with NodePort always gets a new port after 'fabric8:apply' #894

Wrt to the release management, what would be the next major release ? Is it 4.0 ?

[rhuss]

@oskutka @rohanKanojia @piyush1594 Can we please discuss the roadmap how we want to move on ? Happy to schedule a call, too.

[rohanKanojia]

@rhuss : Yes, We would love to schedule a call with you guys in order to discuss the roadmap for fmp, refactoring fmp to fabric8-build, dmp integration etc

cc @oskutka

[rhuss]

I update 2 boards in https://github.com/fabric8io/fabric8-maven-plugin/projects to reflect the idea I would have for a roadmap (including concrete tasks):

• fmp 4.x for a consolidation phase, touching down to the required features and cleaning & stabilizing fmp
• fmp 5.x for moving out the core functionality to be usable by other projects

I would leave fmp 3.x as it is now, branching off from the latest release for the most urgent bugs.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!