SmartSDR v1.4.11 ?

PAØGDW

After SmartSDR  v1.4.3 ... why is this update called SmartSDR  v1.4.11 ?

Are we going down in the next release to SmartSDR  v1.3.3 ?  

73 Gerben PA0GDW

Jim Gilliam

I am so glad you asked that question! I was scratching my head wondering the same thing?

W7NGA

isn't 11 greater than 3? 

KY6LA_Howard

1 2 3 456789 10 11

Because. 11 comes after 10 which Comes after 9. .......

11 is larger than 3

It was the 11 th test version of 1.4.

Dan -- KC4GO

There were 8 sub releases 1.4.4 thru 1.4.10 before 1.4.11 -- most likely seen only by FRS programmers and/or the ALPHA team.  The next logical release would be 1.4.12 which you may or may not see. That to path to 1.5.x in the future. The reason this isn't 1.5 is as Steve said their not finished with the NR/ANL still some tweaking to be done. 

Rob N4GA

Looks fully but indeed 11 is greater than 3

it's not 1.4.1.1 it's 1.4.11

Jim Gilliam

yes but .11 < .3

PAØGDW

tnx...for me i did not see any sub releases ....i thought Version 1.4.4 was the logical name...hi..

 

Rob N4GA

Learn the convention. That's not how it works.

Jay -- N0FB

11 is greater than 3.  There is no issue.

IW7DMH, Enzo

A leading zero notation could be clearer, at least for the build numbers.
Just like 1.04.03 or 1.04.11

PAØGDW

in decimal viewpoint ....     .3 is   more than .11     hi..

PAØGDW

Bingo !! just my thoughts... 

Bob Brown - N8OB

And all this time, I thought it was only me..

Jim Gilliam

It would obviate the ambiguity in that .03 < .11

Steve W6SDM

****!  Maybe they should put this question on the Extra exam. 

PAØGDW

ok Guys...enough now over this V1.4.11....hi...

More  important is that my first impression is that with this new firmware the NR is much better....i like this... not enough time  to test the NB....

so my last wish to the list is to FILL IN The Panadapter Display ...like in the older PowerSDR... 

 switchable ofcourse ....on or off.... 

Steve-N5AC

Here's the canonical answer since this has been asked a few times:  All of our releases have a 4-number release version that looks like "vA.B.C.D".  Here's what the numbers mean:

A: Major version number
B: Minor version number
C: Internal release sequence
Build number

A & B are use primarily for marketing purposes to help customers understand the changes in the software.  A jump in the major version number signifies major changes in the software while a jump in the minor version number signifies more minor changes.

While we are working on a release, C is incremented every time we release any software outside of the building.  This way we always know what a customer has in their hands if they give us "vA.B.C".  Every release we make to the Alpha team or when we do a Beta or General release will have a new vA.B.C release identifier.

D is incremented automatically by our build server.  Anytime a developer checks in any code, this number is incremented and the entire suite of software is rebuilt with a new unique vA.B.C.D sequence.  This helps us internally keep track of software floating around our building.  The D number really doesn't mean anything externally -- it is essentially redundant.  For any A.B.C combination that a customer has, there is a corresponding D which is always the same.

Incidentally, we would typically have released v1.4.11 as v1.5.  After we publicly stated that v1.5 would have the noise mitigation advances, we realized that we could release any new work incrementally over time without holding everything until we were done.  We felt like releasing these incremental pieces as v1.5, v1.6 would generate a lot of "wait, are they done?" discussion so to bypass this, we decided to just release as v1.4.x until we feel we have made the progress we set out to make.  This way you get the features and advances as we have them ready.  Of course noise mitigation will go on forever.  Just because we release v1.5 doesn't mean we'll never incorporate any new techniques we develop/learn.

Hope this helps.

PAØGDW

tnx..Steve...very clear now... 

73 Gerben PA0GDW

Mark Griffin

It will be interesting to see which version will be operating at Dayton? The only reason I say that is with DAX issues that have been occurring with the past 2 upgrades.

Steve W6SDM

That would be a cool way for us nerdy types to use that convention in naming out kids, i.e., kid version 1.0.0, kid version 2.0.0, then we could add revision and release numbers for the grand kids and great grand kids.

Patrick

Text title with period as delimiter.... Does not equate to a numerical value as a whole but numerical values separated by a period. 

Jim Gilliam

DAX was invented to be like the weather. We all talk about it but do nothing to change it.