Hi,

My org uses an old version of Roundup, and I'm hoping we can upgrade 
soon. It's great to see you have a comprehensive changelog and docs 
about updating to new versions, but so far I haven't seen anything 
definitive about what has to happen to arrive at a stable v2 release.

Is there something I can track saying what still needs to be done for 
v2 to get a full release? My group is reluctant to do a major version 
change for a critical part of our workflow if it is to an alpha 
version that introduces more bugs than it fixes.

If there's no official/constantly updating page regarding the update, 
could you at least give me a quick overview of what still needs to be 
done and a timeline approximation? Would be really helpful to know 
approximately when we could responsibly update.

Digging through issues a bit more, I can see that there's been 2.x 
releases already on pypi since last year! That's a great milestone, 
congratulations. What stops it from proceeding at least to beta at this 
point?

Hi Dannio,

The biggest impediment is lack of testing.

The changelog for post 2.0.0 alpha0 is at:

   https://sourceforge.net/p/roundup/code/ci/default/tree/CHANGES.txt

the testing requested in the 2.0.0alpha release announcement:

  https://sourceforge.net/p/roundup/mailman/message/36791520/

I haven't had lots of reports of people trying it (there is another 
thread a few weeks after asking for stories about 2.0.0 release).

Having people with roundup instances spin up a new instance, 
export/import the data into the new instance and test would go a long 
way toward getting the kinks out. Especially if they use python 3
as the interpreter.

BTW what version of roundup are you currently using?

-- rouilj

2.0.0beta0 was released 2020/04/06.

I plan to release 2.0.0 final in July.

2.0.0 was released last monday July 13. Note that you want to make
sure to get a backup before upgrading and test.

Enjoy.