On Friday, March 6, 2020 at 10:07:29 AM UTC-8, Greg Troxel wrote: > > Vince Skahan <vince...@gmail.com <javascript:>> writes: > > Greg - still missing what you're looking for that you can't already do. > > - git pull > > - git checkout -b v3.8.2 (create a local branch off a release > tag) > > That creates a branch off a release tag. It has seemed to me that fixes > go onto master after the release (which is a good thing). > > They do. So ???
> What's missing ? > > A way to "follow 3.9 stable" without me back-constructing the branch > tag. > > I think you can look at 'master' as similar to the 'stream repo' concept in new RHEL/CentOS. It would contain the latest stable set of patches to the latest production version, pre-release of a new (tagged, bundled, packaged) version. So master at any point in time is what the next release would look like, if it had to happen 'now'. The other branches are (to me) stuff not so stable, possibly experimental, possibly never to see the light of day in an official release. In git-flow terminology they'd call them feature branches. Bottom line - we can't assume 'master' is 'latest release' because it isn't. It's the 'to be NEXT release' as it exists at the current date. So basically what's missing is a branch ref stable-3-9 which started out > pointing to master as soon as it became v3.9 time, is advanced along > commits on master intended for v3.9.next, and now points to 0ecd4fed. > > Totally lost. There 'is' no stable N-1 branch. You can always get to what N-1 was by using its release tag. -- 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 weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/24bc0132-3478-4dad-86e6-41ccd98e3788%40googlegroups.com.
