Has the newly released branch replaced master, and been tagged with the new version number, yet? If not, that's first step, right? T (Actually, I strongly recommend taking advantage of the opportunity to replace master with main, to confirm to modern guy conventions.)
Cleaning up old branches is definitely overdue, though not exciting. It isn't hard to get a diff to see what each changed and then decide whether there's anything not included in main that's worth copying/reimplementing, just a nuisance. Frankly, unless it's something major it may not even be worth checking. Last time I looked at this, I think my conclusion was that the oldest aren't even worth checking... -- /_ 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: Mukul Gandhi <muk...@apache.org> Sent: Wednesday, April 12, 2023 8:25:52 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: XalanJ new git branches Hi Gary, Thanks for the thoughts. On Wed, Apr 12, 2023 at 5:31 PM Gary Gregory <garydgreg...@gmail.com> wrote: > we should clean up what we have now first IMO. Why don't we rename > xalan-j_2_7_1_maint to something more sensible first? The XalanJ 2.7.3 release's src distribution contains copy of readme file. That readme file mentions the branch name xalan-j_2_7_1_maint of repos xalan-java. Renaming the branch name from xalan-j_2_7_1_maint, shall invalidate XalanJ 2.7.3 src distribution's readme information and users may not feel ok. I think, this renaming action is too early as well. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
