Re: Does anybody have release plans for current roundup devel?

Hi Joseph:

In message <[email protected]>,
Joseph Myers writes:
>On Tue, 19 Feb 2019, John P. Rouillard wrote:
>> There is at least one patch:
>> 
>>   https://issues.roundup-tracker.org/issue2551023
>> 
>> that could go into a 1.6.1 release. Thomas Hein do you have a cheat
>> sheet for creating a 1.6 release branch and tagging a 1.6.1 release?
>
>I've previously suggested that my fix for issue2550994 (breakage caused by 
>configparser backports; fix is 0cdf19b82354) ought to be added to the 1.6 
>branch (which already exists) if such a release is to be made.

Yeah, that looks like it should go in.

>(Though I'm more interested in having a 2.0.0 release from current
>trunk, with successive 2.0.1, 2.0.2 etc. following reasonably quickly
>should issues be found with the changes in 2.0.)

Would you like to take on the role of release manager for the 2.0.x
series? Probably the only way to get the 2.0 series released quickly
like you suggest.  If so I'll email you off list to get you set up.

I would suggest a 2.0 alpha or beta release first with
announcements. That would let people explicitly install the
pre-release from pypi (pip install roundup==2.0a1). Anybody upgrading
in the 1.x series or just doing a pip install roundup will get 1.6.x
until the formal 2.0.0 is released. The REST code is probably alpha at
this point as we are still running it through it's paces.

It would be nice to have some way to tell how many downloads we have
of each release from pip so you can see if the alpha/beta is getting
used. But that is not easily available.

Thoughts?

Have a great week.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.