Roadmap for 2025 and later

[vdemeester]

This is very much similar to tektoncd/pipeline's roadmap discussion but for this repository.

First, the current ROADMAP.md file has not been updated for 3 years and is most likely not fully representative of what is planned, …

• I think we need a more dynamic way to manage the roadmap. It could be using a discussion (all maintainers can edit the main body and thus, given discussions, … could add items to the roadmap) or some issue labels + filter + project maybe (? but we tried this before, I don't think anybody uses the projects today).
• We should remove that file and instead discuss the roadmap here (for now) and then figure out where and how we store and update it.

My initial thoughts

• Urgent
  • Detect *stale* tekton objects prior to a upgrade / reconciliaton #2474
  • Upgrade without killing the CRDs #2473
  • Enhance log reports from the operator controller(s) #2472
  • Migrate e2e tests in GitHub workflow #2470 and Testing Matrix #1826 and Migrate e2e tests on kind #1144 (all doable in one shot)
  • Option to disable proxy #872
• Important
  • v1beta1 API "epic" #1145
  • Automate releases
    • aka create a branch and release is done
    • … and bugfix release are done automatically as well
• Lower-anging fruits
  • Enable image signing (with chains) in Tektoncd Operator release pipeline #763 (make sure it is the case already)

Most likely there is more items we could add, let's discuss this.

In addition, there is the label area/roadmap that should help/reflect this.

cc @tektoncd/operator-maintainers @tektoncd/operator-collaborators