I suggest that we build our updates using our own numbers on the user build disks. We can then sort out ¡°official¡± (I hate that word) numbers when we re-distribute.
That¡¯s the 594 for CP and the 593 for CMS. Bothy are accessed as ¡°E¡±. You can then name your mods LCLnnnDK or LCLnnnDM and whoever builds the release can give them ¡°official¡± names and numbers.
In the past its whatever me or bob, or further back Andie or whoever liked.
?
No thoughts on the rest. The original idea was for quick releases. That hasn¡¯t happened¡
From:[email protected] <[email protected]> On Behalf Of William Denton via groups.io Sent: 26 August 2024 19:59 To:[email protected] Subject: [h390-vm] Contributing to, Building, and Maintaining VM370CE #VMCE
?
I recently posted on asking these questions about how I should submit my VM updates for inclusion in a future CE "release":
Is there a master list of assigned update numbers? How do I figure out the "###" part of the update name"HRC###DK"????
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?
What sort of consensus/approval/voting process do I need to go through to share my stuff?
Dave Wade responded that, since there really aren't any current processes, it might be a good idea to take the discussion to the wider group.
?
So, how do we go about creating some sort of guidance/process for enhancing and maintaining future releases of VM370CE? I guess, first of all, is there really any serious interest in continuing the "Community Edition" idea? If so, then we probably could use at least a loose sort of "product management" strategy.
