That was just me being stupid. I committed, but then forgot to push my changes out.
On Mon, Feb 23, 2026 at 3:50 PM Greg Troxel <[email protected]> wrote: > I was confused at the state of the repo. This is me getting unconfused > in case that helps. Part of that is master/development and part was > just me being confused. The master/development naming is only explained > in CONTRIBUTING, but people who are just trying to run the code need to > know that. Suggested fix at end. > > On master since v5.2.0 there are 26 commits. Presumably those are "on > the 5.2 branch". Skimming commit messages, this seems plausible. So > this is what could be v5.2.1. (It won't happen -- that's fine. The > point is that they are thought to be commits appropriate to the stable > branch.) > > On development there are 139 commits not on master. There are no > commits on master that are not on development. Makes sense. > > I do see 5.3.0b1 in a commit message along master. > > I see no v5.3.0-b2 tag. I see no recent beta tags at all. > I get it that they are noise later. > > pyproject.toml still says 5.3.0b1. I guess that is the one true source > of version. > > Presumably you mean that v5.3.0-b2 is > > commit eea921253f2f0e3b9f09f0ed8560fa1aba0f4939 (HEAD -> development, > upstream/development, origin/development) > Author: Tom Keffer <[email protected]> > Date: Mon Feb 23 14:30:37 2026 -0800 > > Additional URLs > > but maybe a commit to pyproject.toml and a regen commit are unpushed? > > > It looks like one can just run this code instead of 5.2, with the same > config file, and that's expected to be ok. If that's true, I'll try it > on my live system (backups of course). > > Random other comments from trying to understand: > > pkg/README talks about "the installer" but I think all these files are > about particular packaging systems. I expect that if I use pip on > NetBSD, that nothing in pkg will be used or needed. > > Suggested fix to make branch names clearer: > > commit f3f27b23b173a258aa6e35e8fcaf3f6d5243ee19 > Author: Greg Troxel <[email protected]> > Date: Mon Feb 23 18:42:21 2026 -0500 > > README.md: Explain branch names > > because people trying to run the sources (but not contribute) would > not think to look in CONTRIBUTING. > > diff --git a/README.md b/README.md > index a481d17a..eade2f1d 100644 > --- a/README.md > +++ b/README.md > @@ -101,6 +101,12 @@ For the latest source code: > > [https://github.com/weewx/weewx](https://github.com/weewx/weewx) > > +## Orientation to Sources > + > +See CONTRIBUTING.md. Briefly, `master` is the stable branch > +(e.g. v5.N) and `development` is where changes for the next release > +(e.g. v5.N+1) go. > + > ## Documentation and Support > > Guides for installation, upgrading, and customization: > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECVLbLq%2B%3DKXahuvs%3DP6-ktXk0h3gkDd1S3Xzrv5ok-85Q%40mail.gmail.com.
