Hi,
Since trac logins are now disabled, it seems that we cannot edit the 9.8
release tour.
Eric.
Le samedi 7 janvier 2023 à 09:02:07 UTC+1, Matthias Koeppe a écrit :
> It's time to work on the release tour for the upcoming 9.8 release
> https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8
>
Sorry if this is answered somewhere in the new documentation, I couldn't
find it: What is the intended procedure for migrated issues which were in
"needs review" state and already had a branch? Am I to push the branch to
my own fork and create a fresh pull request for each such issue?
--
You re
It is now in
https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8
But we don't have permissions to edit it yet.
On Monday, February 6, 2023 at 5:38:46 PM UTC+9 Eric Gourgoulhon wrote:
> Hi,
>
> Since trac logins are now disabled, it seems that we cannot edit the 9.8
> release tour.
>
On Monday, February 6, 2023 at 5:47:22 PM UTC+9 Lorenz Panny wrote:
Sorry if this is answered somewhere in the new documentation, I couldn't
find it: What is the intended procedure for migrated issues which were in
"needs review" state and already had a branch? Am I to push the branch to
my own
Thank you all for your work!
A minor point: the PR template still says "we are not accepting pull
requests yet".
--
Marc
--
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 e
Le lundi 6 février 2023 à 08:25:30 UTC+1, GMS a écrit :
Huge thanks to everybody involved.
+1
Eric.
--
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-de
Le lundi 6 février 2023 à 09:50:58 UTC+1, Kwankyu Lee a écrit :
It is now in
https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8
OK, very good.
I've updated
https://wiki.sagemath.org/ReleaseTours
accordingly.
Eric.
But we don't have permissions to edit it yet.
On Monday, Februar
Le lundi 6 février 2023 à 09:50:58 UTC+1, Kwankyu Lee a écrit :
It is now in
https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8
But we don't have permissions to edit it yet.
Do you know when/how we can get these permissions? Sage Days 117 have
started this morning and it would be ni
Marc Mezzarobba wrote:
> A minor point: the PR template still says "we are not accepting pull
> requests yet".
Another one (more of a warning to other users actually): apparently
subscriptions to issues have not been migrated; you need to
re-subscribe to issues you are interested in.
--
Marc
--
On Mon, 6 Feb 2023, 09:29 Eric Gourgoulhon, wrote:
>
> Le lundi 6 février 2023 à 09:50:58 UTC+1, Kwankyu Lee a écrit :
> It is now in
>
> https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8
>
> But we don't have permissions to edit it yet.
Can you edit it now? I'd removed "Restrict editi
Thank you for organizing this!
On Monday, 6 February 2023 at 06:07:04 UTC+1 Travis Scrimshaw wrote:
> Hi everyone,
>I know things are a bit hectic with the transition right now. However,
> the deadline for submitting our GSoC proposal is tomorrow (at least for
> me). I would appreciate it i
On Mon, Feb 6, 2023 at 9:07 AM Marc Mezzarobba wrote:
>
> Thank you all for your work!
>
> A minor point: the PR template still says "we are not accepting pull
> requests yet".
I've just fixed this one. We still need to create a real tempate...
>
> --
> Marc
>
> --
> You received this message bec
I just opened an issue (the first on github?), but I could not add labels
either. Perhaps the labels are deactivated for ordinary users?
On Monday, 6 February 2023 at 10:00:52 UTC+1 Kwankyu Lee wrote:
> On Monday, February 6, 2023 at 5:47:22 PM UTC+9 Lorenz Panny wrote:
> Sorry if this is answe
I could also not add labels.
On Monday, February 6, 2023 at 4:44:03 AM UTC-6 axio...@yahoo.de wrote:
> I just opened an issue (the first on github?), but I could not add labels
> either. Perhaps the labels are deactivated for ordinary users?
>
> On Monday, 6 February 2023 at 10:00:52 UTC+1 Kwan
I am unable to pull from upstream, I get a timeout:
$ git pull upstream develop
fatal: unable to connect to github.com:
github.com[0: 140.82.121.3]: errno=Connection timed out
I can ping the same IP address OK. I think I have my remote set OK:
$ git remote -v
origin g...@github.com:JohnCremona
don't use git://, use ssh, i.e.
g...@github.com:sagemath/sage.git
run
$ git remote remove upstream
$ git remote add upstream g...@github.com:sagemath/sage.git
On Mon, Feb 6, 2023 at 12:13 PM John Cremona wrote:
>
> I am unable to pull from upstream, I get a timeout:
>
> $ git pull upstream de
On Mon, 6 Feb 2023 at 12:31, Dima Pasechnik wrote:
> don't use git://, use ssh, i.e.
> g...@github.com:sagemath/sage.git
>
> run
>
> $ git remote remove upstream
> $ git remote add upstream g...@github.com:sagemath/sage.git
>
Thanks Dima, that worked.
>
> On Mon, Feb 6, 2023 at 12:13 PM Joh
After followong the steps given for an existing tree, my develop branch
still followed OLD-ORIGIN. Shouldn't that be orign ?
Le lundi 6 février 2023 à 08:02:59 UTC+1, Matthias Koeppe a écrit :
> https://github.com/sagemath/sage
>
> See
> https://github.com/sagemath/trac-to-github/blob/master/do
On Monday, February 6, 2023 at 11:45:12 PM UTC+9 emanuel.c...@gmail.com
wrote:
After followong the steps given for an existing tree, my develop branch
still followed OLD-ORIGIN. Shouldn't that be orign ?
You remove the develop branch, and make a new one (named develop) from the
remote origin.
No. Make it from the remote upstream, so I think the command is
git branch -D develop; g checkout -b develop upstream/develop
On Monday, February 6, 2023 at 11:51:43 PM UTC+9 Kwankyu Lee wrote:
On Monday, February 6, 2023 at 11:45:12 PM UTC+9 emanuel.c...@gmail.com
wrote:
After followong the s
Or
git branch -D develop; git branch --track develop upstream/develop
On Tuesday, February 7, 2023 at 12:03:39 AM UTC+9 Kwankyu Lee wrote:
No. Make it from the remote upstream, so I think the command is
git branch -D develop; g checkout -b develop upstream/develop
On Monday, February 6, 202
Le lundi 6 février 2023 à 10:47:28 UTC+1, dim...@gmail.com a écrit :
Can you edit it now?
Yes, thanks!
Eric.
I'd removed "Restrict editing to users in teams
with push access only"
Please also note that GitHub wikis are git repos. You can clone them
in the usual way (git clone
https://
Talk will start in about 10min from now at
https://webconf.u-bordeaux.fr/b/vin-g33-6qy
On 03/02/2023, Matthias Koeppe wrote:
> Recording my talk is, of course, fine with me.
>
> On Friday, February 3, 2023 at 1:38:33 AM UTC-8 vdelecroix wrote:
>
>> This could be recorded (if Matthias agree)
Marc Mezzarobba wrote:
> Another one (more of a warning to other users actually): apparently
> subscriptions to issues have not been migrated; you need to
> re-subscribe to issues you are interested in.
Maybe related: search patterns of the form mentions:someone (including
the default filter 'Ever
Marc Mezzarobba wrote:
> Maybe related: search patterns of the form mentions:someone (including
> the default filter 'Everything mentioning you') seem to only return
> issues created after the migration.
...However, involves:@me seems to work.
--
Marc
--
You received this message because you a
The notes of my talk are available at https://hackmd.io/@mkoeppe/HyibcDT2j
On Friday, February 3, 2023 at 8:00:29 AM UTC-8 GMS wrote:
>
> As I have said to Vincent, I can take care of making the video.
> I shall submit it to Matthias before making it available for publication.
>
> Guillermo
>
>
I've noted this in https://github.com/sagemath/trac-to-github/issues/184
On Monday, February 6, 2023 at 9:57:40 AM UTC-8 Marc Mezzarobba wrote:
> Marc Mezzarobba wrote:
> > Maybe related: search patterns of the form mentions:someone (including
> > the default filter 'Everything mentioning you') s
Dear Sage developers,
As the migration of the Trac tickets to GitHub issues was completed
yesterday night, I am stepping away for a little while from working on the
development infrastructure of the project.
In the next weeks, the developer community should discuss, implement, and
document the n
On Mon, Feb 6, 2023 at 8:17 PM Matthias Koeppe
wrote:
>
> Dear Sage developers,
> As the migration of the Trac tickets to GitHub issues was completed
yesterday night, I am stepping away for a little while from working on the
development infrastructure of the project.
🙏 you did wonders!
> In the
Thank you !
But I already restarted in a fresh tree, which gad the unexpected side
effect of seriously deflating its size (9,4 GB vs 24 GB in the old tree...).
The migration guide should be amended...
Le lundi 6 février 2023 à 16:06:34 UTC+1, Kwankyu Lee a écrit :
> Or
>
> git branch -D devel
The video should be available at
https://webconf.u-bordeaux.fr/b/vin-g33-6qy at the bottom of the page.
Vincent
https://visio.u-bordeaux.fr/playback/presentation/2.0/playback.html?meetingId=887e0bfc02a9a556a1ea79a2c1d59e3cb7717460-1675700189259
On 06/02/2023, Matthias Koeppe wrote:
> The notes
https://github.com/sagemath/sage
See
https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
for a transition guide from Trac to GitHub.
Gratuliere and congratulations to all the many people who made this huge
task possible!
--
You received this message be
32 matches
Mail list logo
