Release Schedule

[cdnninja]

I have enabled releases as a starting point. Feedback is appreciated on if it should be changed.

Right now it auto generates release notes and increases numbers via semantic version control. It releases on Wed/Sunday. Any owner can also trigger it via actions. I am open to adjusting it if it doesn't make sense. This lets us also have uses test things in master before it hits widespread updates.

[cdnninja]

In case it interests others here is the current stats for installs for those with the reporting turned on. With the recent releases our version will take time to catch up. Some of those versions are also other forks so won't update until the person reverts to this one.

"audiconnect": {
    "total": 648,
    "versions": {
        "1.0.1": 50,
        "1.0.0": 18,
        "2021.1.1": 290,
        "1.3.0": 126,
        "1.0.3": 29,
        "1.2.0": 33,
        "1.1.0": 59,
        "1.0.2": 25,
        "1.5.1": 5,
        "2023.12.3": 11,
        "1.0": 2
    }
},

Source: https://analytics.home-assistant.io/custom_integrations.json

[Kolbi]

"audiconnect":{
      "total":660,
      "versions":{
         "1.0.1":41,
         "1.0.0":14,
         "2021.1.1":290,
         "1.3.0":67,
         "1.5.0":33,
         "1.3.1":36,
         "1.5.1":14,
         "1.4.0":4,
         "1.2.0":13,
         "1.5.2":65,
         "1.1.0":32,
         "1.0.2":18,
         "1.0.3":19,
         "2023.12.3":12,
         "1.0":2
      }
   }

Wow high adapting rate currently :)

BTW: sorting is interesting in the json :)

[coreywillwhat]

{
   "audiconnect": {
      "total": 685,
      "versions": {
         "1.0.1": 33,
         "1.0.0": 14,
         "2021.1.1": 256,
         "1.6.5": 75,
         "1.6.4": 141,
         "1.5.2": 14,
         "1.5.3": 23,
         "1.5.0": 4,
         "1.1.0": 14,
         "1.0.2": 15,
         "1.3.0": 17,
         "1.2.0": 5,
         "1.5.1": 3,
         "1.3.1": 9,
         "1.4.0": 1,
         "1.6.2": 12,
         "1.6.1": 5,
         "2023.12.3": 9,
         "1.0": 2,
         "1.6.3": 14,
         "1.6.0": 6,
         "1.5.4": 3,
         "1.7.0": 7,
         "1.0.3": 3
      }
   }
}

[cdnninja]

Amazing work!!

[Kolbi]

Still growing:

"audiconnect": {
"total": 705,
"versions": {
"1.0.1": 26,
"1.0.0": 13,
"2021.1.1": 235,
"1.8.0": 113,
"1.9.0": 99,
"1.5.3": 8,
"1.5.0": 4,
"1.5.2": 5,
"1.7.0": 65,
"1.6.4": 43,
"1.0.2": 9,
"1.6.5": 15,
"1.5.1": 1,
"1.3.0": 13,
"1.1.0": 10,
"1.3.1": 7,
"1.6.1": 1,
"2023.12.3": 9,
"1.0": 2,
"1.6.2": 6,
"1.6.3": 7,
"1.5.4": 6,
"1.2.0": 4,
"1.6.0": 2,
"1.0.3": 2
}
},

[cdnninja]

This is also only users who enroll in the telemetry. So actual user count is higher.

[coreywillwhat]

Is there a way we can run a beta branch? There seems to be a lot of variability with vehicles. Some reporting different timestamp formats, or different features supported or not. it would be nice to push some beta releases so those who want to test can, and others can stay on the stable version.

[cdnninja]

Right now it generates a release Sunday and Wednesday.

If some merges need to be beta you can run the action to generate the release and right after edit the release and select the beta checkbox.

The action will release a stable release next commit though on those days.

We could make the release action always do beta releases but someone needs to check the box to convert to non beta at some point. Manually is always a challenge since this is a group of people it may get forgotten.

Part of the two days a week approach was it lets people update from master to test if needed. However that's also manual.

Open to thoughts.

[coreywillwhat]

I'm torn between going full auto release for beta with the thought being, if someone is in here submitted PRs and merging, then they will likely know to either push a manual or wait for a beta push.

The other part of me is thinking move the stable releases to weekly, to give more time for beta testing throughout the week?

My major concern here is I dont think there is enough community involvement to get people to manually patch from the master branch for testing. I do think there are people who would choose the beta branch within HACS/HA and update to that/feel comfortable with that. As they can always downgrade from within HA too.

[cdnninja]

If I find a way to say:

Release as beta on commit merge or once a day.

Weekly promote the current beta to prod

It would mean if someone finds a breaking beta near end of week they need to pull that beta by hand.

Otherwise would be automated. Would that help?

[cdnninja]

Other note to keep in mind is HACS only checks in once every few days. So the average person isn't notified of releases for a bit. Most likely why that issue was caught by a dev vs general user.

[coreywillwhat]

That method makes sense to me, but no rush on this either. Would rather take the time we need to discuss and find something we're all comfortable with. Do you think the approach makes sense? I don't want to change something just because its something I'm thinking. Really appreciate the collaboration.