On Saturday, September 17, 2022 at 8:43:55 PM UTC-7 Kwankyu Lee wrote:
> On Sunday, September 18, 2022 at 9:55:10 AM UTC+9 Matthias Koeppe wrote:
>
>> The conversion of the Trac tickets to GitHub Issues/PRs only works in one
>> shot. Incrementally syncing updates from Trac to existing issues is n
On Sunday, September 18, 2022 at 9:55:10 AM UTC+9 Matthias Koeppe wrote:
> The conversion of the Trac tickets to GitHub Issues/PRs only works in one
> shot. Incrementally syncing updates from Trac to existing issues is not
> possible.
> This means that we cannot continue to operate Trac after
On Saturday, September 17, 2022 at 5:44:52 PM UTC-7 Kwankyu Lee wrote:
> On Friday, September 16, 2022 at 6:30:05 PM UTC+9 dim...@gmail.com wrote:
>
> I'd rather focus the vote primarily on the move away from trac, ...
>
>
> What would the move mean precisely? As there are two things to be done
>
On Friday, September 16, 2022 at 6:30:05 PM UTC+9 dim...@gmail.com wrote:
I'd rather focus the vote primarily on the move away from trac, ...
What would the move mean precisely? As there are two things to be done
(1) The release manager declares to merge tickets only from Github, not
from Trac
On Sat, 17 Sep 2022, 13:22 kcrisman, wrote:
>
> I think the 1st vote should be on moving from trac to Git**b; besides it
>> appears that, technically, move to Github is much easier than to Gitlab
>> (while there are migration tools available for trac->github, I could not
>> find anything for trac
> I think the 1st vote should be on moving from trac to Git**b; besides it
> appears that, technically, move to Github is much easier than to Gitlab
> (while there are migration tools available for trac->github, I could not
> find anything for trac->gitlab).
>
> On the other hand github->gitla
On Saturday, September 17, 2022 at 2:07:21 AM UTC-7 mpn7...@gmail.com wrote:
> > Only developers who work with tickets that add packages or make changes
> > to the build infrastructure run into the problem that the downloaded
> > "configure" is not suitable.
>
> And yet I think this is worth ad
Only developers who work with tickets that add packages or make changes
to the build infrastructure run into the problem that the downloaded
"configure" is not suitable.
And yet I think this is worth addressing. Those contributors who add
packages may, just like me, know nothing of sage's buil
