Second the suggestion to reset Master to be a copy of the latest production release, so future development starts from that point.
Unless there's sufficient interest in doing a reconciliation pass... -- /_ 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: Monday, January 30, 2023 11:10:11 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: source location? On Mon, Jan 30, 2023 at 10:46 AM Mukul Gandhi <muk...@apache.org> wrote: > But for XalanJ, this may not be easy to do. We'd need to identify, all > deltas correctly for xalan-java repos between branch > xalan-j_2_7_1_maint (just post the 2.7.3 release) and the master > branch, and have those deltas synch to the master branch. Ideally, > after this, the xalan-java's master branch shall need to be tested > with the test suite that XalanJ has. It's much easier than that. I am proposing that whatever source is released as 2.7.3 becomes the main branch. Any changes in what is currently on master that are not in 2.7.3 are simply wiped out. In the unlikely event anyone wants to move some of them forward, that's what history is for. I'm proposing we accept the truth that we have a single maintained branch that only accepts bug fixes, and optimize the workflow for what we're already doing. -- 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
