- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Tue, 10 May 2022 15:26:31 +0100
- To: Michael Kay <mike@saxonica.com>
- Cc: public-xslt-40@w3.org
Received on Tuesday, 10 May 2022 14:27:53 UTC
Michael Kay <mike@saxonica.com> writes: > When I generate new tests, I often want them to go into both, and I > assumed that making it a fork would make that easier (I do > occasionally synchronize, though I haven't done so for a while). Also, > I assumed that if it ever happens that 4.0 gets official approval in > some sense, then we will want a single converged test suite in which > all tests are labelled with the version that they depend on. Well, okay. If there really is a use case for merging between them, I suppose a fork makes sense. > I certainly hadn't realised this would stop people having forks of > both. Does this just mean GitHub forks of both? Does it just mean that > the two forks need to be under different GitHub ownership? It seems a > very odd restriction. It does. I’ll dig a little deeper when I have the chance. In the meantime, I’ll abandon my proposal. Be seeing you, norm -- Norm Tovey-Walsh Saxonica
Received on Tuesday, 10 May 2022 14:27:53 UTC