Closed luizaandrade closed 4 years ago
All done!
I want to add "re-base existing branches and write in check-list issue which branches were successfully re-based and which were not".
Re-base after v1.5
:
iefieldkiterror
dev-iecorrect
iecodebook-hashdata
issue-100
Branches that fails to re-base starts to be so out of data that they might be gnarly to merge towards master.
No action required on the failed re-bases, but if I saw a branch that was mine that could be deleted in failures, then now would be a good time to do that. And if I saw one that I intend to work on, then I would try to solve this before it gets worse @bbdaniels and @luizaandrade
I think that makes sense. I also added an item to update the command from SSC and make sure it's the last version once we get the email from Kit Baum
I think we can close the branch on #100, since we decided not to implement it.
ok, I saw you deleted it now. thanks!
develop
branch.master
branch. Name this branch the same as the version number you are about to release. For example,v1.1
,v2.32
etc.develop
branch, merge those todevelop
and then re-mergedevelop
to the version branch and test again.net install
Version number and dates in ado-files and help files.
The version number is on the format
number.number
where the first number is incremented if it is a major release. If the first number is incremented the second number is reset to 0. If it is not a major release, then the first number is left unchanged and the second number is incremented.Version number and date in ado-file. Change both version number and date. Make sure that this line is the very first line in the ado-file:
Date at the top of the help file. Change only the date, there is no version number in the help file.