I'd rather not see it called Xalan 3.0, reserving that name for if/when it gets merged into the main stream.
-- /_ 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: mukulga (via GitHub) <g...@apache.org> Sent: Saturday, July 1, 2023 11:17:05 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: [GitHub] [xalan-java] mukulga commented on pull request #13: implementation of xpath 3.1 function item inline function expressions. also implementations of xpath 3.1 higher-order functions fn:for-each and fn:filter, that use inline function expressions... mukulga commented on PR #13: URL: https://github.com/apache/xalan-java/pull/13#issuecomment-1615956145 > I suggest PRs into feature branches should use "Squash and merge" or "Rebase and merge" (as appropriate) from the PR's "Merge" button options, to avoid creating extra merge commits on the feature branch. The feature branch will be merged with a single merge commit into master at some point. See the convoluted history remaining, otherwise: > > * https://github.com/apache/xalan-java/network > >  > > Of course, this does require developers to reset their local working branches to the remote feature branch after "merging" the PR. I think, there's no significant discussion so far within XalanJ team about, how XalanJ's implementation from dev branch xalan-j_xslt3.0 shall be released. My personal opinion as of now, about XalanJ's next release is following. The XalanJ next release may consist of following two release packages to be provided simultaneously, 1) XalanJ XSLT 1.0 release (to be likely named XalanJ 2.7.4) made from xalan-java repo's 'master' branch. This XalanJ release shall use the XalanJ test cases from xalan-test repos's 'master' branch. 2) XalanJ XSLT 3.0 release (may be named as XalanJ 2.7.4-xslt3.0-M1, as a milestone release from XalanJ dev branch xalan-j_xslt3.0x). This XalanJ release package shall provide users with early access to XalanJ implementation's XSLT 3.0 new features so that users may provide feedback. This XalanJ release, might use XalanJ test cases available at https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0/tests/org/apache/xalan/xslt3 (these XalanJ tests entry-point is the Java class AllXsl3Tests.java). This XalanJ test suite should have, sufficient test cases for this release type. I've seen this, release type from few latest releases from other Apache projects, which provides me this idea. Any thoughts about this topic from, persons like Gary, Joseph shall be nice to know. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
