Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version actions #3

Open
bobmcc9 opened this issue Sep 22, 2020 · 1 comment
Open

Version actions #3

bobmcc9 opened this issue Sep 22, 2020 · 1 comment
Assignees

Comments

@bobmcc9
Copy link
Contributor

bobmcc9 commented Sep 22, 2020

a. We need to adopt Semantic version for this REPO https://semver.org/

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.

b. in order to achieve this we need to amend GVBEYE MACRO eyecatcher area

  Currently GVBEYE delivers this code

     hdreye   ds    0x               label 
     eyestaMP DC    C'SAFREYECATCHER: '    
     modname  DC    Cl8'GVBUR20 '          
     DC    C'PM4.18.99 D  '       
     DC    C'20200917  01.08'     

c. assumption 1 -- this Gvblib version will be independent of other genevaers REPOs

d. assumption 2 -- for this repo at this point in time we have

Major  = 0     is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
Minor  = 0     by default
Patch   = 0     by default

e. this will require a change to GVBEYE see bold

     hdreye        ds    0x               label  
     eyestaMP   DC    C'SAFREYECATCHER: '     
     modname   DC    Cl8'&module '           
                       DC    C'**GVBLIB 0.0.0** '           
                       DC    C'&SYSDATC  &SYSTIME'   

f. when stable we can change Major to 1 and create a new branch

Question: May I proceed with this change?

many thanx
bob McCormack

@KipTwitchell
Copy link
Member

That all makes sense to me, if Randall Approves. Also, it seems Bob you seem to have a vision for what should be in the "release" document in the community repo. Mind giving that a draft as that is on our TSC to-do list?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants