From: Craig A. B. <cra...@ma...> - 2022-02-03 13:54:01
|
> On Jan 28, 2022, at 4:12 AM, Jo Calder <Jo....@ha...> wrote: > > Hi all, > > I see that there's new eXist-db (6.0 reached via http://exist-db.org/exist/apps/homepage/index.html#downloads, and clicking on the 5.3.1 link). Did I miss the announcement for 6.0? > > The new drop happened just as I was preparing a release. It would be really useful to know whether any regressions were detected in 5.3.1 (relative to 5.2) which are corrected in 5.4/6.0. Can anyone supply that info? According to the publicly-available community call meeting minutes from Monday: <https://docs.google.com/document/d/1eycQBp0CR9_B4fcGPt-1et4Ymgt4Fpzj5YcKhZp3Ln4/edit#heading=h.ei4sqy3ojpkl> The announcements for 5.4.0 and 6.0.0 were held back because of a problem discovered with Monex in those releases. That problem seems to have been addressed: <https://github.com/eXist-db/exist/pull/4215> and releases of 5.4.1 and 6.0.1 that include it should be out soon. The fix is in eXist itself and can't be fixed by upgrading Monex. The small team of volunteers that produces these releases is understandably a bit behind on their paperwork and has some work to get the issue tracker caught up with reality, but I would expect master tickets for the upcoming releases to appear soon on the milestones page: <https://github.com/eXist-db/exist/milestones> ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |