What is the proposed workflow to merge the develop branch after a new
release into PR (or other) branches of your fork (i.e re-basing)? Obviously
this is possible by pushing on sync in the web interface or typing gh repo
sync USERNAME/sage -b branch in the command line. But how do you resolve
https://trac.sagemath.org/ticket/34536
There, Luschny!
On why I initially only changed B_1 = +½, I have a rebuttable demand of my
code: *it must be as beautiful as the maths it implements*. Having
bernoulli_gen() (your generalised Bernoulli function as implemented in the
SageMath ticket) alongsid
Thank you for coming, Luschny.
I not only wholeheartedly believe B_1 = +½ and that there is no convention
about it, but also that I believe in the reality and usefulness of the
Bernoulli, Euler and other functions you defined in your 2020 paper.
When I implemented those functions in SymPy there w
On Wednesday, September 14, 2022 at 1:50:43 AM UTC-7 tobias...@gmail.com
wrote:
> Smaller suggestions can also be made through the github web interface as
> part of the pullrequest review, see
> https://egghead.io/lessons/github-add-suggestions-in-a-github-pr-review
> and
> https://docs.githu
I think for now we only need to describe the process up to the point of
"positive review".
The discussion on how to do release management etc. is best held when
Volker finds the time to join the discussion on these things.
On Wednesday, September 14, 2022 at 1:58:40 AM UTC-7 tobias...@gmail.com
I am in the middle of picking a kid from school at that time so I won't
be there for that one tomorrow. Filled my bit in the pool.
On 15/09/22 06:36, Matthias Koeppe wrote:
Friday afternoon, 3:15pm Auckland (New Zealand)
François
--
You received this message because you are subscribed to the
On Wednesday, September 14, 2022 at 11:36:19 AM UTC-7 Matthias Koeppe wrote:
> We would hope that there is enough interest to make it a weekly meeting,
> possibly alternating between these two times so that we can include a
> convenient time for everyone in all timezones.
> In order to find the
I would be interested in participating. However my thursdays are usually
busy (every two weeks). I'll definitely attend if it fits my schedule. I'm
in EDT, UTC-4 timezone.
Best,
David A.
Le mercredi 14 septembre 2022 à 14:36:19 UTC-4, Matthias Koeppe a écrit :
> Dear all,
> William, Dima, and
Dear all,
William, Dima, and I would like to invite all of you to join a 30-minute
Sage developer call on Zoom. The purpose is: Short announcements/demos,
socializing, brief discussions, having coffee together.
This sort of weekly meeting has become pretty standard in big successful
open-source
I could have swore that I did that command (at least once!). Those threads
above also suggest Xcode CLT needs to be > version 13, which I have.
Nevertheless, I ran through the whole process from start to finish again,
and this time it worked!
--
You received this message because you are subsc
tl;dr, 80 lines, sorry.
I think there is a better alternative than changing the current
implementation of the Bernoulli numbers.
Fredrik: "The sign convention for B_1 is fairly arbitrary, ..."
Calling the question a 'convention' sets a wrong framing from
the start. Conventions are treated diff
On Wednesday, September 14, 2022 at 10:10:47 AM UTC-7 john.c...@gmail.com
wrote:
> GH issues can also be used as "metatickets" on trac, with a checklist of
> things to do which can be checked off as they are dealt with by various
> PRs.
>
Thanks, I've added this
to https://github.com/sagema
GH issues can also be used as "metatickets" on trac, with a checklist of
things to do which can be checked off as they are dealt with by various
PRs. We often do this with the LMFDB whose code development is done on GH
via issues and PRs as described by others here. We have fewer developers
of c
Have you forgotten to
source .homebrew-build-env
?
On Wed, 14 Sep 2022, 15:10 Dima Pasechnik, wrote:
> this
>
> https://bitbucket.org/malb/m4rie/issues/23/trying-to-compile-on-apple-m1
>
> and trac tickets mentioned there might be related.
>
>
> On Wed, 14 Sep 2022, 14:51 Ben Salisbury, wrot
this
https://bitbucket.org/malb/m4rie/issues/23/trying-to-compile-on-apple-m1
and trac tickets mentioned there might be related.
On Wed, 14 Sep 2022, 14:51 Ben Salisbury, wrote:
> I'm trying to build from source on a MacBook Air with the new m2 chip, and
> the build fails at m4ri. I've tried
I think we need also another branch "merge-queue" which serves as the
target for pull requests, with branch protection rules linear history,
require positive review and checks.
Also "Release Manager @vbraun merges positively reviewed tickets into his
branch https://github.com/vbraun/sage"; shou
Smaller suggestions can also be made through the github web interface as
part of the pullrequest review, see
https://egghead.io/lessons/github-add-suggestions-in-a-github-pr-review and
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/in
On Wed, 14 Sep 2022, 03:15 Nils Bruin, wrote:
> On Tuesday, 13 September 2022 at 14:04:24 UTC-7 dim...@gmail.com wrote:
>
>>
>>
>> On Tue, 13 Sep 2022, 21:56 Nils Bruin, wrote:
>>
>>> I'd actually be interested in knowing what the substitute for "git trac
>>> checkout ..." is. Because with trac,
18 matches
Mail list logo
