The planned major changes on the roadmap for Ansible 12 seem to be identical with the ones on the Ansible 11 roadmap. I’ve overlooked this completely, concentrating solely on the dates
Anyway, do you think we should keep a planned major changes section for future releases? I mean, it looks like we’re going to remove cisco.ise on short notice and cancel the removal of google.cloud. Should we update this section in those cases? If yes, I fear we’ll forget about this; and if no, people will see outdated (that is: wrong) information there.
@felixfontein suggested a third approach on Matrix: Keep the section just in case, but leave it empty until we really have something to announce. That is, something else than collections to be removed.
Breaking changes are also major changes, so it’s kind of OK I guess Maybe we should call it “Major work”, not “Major changes”? In any case, I would not mention removed collections there, since they’re already mentioned in the Ansible X-1 and Ansible X porting guides / changelogs, and having yet another place where they are mentioned (and need to be updated in case of changes, like the Google collection right now) increases the risk of one of these lists being out of date.
Good point! Maybe we should keep the section, but change it to something like:
Please see the X-1 and X (which we’ll start publishing together with the X.0.0 alpha1 release) Ansible Porting Guide for the currently planned major changes.
Or maybe drop the reference to X-1? The one for Ansible 11 is quite long… I don’t think we should tell users to read this through. So maybe just:
Please see the Ansible X Porting Guide (which we’ll start publishing together with the X.0.0 alpha1 release) for the currently planned major changes.
I would change ...for the currently planned major changes to ...for the currently implemented major changes, since everything that’s in the porting guide or Ansible X has already been implemented in Ansible X.
But honestly, I think we can also simply leave the section away once we start writing this.
The Major changes section in the roadmap doesn’t seem to add a lot of value, so changing it to boilerplate text to say ‘see the porting guide’ makes sense, or removing it altogether as a section also seems fair imo.
The more I think about this, the more I’m convinced we should simply drop this section.
What I mean is: The planned major changes are either inherited by the collections that we include (and it’s not always clear if there will be a new major release including major / breaking changes in time for rc1). Or it’s about collections we remove, or cancel the removal of collections. Which isn’t something we can predict when doing the roadmap. This can happen quite late (see here and here) in the development cycle.
So the only boilerplate text we could add would be something like: Well, this is a moving target! Keep a lookout on the collections you’re interested in, and at the changelogs of version X-1 and X-2, and X once we’started with a1. (I’m exaggerating here, of course.)
Maybe we should call it “Major work”, not “Major changes”? In any case, I would not mention removed collections there, since they’re already mentioned in the Ansible X-1 and Ansible X porting guides / changelogs, and having yet another place where they are mentioned (and need to be updated in case of changes, like the Google collection right now) increases the risk of one of these lists being out of date.