Thomas Keffer <[email protected]> writes: > The merge was intended (and usually is) done just before release. It was > our intention to do an immediate release, but we had some delays. > > WeeWX may be a bit different from other software you are used to. We > *never* support old releases. Either you upgrade, or you > don't. There's nothing in between. So, the usual work flow is to do > the merge into master, then release. There's no reason to have > branches dedicated to maintaining older releases.
I am used to the not supporting old releases concept. pkgsrc is like this; when a branch is released, then we immmediately cease maintenance - even security fixes - on the old branch. I am merely not used to not being able to tell with git names what is what, and not being able to choose straightforwardly to stay on a branch. I did not mean to suggest in the slightest that old releases should be miintained. In my case I was thrown off because I was trying to make sure I was up to date with all the old stable bits before contemplating building/using what was about to be the new stable bits, and once I was updated, it was quite difficult to find out if my old pointer was the farthest along the old stable or not (it was). I do wonder if any of the LTS Linux distributions have weewx packaged and how they deal with backporting fixes. There may be only a few individuals doing this, and few to no security issues needing addressing. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/rmiftelcrp8.fsf%40s1.lexort.com.
