All of which sounds reasonable to me, unless Apache has a reason for maintaining it's own git other than "that's how we started".
Still waiting for permissions to come through, but I could start reviewing old branches to see if they were already merged or otherwise addressed... -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Elliotte Rusty Harold <elh...@ibiblio.org> Sent: Friday, April 21, 2023, 12:13 PM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: The Curse of Knowledge as applied to open source projects On Fri, Apr 21, 2023 at 7:53 AM Joseph Kesselman <kesh...@alum.mit.edu> wrote: > The question is, what are folks finding most confusing/difficult, and is it > something we can fix? Open Jira items for that, size, and prioritize > appropriately? 1. Publish the release to Maven Central. 2. Make the main branch of Github the source of truth. Use Github for all PRs and code reviews. 2a. No long lived branches. All development on the main branch that is ready for release at any time. 3. Merge the tests into the primary Github repo on the main branch -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
