Release related end-user burnout

Started by OPNenthu, Today at 01:32:42 AM

Previous topic - Next topic
Today at 01:32:42 AM Last Edit: Today at 01:49:35 AM by OPNenthu
In response to @franco's comment here-
 
I say "yay!" for more frequent security fixes, but I have a concern if the frequency of release notes that I need to pay attention to increases ;)  Anything in the works to automate security patches but leave the features and (potentially) breaking changes as manual updates?

Actually I'm not sure what's less cognitive load: more things less often, or fewer things more often.
N5105 | 8/250GB | 4xi226-V | Community

I like that the entire release history is repeated in that pop up change log prior to updates.

All you really have to do is read the last date entry to see changes since last update.

It took me a while to get the rhythm but it's nice to be read the changes if I want.

On Reddit we list the release notes in reverse order... maybe that's something we should do for the normal release notes as well?

https://www.reddit.com/r/opnsense/comments/1xtjd8f/opnsense_2679_released/

When it comes to hotfix or patch releases the question is how we can describe the process and the changes. Traditional tags and branches are a bit ill-suited if it means having to maintain 3 x 20 additional "stable" branches just for community versions per year (with all of them being flexible and optional) and even then it's very cluttered across different repositories and impossible to translate into release notes.

In the business version we already shifted to patch releases which structures everything a bit better, but even there are some limits that would better be solved with something more straight forward. Ironically, it could be something that was already done in the past with varying degrees of success before being abandoned altogether.  ;)


Cheers,
Franco