View Issue Details

IDProjectCategoryView StatusLast Update
00032372 - Next Dev List (Holding Area)Enhancementpublic2020-07-02 02:11
ReporterK7ZCZAssigned To 
Status newResolutionopen 
Summary0003237: Build types should be fixed choices, not free strings
At present, the build type can be any string, arbitrarily. This isn't too useful.

It would be nice to enable or disable code based on build types -- certain code appears or disappears when a beta build is created, for example, for testing.

We should rearrange HRDVER.H and the build script so that the build type is given from a set of choices, which are fixed and drive on/off preprocessor macros to enable or disable code optionally.

We do need to still flag unsigned builds of any type. So I propose these mutually exclusive build types:

EXPERIMENTAL // not a beta or a release build; maybe a one-off for testing
BETA         // a public beta release
RELEASE      // a released and supported build

Additionally, the "UNSIGNED" flag may be set:

UNSIGNED == 0 // this build is signed
UNSIGNED == 1 // this build is not signed
SIGNED   == 1 // this build is signed
SIGNED   == 0 // this build is not signed

TagsNo tags attached.
TestingNot Started


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-03-06 17:29 K7ZCZ New Issue
2020-07-02 02:11 WA9PIE Project 3 - Current Dev List => 2 - Next Dev List (Holding Area)