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 wr
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 transiti
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 ever
On Saturday, September 24, 2022 at 9:27:46 AM UTC-7 mathzeta2 wrote:
> Is it possible to choose the issue numbers in GH when making a migration?
> Then, setting a redirect of the form "
> https://trac.sagemath.org/ticket/$TICKET_NUMBER ->
> https://github.com/sagemath/sage/issues/$TICKET_NUMBER"
On 24/09/2022 14:57, kcrisman wrote:
I think part of a solution could be PR templates, which add
structure to the PR description (= the first comment). That
could be a way of adding Authors (and Reviewers) to a
On Sat, Sep 24, 2022 at 9:15 AM Matthias Koeppe
wrote:
>
> On Saturday, September 24, 2022 at 4:57:36 AM UTC-7 kcrisman wrote:
>>>
>>> On another note, I realize that the comment I made 6 years ago after
>>> Volker's comment is still relevant:
>>
>> "There's also the non-trivial (though not block
On Saturday, September 24, 2022 at 4:57:36 AM UTC-7 kcrisman wrote:
> On another note, I realize that the comment I made 6 years ago after
>> Volker's comment is still relevant:
>>
> "There's also the non-trivial (though not blocker, probably) issue that
> zillions of links to trac.sagemath.or
> I think part of a solution could be PR templates, which add structure to
> the PR description (= the first comment). That could be a way of adding
> Authors (and Reviewers) to a PR.
If there's a way to (lightly) enforce that via some kind of bot, that
sounds very reasonable.
On another n
