Hi all,
With 18 people voting there was a relevant tie. The new committee is
Nils Bruin (nbr...@sfu.ca, nbruin on github) - sorry again for the earlier
misspelling!
J-P Labbé (jeanphilippela...@gmail.com, jplab on github)
John Palmieri (jhpalmier...@gmail.com, jhpalmieri on github)
Viviane Pons (
Congratulations!!!
--
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://group
Back again with more class questions and general advice help
While getting all the old sage code into this new project, I realised there
are places where we really rely on the underlying curve classes. One
example is that we need
```
def dimension():
return 1
```
To avoid some crashes, but
Dear all:
Please take the time to participate in the voting process for the
"disputed" PRs.
https://github.com/sagemath/sage/pulls?q=is%3Aopen+label%3Adisputed+is%3Apr+label%3A%22s%3A+needs+review%22%2C%22s%3A+positive+review%22+sort%3Aupdated-desc
Participation matters!
Matthias
--
You recei
I will echo Matthias here. We just spent multiple months working out this
new process. In order to make it work, people need to help make judgements
about which of these PRs should proceed and be included in Sage.
I understand that participating in these particular PRs can be daunting:
the peopl
These disputed PRs under voting need input from the sage community.
I think the release manager should deal with a disputed PR that got
"positive review" from voting separately and give at least a week or two
before deciding on it (to merge).
--
You received this message because you are subsc
