>>>> Can you give me a (realistic) worst case scenario if we were to >>>> release without making any changes? >>> >>> IMO Worse case we can't make a release until this is resolved. >> >>No, I meant what would happen if we went ahead a binary release >>without fixing this... Tempting, because we did that nearly a dozen >>times without the world coming to an end. > > That was my point. Unless we find out that Saxon has some unfriendly > dependencies, the question of whether a binary dependency in the package > was compiled from sources or not or whether the Installer should ask about > MPL and MIT dependencies probably doesn't put the foundation at risk, so > the worst case is you hit send on the announcement and we hear back at > that moment that there is a rule like that and we have start in on fixing > that, but I would be surprised if we have to pull it back.
OK, thanks. I'll proceed under the assumption that this will be resolved before we release, but that if it isn't, we don't treat this as a blocking issue. I plan to start a 14.4.1 branch right after we release 14.4.0, just in case we need it to fix e.g. this issue or some TLF related emergency. That should bring down the lead time when an issue arises considerably. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
