Re: Release timeline

"John P. Rouillard" <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <[email protected]>
Hi Tom:

TL;DR - I have no plan for a new release before 2.3.0 in July 2023.

In message
<CO3PR08MB79577055D990A5C1C61A7B7ACA7E9@CO3PR08MB7957.namprd08.prod.outlook.com>,
Tom Ekberg writes:

>I have noticed a large number of patches to roundup in the past few
>months. As I'm currently using version 2.2, is there a plan regarding
>releasing roundup 2.3? I'm particularly interested in the native
>Postgres FTS fixes.

The fixes for PostgreSQL native-fts landed in the last week. Turns out
the indexer was working, but could not be enabled in the released
version. The joke is that the indexing tests worked fine using
PostgreSQL fts. However there was no way to actually use the
PostgreSQL fts code. Trying to enable it would raise a NotImplemented
exception 8-). If you managed to get past that (just comment ut the
raise statement), it would actually use xapian/whoosh/native indexers
and not native-fts.

A lot of the checkins you saw were either documentation or me trying to
get GitHub actions to run the test suite. I finally got a clean build
on both GitHub and TravisCI that looks equivalent last week.

My last commits to fix PostgreSQL FTS somehow broke some SQLite tests.
A varying (with run and with python version) set of SQLite tests are
failing with:

   sqlite3.OperationalError: disk I/O error
 
My guess is some sort of race but... frankly I am stumped.

Of course I can't reproduce this running the test suite locally. Each
run takes 3+ hours on my system so it is not be fast enough to compete
with the 15 minute run time in CI.

Also a consistent set of postgres tests under python 2.7 are also
failing. I just reproduced this in another window so I at least have a
hope of fixing it 8-).

So to answer your question, there is no plan to release a new version
before the next scheduled release cycle in July. Since PostgreSQL FTS
is a new feature (that nobody tried during the 2.2.0 rollout), I am
not inclined to roll a new release just to make that work.

You could try using the current development version to give
PostgreSQL fts a test once I get a working release.

Look for passing roundup-ci actions (I run three action workflows on
GitHub you want the roundup-ci one) at:

  https://github.com/roundup-tracker/roundup/actions

or a passing build on 

  https://app.travis-ci.com/github/roundup-tracker/roundup/builds

and hg or git clone and update the the passing releases.

Have a great week.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.