On Mon, Aug 26, 2024 at 14:59 William Denton via <williamedenton=[email protected]> wrote:
Is there a master list of assigned update numbers? How do I figure out the "###" part of the update name"HRC###DK"????
I've been opening GitHub Issues at either
?or?
for everything I discover, and then attaching fixes when I figure out how to fix them. My VM updates are all RAPxxxcc, 'cause my initials are RAP ?. ?"cc" is the component code - DK, DS, DM, or DT.? And I use AUXLCL, 'cause there's already DMSLCL CNTRL that specifies that.? So, for example, see
.? And I've been assuming that whomever collects things into a release will renumber them as HRCyyycc, where xxx and yyy are likely to be different.? I have a few small EXECs that make renumbering updates easier.
Is there a preferred way to package the files in an update? On my system, I keep all the files together in a .txt file in CMS READCARD format. How do the keepers of the CE releases prefer to receive proposed updates?
I've been keeping mine on the LCL disk, with the expectation that I'll delete them when the corresponding HRC updates come out in the next release.? And, of course, I've been opening Issues, which at least one person has pulled a fix from.
What sort of consensus/approval/voting process do I need to go through to share my stuff?
I ought to leave that as a question for Dave et al.? But as a very old friend of Bob Bolch, I'll suggest that his technique would have been to accept every bugfix, if written will enough, and to ?discuss feature contributions on this list.? Some of you may recall the discussions about BREXX and CMS.
is there really any serious interest in continuing the "Community Edition" idea?
