[weewx-development] state of the git repo, master/development considered very awkward

2020-02-29 Thread Greg Troxel
I have been following the messages about 4.0 alpha/beta stuff with interest, expecting to get around to testing some day. I just did a git remote update, and was surprised to find that master, which had previously been the stable branch, now contains 4.0beta (loosely speaking). I must have missed

[weewx-development] v4beta mystery element values in packets from test driver

2020-02-29 Thread Vince Skahan
I'm cobbling together a driver that will ultimately seed its packets with a JSON query from the Davis WeatherLink Live hardware (mentioned in a separate thread). I used mwall's suggestion to start with his maxbotix driver, and stripped a bunch of stuff out of it to basically have it generate a

[weewx-development] Re: state of the git repo, master/development considered very awkward

2020-02-29 Thread Vince Skahan
Interesting post. Sounds like you want some kind of semi git-flow kind of thing except with long-lived minor-release extra level of integration branches. I think weewx basically takes the position of "*stick where you're at or get yourself current*" in general, other than also pointing folks

[weewx-development] Re: v4beta mystery element values in packets from test driver

2020-02-29 Thread gjr80
A few things to remember: 1. The console output from running WeeWX directly is not the output from the driver rather it is the resulting packet/records after all WeeWX services have been run (StdConvert, StdCaibrate, StdWXCalculate etc). Have a look at the [[Services]] stanza at the bottom of w

[weewx-development] Re: v4beta mystery element values in packets from test driver

2020-02-29 Thread Vince Skahan
On Saturday, February 29, 2020 at 3:13:42 PM UTC-8, gjr80 wrote: > > A few things to remember: > > 1. The console output from running WeeWX directly is not the output from > the driver rather it is the resulting packet/records after all WeeWX > services have been run (StdConvert, StdCaibrate, Std

Re: [weewx-development] state of the git repo, master/development considered very awkward

2020-02-29 Thread Thomas Keffer
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

[weewx-development] Re: v4beta mystery element values in packets from test driver

2020-02-29 Thread gjr80
On Sunday, 1 March 2020 10:55:37 UTC+10, Vince Skahan wrote: > > I was worried weewx was making stuff up :-) > Actually there is a fair bit of effort made to ensure WeeWX does not make things up (windDir = None when windSpeed == 0, culling of fields from drivers etc) Gary -- You received this