Re: [sage-devel] Milestones

On Fri, Oct 14, 2016 at 5:01 PM, Jeroen Demeyer wrote: > On 2016-10-14 16:23, Erik Bray wrote: >> >> sage-duplicate/invalid/wontfix is a terrible "milestone" and I >> wouldn't mind getting rid of that too. That's a resolution status for >> an issue, not project goal. > >

Re: [sage-devel] Milestones

> On 17/10/2016, at 22:33, Erik Bray wrote: > > My point is, as it is I see no way to divine when or why a Sage > release is coming out. Release early, release often. In my experience in the last 8 years, especially release often - it has slowed down a bit, but it is

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 11:23 AM, Jori Mäntysalo wrote: > On Mon, 17 Oct 2016, Erik Bray wrote: > >> Does Sage have *any* kind of roadmap planning? > > > No. > > What kind of roadmap it could be? If some developers are interested in graph > theory, how to make them to add

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 11:54 AM, Francois Bissey wrote: > >> On 17/10/2016, at 22:42, Erik Bray wrote: >> >> On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey >> wrote: >>> On 17/10/2016, at 22:33,

Re: [sage-devel] Milestones

On Fri, Oct 14, 2016 at 7:24 PM, Jori Mäntysalo wrote: > On Fri, 14 Oct 2016, Jeroen Demeyer wrote: > >> As far as I know, the only real use-case for milestone is a milestone like >> `sage-duplicate/invalid/wontfix` or `sage-pending`. I think that every >> milestone of the

Re: [sage-devel] Milestones

> On 17/10/2016, at 22:42, Erik Bray wrote: > > On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey > wrote: >> >>> On 17/10/2016, at 22:33, Erik Bray wrote: >>> >>> My point is, as it is I see no way to divine

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey wrote: > >> On 17/10/2016, at 22:33, Erik Bray wrote: >> >> My point is, as it is I see no way to divine when or why a Sage >> release is coming out. > > Release early, release often. In my

Re: [sage-devel] Milestones

On Mon, 17 Oct 2016, Erik Bray wrote: Does Sage have *any* kind of roadmap planning? No. What kind of roadmap it could be? If some developers are interested in graph theory, how to make them to add more linear algebra code to Sage? -- Jori Mäntysalo

Re: [sage-devel] Milestones

On Fri, Oct 14, 2016 at 5:25 PM, Volker Braun wrote: > I don't really use the milestones except for the > sage-duplicate/invalid/wontfix which indicates that there is nothing to > merge. > > We don't really use trac for roadmap planning so there is no real > significance to

Re: [sage-devel] Milestones

On Mon, 17 Oct 2016, Erik Bray wrote: I'm mostly just talking about a policy that generates a (rough) release schedule. OK, so you mean something like Fedora release, where it was decided about half a year ago that version 25 will be out at 2016-11-08 (and that was later changed to

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 11:40 AM, Jori Mäntysalo wrote: > On Mon, 17 Oct 2016, Erik Bray wrote: > >> I'm mostly just talking about a policy that generates a (rough) >> release schedule. > > > OK, so you mean something like Fedora release, where it was decided about > half a

[sage-devel] Re: Customizin failed login -page

On Monday, October 17, 2016 at 6:46:52 AM UTC, Jori Mäntysalo wrote: > > See https://sage.sis.uta.fi/ . I just learnt that our students do not see > the text "This is part of services available to students of SIS unit. To > get an account see (link)this page(/link)." > I certainly see this;

Re: [sage-devel] NTL 1v0.1.0

On 15/10/16 03:28, Victor Shoup wrote: After much foot dragging, and with the help and encouragement of folks here at sage-devel, I've finally got around to making (nearly) all of the packaging/build features that were requested. The big ones are locally generated libtool and $(MAKE). I did not

Re: [sage-devel] NTL 1v0.1.0

> On 18/10/2016, at 17:18, Victor Shoup wrote: > > I see. I don't do it on purpose... > I looked at some singular source files, but I don't know if I have the most > recent. But it looks like they are trying to look inside ntl's ZZ > representation. That's a big no no.

Re: [sage-devel] NTL 1v0.1.0

That said, I think the quickest fix is to replace static_cast with (long*). But it's not a good long term solution. -- 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

Re: [sage-devel] NTL 1v0.1.0

Interesting. Looks like the singular code is using internal, undocumented NTL interfaces. I work very hard to keep the documented interfaces stable and reliable, but I can't guarantee anything for undocumented interfaces. If singular is going to do that, they will have to use ifdefs or

Re: [sage-devel] NTL 1v0.1.0

> On 18/10/2016, at 16:49, Victor Shoup wrote: > > Interesting. Looks like the singular code is using internal, undocumented NTL > interfaces. I work very hard to keep the documented interfaces stable and > reliable, but I can't guarantee anything for undocumented

Re: [sage-devel] NTL 1v0.1.0

I see. I don't do it on purpose... I looked at some singular source files, but I don't know if I have the most recent. But it looks like they are trying to look inside ntl's ZZ representation. That's a big no no. Right now, the only semi efficient way to do this with the existing interface

Re: [sage-devel] NTL 1v0.1.0

Hans does seem to fix most bugs that are reported unless they require extensive rewriting or aren't considered bugs. It looks like this code was written with the expectation that it would be maintained, so I'd just report it to him [1]. Bill. [1]

Re: [sage-devel] NTL 1v0.1.0

Good! But it should be determined if there is an interface that ntl could provide so that this problem goes away -- 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] Customizin failed login -page

See https://sage.sis.uta.fi/ . I just learnt that our students do not see the text "This is part of services available to students of SIS unit. To get an account see (link)this page(/link)." A wish for those making frontend(s) to SageMath: please make it easy to customize failed login -page.

Re: [sage-devel] Re: Customizin failed login -page

On Mon, 17 Oct 2016, Dima Pasechnik wrote: See https://sage.sis.uta.fi/ . I just learnt that our students do not see the text "This is part of services available to students of SIS unit. To get an account see (link)this page(/link)." I certainly see this Sorry,

Re: [sage-devel] Milestones

On Mon, 17 Oct 2016, Francois Bissey wrote: To move to the kind of release schedule you are talking about we’ll need a new release manager who has the vision for this kind of things. What is Volker's vision? I.e. do he have some plan in his head about when to release 7.6? I think that

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 12:29 PM, Jori Mäntysalo wrote: > On Mon, 17 Oct 2016, Francois Bissey wrote: > >> To move to the kind of release schedule you are talking about >> we’ll need a new release manager who has the vision for this kind >> of things. > > > What is Volker's

Re: [sage-devel] Milestones

On 2016-10-17 11:38, Erik Bray wrote: But you're using a "milestone" to set what is effectively a resolution status. Why should "normal" users be able to set sage-duplicate/invalid/wontfix? That seems like a decision for a maintainer to make, at which point they can close the ticket. The way

[sage-devel] Re: puzzling dev.upload_ssh_key() in developer manual

Thanks, I will definitely look into it. -- 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 post to this group, send

Re: [sage-devel] Milestones

On 2016-10-17 11:33, Erik Bray wrote: I'm mostly just talking about a policy that generates a (rough) release schedule. Which problems would that solve? I don't really see the problem with the current "release whenever it's done" way of doing things, where "whenever it's done" is largely

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 3:44 PM, Jeroen Demeyer wrote: > On 2016-10-17 15:27, Erik Bray wrote: >> >> What problems does it solve? First of all, I already mentioned >> one--nobody but the "release manager" knows when a release is expected >> to come out > > > Who cares

Re: [sage-devel] Milestones

On 2016-10-17 16:32, Erik Bray wrote: If a critical bug is found in released software it makes absolute sense to prioritize a release for that bug. Besides, isn't this exactly what I said? That the "release schedule should depend on the urgency of open issues." If there is a very important

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 4:50 PM, Jeroen Demeyer wrote: > On 2016-10-17 16:32, Erik Bray wrote: >> >> If a critical >> bug is found in released software it makes absolute sense to >> prioritize a release for that bug. > > > Besides, isn't this exactly what I said? That the

Re: [sage-devel] Milestones

On Monday, October 17, 2016 at 11:42:46 AM UTC+2, Erik Bray wrote: > > On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey > wrote: > > Release early, release often. In my experience in the last 8 years, > > especially release often - it has slowed down a bit, but

Re: [sage-devel] Milestones

On Mon, 17 Oct 2016, Jeroen Demeyer wrote: Who cares when a release is expected to come out? I do, but very, very slightly. We have a maintenance break at every monday after second tuesday of the week. (That is, six days after Microsoft patch day.) I could plan upgrades if I know in

Re: [sage-devel] Milestones

On 2016-10-17 16:32, Erik Bray wrote: If a critical bug is found in released software it makes absolute sense to prioritize a release for that bug. First of all, there have occasionally been bugfix releases of Sage: * http://www.sagemath.org/changelogs/sage-5.0.1.txt *

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 4:48 PM, Jeroen Demeyer wrote: > On 2016-10-17 16:32, Erik Bray wrote: >> >> If a critical >> bug is found in released software it makes absolute sense to >> prioritize a release for that bug. > > > First of all, there have occasionally been bugfix

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 2:08 PM, Jeroen Demeyer wrote: > On 2016-10-17 11:38, Erik Bray wrote: >> >> But you're using a "milestone" to set what is effectively a resolution >> status. Why should "normal" users be able to set >> sage-duplicate/invalid/wontfix? That seems

Re: [sage-devel] Milestones

On 2016-10-17 15:27, Erik Bray wrote: What problems does it solve? First of all, I already mentioned one--nobody but the "release manager" knows when a release is expected to come out Who cares when a release is expected to come out? what the purpose of that release is, and what one can

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 2:15 PM, Jeroen Demeyer wrote: > On 2016-10-17 11:33, Erik Bray wrote: >> >> I'm mostly just talking about a policy that generates a (rough) >> release schedule. > > > Which problems would that solve? I don't really see the problem with the >

Re: [sage-devel] Overcommitted memory and error handling

On 2016-10-17 17:40, Jori Mäntysalo wrote: but due to overcommit there is no exception raised. That's really the fault of the OS, not the fault of Sage. Side comment: don't use x = malloc(n) memset(x, 0, n) There is calloc for that. And *certainly* don't use NULL, use 0 for that. -- You

Re: [sage-devel] Milestones

On Mon, Oct 17, 2016 at 5:00 PM, Ralf Stephan wrote: > On Monday, October 17, 2016 at 11:42:46 AM UTC+2, Erik Bray wrote: >> >> On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey >> wrote: >> > Release early, release often. In my experience in the

[sage-devel] Overcommitted memory and error handling

Is it even theoretically possible to handle something like Graph(10^10)? That will crash at the line memset(self.vertices, NULL, nverts * self.hash_length * sizeof(SparseGraphBTNode *)) Before that we have sig_malloc(nverts * self.hash_length * . . . if not . . . raise

[sage-devel] Re: slow doctest number_field_element.pyx on my machine

this is now https://trac.sagemath.org/ticket/21719#ticket Am Dienstag, 4. Oktober 2016 22:13:50 UTC+2 schrieb Volker Braun: > > I've seen that time out often on the buildbot, too. Please, somebody > replace the test in there by something more reasonable. > > > > On Tuesday, October 4, 2016 at