When I was in XSoft, a relatively small software division in Palo Alto, the project team I was on had one of those tiny wind-up monkey dolls that banged cymbals. The way things worked, if you had the monkey on your desk, you were the only one to do commits and run the build and tests. That would be for your changes that were already in the repo and been unit-tested.
The monkey would be passed around. This was just to have there be no collisions with the pending-release test-build process. What is happening now to have Francis have the monkey on Taming? I assume Jean has stepped back, but I'd hate to see anything she had in mind to do be trampled on. Is there any commitment to have change work happen in the open? I don't see any forks of the repo, and it is essentially empty at the moment. -----Original Message----- From: Dennis Hamilton <[email protected]> Sent: Friday, February 5, 2021 09:32 To: [email protected] Subject: RE: Repository Organization Keep in mind that branching happens at the project/repository level. That is, a branch is always of the *entire* repository in some (branch) state. I think my main point is that repository organization should be by document, since there is no way to do all the documents in lockstep with AOO dot releases. There does not seem to be any capacity for the level of effort that would require. The tricky part, since you can't go finer other than by external agreement (e.g., naming branches to identify the guide and release they apply to, say), is figuring out how to resolve pushes of changes to different guides that are collisions at the repo level. Collisions in the same guide are presumably reconcilable, although/because there is no diff for ODF-format files. It's all or nothing or whatever adjustments happen off-line before a change is made to the branch in the main repo. Big projects have organizations structures among editors/captains/committers to help manage the review and roll-up of changes. Git was invented to facilitate that with an organized hierarchy for the march of changes into a new release (e.g., for Linux itself). With regard to the work that Francis is doing, is it showing up on the repository or are folks reporting what they are doing entirely off-line? - Dennis -----Original Message----- From: Keith N. McKenna <[email protected]> Sent: Thursday, February 4, 2021 16:46 To: [email protected] Subject: Re: Repository Organization [orcmid] [ ... ] It does certainly make sense. I was thinking more along the lines that Dennis outlined and keeping each guide in its own Branch and use tags to specify what revision of the software it applies to. That way if it is applicable to another version as well we tag it that way and not have to redo the entire guide. Also if there are only minor changes we can do errata sheets and not have to redo the entire guide. regards Keith [ ... ] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
