I don't think it's useful to reflect this change in a version number. I 
think it can just happen in the middle of the 9.8 release cycle.

On Sunday, September 25, 2022 at 8:21:41 PM UTC-7 John H Palmieri wrote:

> Will the changeover also mark Sage 10.0? Is there a vision for what Sage 
> 10.0 means?
>
> On Saturday, September 24, 2022 at 8:48:15 PM UTC-7 Matthias Koeppe wrote:
>
>> I've added this to 
>> https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b#conversion-of-trac-tickets-and-the-trac-wiki-to-github
>>  
>> now
>>
>> On Saturday, September 24, 2022 at 5:46:15 PM UTC-7 Matthias Koeppe wrote:
>>
>>> On Saturday, September 24, 2022 at 5:15:11 PM UTC-7 John H Palmieri 
>>> wrote:
>>>
>>>> I think I'm missing part of this. What is the actual path to switching 
>>>> to GitHub? I've seen pages describing how individual development tasks 
>>>> will 
>>>> be converted from trac to GitHub, but what does the overall transition 
>>>> look 
>>>> like?
>>>>
>>>> - Do we just say, before November 1 (or whenever) we're doing 
>>>> everything on trac, and after we're doing everything on GitHub?
>>>>
>>>
>>> Yes, exactly (although we have not discussed the date yet).
>>>
>>> On the switchover day, it would look like this: 
>>> 1. We take Trac offline, reconfigure it to be read-only, bring it online.
>>> 2. Convert all tickets to Issues in a new repo. (This preserves the 
>>> ticket numbers as Issue numbers.)
>>> 3. Final check that the new repo is OK.
>>> 4. Replace sagemath/sage by the new repo.
>>> 5. Announce that sagemath/sage is now open for Issues and PRs.
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5f91d2ee-d54c-47ed-a126-bc1152fa7209n%40googlegroups.com.

Reply via email to