Juju requests

store-requests
2

Hi,

Both the name registration requests were approved. Also, the 3.4 track for juju was successfully created.

Now regarding the track requests for jujud-controller;

Per Process for aliases, auto-connections and tracks 2, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

I have a couple questions before casting my vote.

  1. What’s the release cadence of jujud-controller, how often are new major versions (potentially requiring a new track) released?
  2. Will the new versions be backwards-incompatible? Meaning, for example, if I was running 3.4 and try to install 4.0, will that just work, or do I need to migrate my data/configuration, or will things break horribly? Moreover, I see that you’ve incorporated beta1 & beta2 into your tracks’ names. May I suggest you keep only the versioning as the name of the tracks (i.e. 3.4 / 4.0 or whichever name we end up deciding upon) and upload the revisions to the appropriate beta risk-level to indicate that they’re still in beta?

Thanks,

Odysseus