Re: [sage-release] Re: Sage 8.2.rc4 released
On Sat, May 5, 2018 at 10:21 PM, wrote: > On Thursday, April 26, 2018 at 7:11:52 AM UTC-7, Erik Bray wrote: >> >> >> Given such a branch to work in, it becomes less "urgent" to finish a >> release since it no longer needs to block normal development progress. >> Of course, you still don't want to spend forever getting a release >> out, but at least the release itself doesn't become a blocker. >> > Having some urgency to completing a release once it's decided to start it is > probably beneficial as a whole. > > However, in the current situation we've have sage8.2rc0 more than a month > ago and progress on the development branch is at a complete standstill at > the moment. I don't think this is healthy for the project. I don't have the > time or expertise to help with that myself, but I hope others do and are > able to dislodge the current jam. My suggestion for how to resolve this seems obvious and straightforward. The only objection I've seen is "but what will the patchbots do?" But with a better documented process that is easily resolved. If it's not clear, shall I write up some more formal documentation for my proposed process? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On Thursday, April 26, 2018 at 7:11:52 AM UTC-7, Erik Bray wrote: > > > Given such a branch to work in, it becomes less "urgent" to finish a > release since it no longer needs to block normal development progress. > Of course, you still don't want to spend forever getting a release > out, but at least the release itself doesn't become a blocker. > > Having some urgency to completing a release once it's decided to start it is probably beneficial as a whole. However, in the current situation we've have sage8.2rc0 more than a month ago and progress on the development branch is at a complete standstill at the moment. I don't think this is healthy for the project. I don't have the time or expertise to help with that myself, but I hope others do and are able to dislodge the current jam. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On Thu, Apr 26, 2018 at 3:55 PM, Jeroen Demeyer wrote: > On 2018-04-26 12:29, Erik Bray wrote: >> >> But I'm told that's somehow impossible for Sage. > > > I don't think that it's fundamentally impossible. But it would require > changes to certain tools. For example, which branch should the patchbot use? > > Allow me to mention what I did when I was release manager: I also always had > a linear release history, but I already started working privately on future > releases, merging tickets and testing them on the buildbot. So once a final > release was made, tickets were fully ready to be merged in the next beta. If > there was a sufficient backlog, this would for example mean that Sage 8.2, > 8.3.beta0 and 8.3.beta1 would be released all on the same day. If there were release branches (say, release-8.1, release-8.2, etc.) that are more or less equivalent to what you described, the patchbot runner (as long as we're still even using it :) could be configured to build tickets intended for those milestones either only against those branches (if they exist) or against the latest "develop", or both. Under the current process you might only make a release- branch alongside the first release candidate. That's the point at which you want to curtail exactly which changes get merged, so that a releasable product can be converged on. Given such a branch to work in, it becomes less "urgent" to finish a release since it no longer needs to block normal development progress. Of course, you still don't want to spend forever getting a release out, but at least the release itself doesn't become a blocker. Updating the tooling (the patchbot, etc.) is not so terrible. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On 2018-04-26 12:29, Erik Bray wrote: But I'm told that's somehow impossible for Sage. I don't think that it's fundamentally impossible. But it would require changes to certain tools. For example, which branch should the patchbot use? Allow me to mention what I did when I was release manager: I also always had a linear release history, but I already started working privately on future releases, merging tickets and testing them on the buildbot. So once a final release was made, tickets were fully ready to be merged in the next beta. If there was a sufficient backlog, this would for example mean that Sage 8.2, 8.3.beta0 and 8.3.beta1 would be released all on the same day. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On 2018-04-26 12:21, Dima Pasechnik wrote: I am really not looking forward to supporting yet another OSX realease that uses gcc :-( Alternatively, one could argue: let's release Sage 8.2 *now* and try to have a Sage 8.3 with clang soon after that. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On 26/04/2018 12:29, Erik Bray wrote: On Thu, Apr 26, 2018 at 11:16 AM, wrote: Hello, can we hope to have 8.2 released and move on to 8.3.beta soon ? I am really worried by the 161 positive-reviewed tickets that have been accumulating, and by the potential rebase work that will be triggered. +1 I know there are supposed issues related to continuous integration (which I would think are fixable) but on a normal project it's possible to create a branch (e.g. 8.2-release) into which only patches intended for that release are merged, while new patches can still be merged into the master branch so that development can proceed apace. +2 These should be two distinct problems: * merging tickets in positive review * making a stable release for which most if not all critical problems are solved The former is urging the second and it's not good for release quality. Vincent -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On Thu, Apr 26, 2018 at 12:38 AM, wrote: > On Wednesday, April 25, 2018 at 2:31:55 PM UTC-7, Steven Trogdon wrote: >> Is this a consequence of fixing the banner >> >> >> >> LC_ALL=C ./sage >> SageMath version 8.2.rc4, Release Date: 2018-04-20 >> >> and thus no banner, or has it always been this way? I only noticed because I >> had changed LC_ALL for some other purpose. I usually have LC_ALL unset with >> the other LC_ variables set individually. > > Yes, it is. With LC_ALL=C we get: > > sage: print(sage.misc.banner.banner_text()) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-69: > ordinal not in range(128) > > Previously, the banner was written into a file at build-time and displayed by > "cat"ing that file, so the contents of the file didn't pass through a Python > codec at runtime. > > I think python is basically correct in doing this: if the locale is C then > only ascii should be sent to the stdout, right? Yes, that's more or less the correct behavior in the current Python (although there are proposals to force Python to use LC_CTYPE=C.UTF-8 if LC_CTYPE=C). But if the current locale uses a non-unicode encoding then it assumes to only send ASCII. The sage.misc.banner.banner() function catches that UnicodeEncodeError and returns the plain banner. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On Thu, Apr 26, 2018 at 11:16 AM, wrote: > Hello, > > can we hope to have 8.2 released and move on to 8.3.beta soon ? I am really > worried by the 161 positive-reviewed tickets that have been accumulating, > and by the potential rebase work that will be triggered. I know there are supposed issues related to continuous integration (which I would think are fixable) but on a normal project it's possible to create a branch (e.g. 8.2-release) into which only patches intended for that release are merged, while new patches can still be merged into the master branch so that development can proceed apace. But I'm told that's somehow impossible for Sage. > Le vendredi 20 avril 2018 22:28:15 UTC+2, Volker Braun a écrit : >> >> As always, you can get the latest beta version from the "develop" git >> branch. Alternatively, the self-contained source tarball is at >> http://www.sagemath.org/download-latest.html >> >> This should be the last rc, so if you want to test it now is the right >> time! >> >> f46abe6c0e (tag: 8.2.rc4, trac/develop) Updated SageMath version to >> 8.2.rc4 >> 88f80f584b Trac #25217: Fix test regression in banner() >> cee7c1d6d3 Trac #25196: sage -gdb abort >> 8fc1b6ad67 Trac #25177: cython() does not work in Jupyter >> b47963fb84 Trac #25078: ./sage -f sagelib no longer works >> a9d274b933 (tag: 8.2.rc3) Updated SageMath version to 8.2.rc3 >> > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
I am really not looking forward to supporting yet another OSX realease that uses gcc :-( I really think it was too quick to decide to unroll the clang support, the main reason being "not enough testing". Given that several weeks have passed since, and the needed gfan workaround tested, I suppose, by a number of people, I really think it's a waste of effort to have yet another gcc-using OSX release. Dima On Thursday, April 26, 2018 at 12:54:43 PM UTC+3, Jeroen Demeyer wrote: > > On 2018-04-26 11:16, fchap...@gmail.com wrote: > > I am > > really worried by the 161 positive-reviewed tickets that have been > > accumulating > > +1 > > There have been releases with less tickets than that. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On 2018-04-26 11:16, fchapot...@gmail.com wrote: I am really worried by the 161 positive-reviewed tickets that have been accumulating +1 There have been releases with less tickets than that. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
Hello, can we hope to have 8.2 released and move on to 8.3.beta soon ? I am really worried by the 161 positive-reviewed tickets that have been accumulating, and by the potential rebase work that will be triggered. Frederic Le vendredi 20 avril 2018 22:28:15 UTC+2, Volker Braun a écrit : > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > This should be the last rc, so if you want to test it now is the right > time! > > f46abe6c0e (tag: 8.2.rc4, trac/develop) Updated SageMath version to 8.2.rc4 > 88f80f584b Trac #25217: Fix test regression in banner() > cee7c1d6d3 Trac #25196: sage -gdb abort > 8fc1b6ad67 Trac #25177: cython() does not work in Jupyter > b47963fb84 Trac #25078: ./sage -f sagelib no longer works > a9d274b933 (tag: 8.2.rc3) Updated SageMath version to 8.2.rc3 > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
On Wednesday, April 25, 2018 at 2:31:55 PM UTC-7, Steven Trogdon wrote: > Is this a consequence of fixing the banner > > > > LC_ALL=C ./sage > SageMath version 8.2.rc4, Release Date: 2018-04-20 > > and thus no banner, or has it always been this way? I only noticed because I > had changed LC_ALL for some other purpose. I usually have LC_ALL unset with > the other LC_ variables set individually. Yes, it is. With LC_ALL=C we get: sage: print(sage.misc.banner.banner_text()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-69: ordinal not in range(128) Previously, the banner was written into a file at build-time and displayed by "cat"ing that file, so the contents of the file didn't pass through a Python codec at runtime. I think python is basically correct in doing this: if the locale is C then only ascii should be sent to the stdout, right? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
Is this a consequence of fixing the banner LC_ALL=C ./sage SageMath version 8.2.rc4, Release Date: 2018-04-20 and thus no banner, or has it always been this way? I only noticed because I had changed LC_ALL for some other purpose. I usually have LC_ALL unset with the other LC_ variables set individually. On Friday, April 20, 2018 at 3:28:15 PM UTC-5, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > This should be the last rc, so if you want to test it now is the right > time! > > f46abe6c0e (tag: 8.2.rc4, trac/develop) Updated SageMath version to 8.2.rc4 > 88f80f584b Trac #25217: Fix test regression in banner() > cee7c1d6d3 Trac #25196: sage -gdb abort > 8fc1b6ad67 Trac #25177: cython() does not work in Jupyter > b47963fb84 Trac #25078: ./sage -f sagelib no longer works > a9d274b933 (tag: 8.2.rc3) Updated SageMath version to 8.2.rc3 > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull develop, parallel (-j16) build OK and make ptestlong passed except for a few transient errors to due to "Jmol failed to create file", as usual on this computer (race error?). All the involved doctests are passed when run standalone. Eric. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
On Sat, Apr 21, 2018 at 5:03 PM, John H Palmieri wrote: > > > On Saturday, April 21, 2018 at 1:28:18 AM UTC-7, Volker Braun wrote: >> >> At the end of the day, this just wastes some time on initial build -> not >> a blocker. If somebody comes up with a fix in the next 24h I'll merge it. > > > Has the CEO declared some deadline for the release? I must have missed that. > Otherwise, why release flawed software that will inconvenience anyone > building on OS X? It's the second build, not the initial build – if you > don't remember that it's an issue, it's the second build. So the typical > workflow will be: run make, switch to another branch to do some development, > run make again, at which point you have to wait for an hour and half even > though you just touched one py file. So as long as this is a bug, you have > to run make twice to get something usable for development. +1 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
2018-04-21 10:47 GMT+02:00 Samuel Lelièvre : > > Under macOS 10.10.5 Yosemite, starting from the tarball, > the build fails on cysignals-1.7.0 (this was also the case > for 8.2.rc3, while all previous rc and beta compiled fine). > > Here is the corresponding log file: > > http://www.math.u-psud.fr/~lelievre/t/cysignals-1.7.0.p0.log > > I will try applying the ticket that upgrades to cysignals-1.7.1 > > - #25189: Upgrade cysignals to version 1.7.1 > https://trac.sagemath.org/ticket/25189 > > and report back. > > Samuel > After applying #25189, the build still fils. Log at: http://www.math.u-psud.fr/~lelievre/t/cysignals-1.7.1.log -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
Its just that: an inconvenience. Its not the only bug, nor the worst bug. We'll be switching to using clang on osx anyways, then you'll need zero gcc builds. Since you'll most likely base your branch off develop, you should be clamoring for faster develop releases... On Saturday, April 21, 2018 at 5:03:33 PM UTC+2, John H Palmieri wrote: > > > > On Saturday, April 21, 2018 at 1:28:18 AM UTC-7, Volker Braun wrote: >> >> At the end of the day, this just wastes some time on initial build -> not >> a blocker. If somebody comes up with a fix in the next 24h I'll merge it. >> > > Has the CEO declared some deadline for the release? I must have missed > that. Otherwise, why release flawed software that will inconvenience anyone > building on OS X? It's the second build, not the initial build – if you > don't remember that it's an issue, it's the second build. So the typical > workflow will be: run make, switch to another branch to do some > development, run make again, at which point you have to wait for an hour > and half even though you just touched one py file. So as long as this is a > bug, you have to run make twice to get something usable for development. > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
On Saturday, April 21, 2018 at 1:28:18 AM UTC-7, Volker Braun wrote: > > At the end of the day, this just wastes some time on initial build -> not > a blocker. If somebody comes up with a fix in the next 24h I'll merge it. > Has the CEO declared some deadline for the release? I must have missed that. Otherwise, why release flawed software that will inconvenience anyone building on OS X? It's the second build, not the initial build – if you don't remember that it's an issue, it's the second build. So the typical workflow will be: run make, switch to another branch to do some development, run make again, at which point you have to wait for an hour and half even though you just touched one py file. So as long as this is a bug, you have to run make twice to get something usable for development. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
Yosemite is unsupported by Apple. You are running with unpatched security issues (including, but not limited to, spectre/meltdown) On Saturday, April 21, 2018 at 10:47:53 AM UTC+2, Samuel Lelievre wrote: > > Under macOS 10.10.5 Yosemite, starting from the tarball, > the build fails on cysignals-1.7.0 (this was also the case > for 8.2.rc3, while all previous rc and beta compiled fine). > > Here is the corresponding log file: > > http://www.math.u-psud.fr/~lelievre/t/cysignals-1.7.0.p0.log > > I will try applying the ticket that upgrades to cysignals-1.7.1 > > - #25189: Upgrade cysignals to version 1.7.1 > https://trac.sagemath.org/ticket/25189 > > and report back. > > Samuel > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Re: Sage 8.2.rc4 released
Under macOS 10.10.5 Yosemite, starting from the tarball, the build fails on cysignals-1.7.0 (this was also the case for 8.2.rc3, while all previous rc and beta compiled fine). Here is the corresponding log file: http://www.math.u-psud.fr/~lelievre/t/cysignals-1.7.0.p0.log I will try applying the ticket that upgrades to cysignals-1.7.1 - #25189: Upgrade cysignals to version 1.7.1 https://trac.sagemath.org/ticket/25189 and report back. Samuel -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
At the end of the day, this just wastes some time on initial build -> not a blocker. If somebody comes up with a fix in the next 24h I'll merge it. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
On Friday, April 20, 2018 at 1:28:15 PM UTC-7, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > As with 8.2.rc3 (and earlier versions, now that I've checked), running 'make' and then 'make' again builds too many packages. I think that what is happening is that when gcc is required, the top-level configure file gets modified in the middle of the first make process (just before building gcc?), so the second make process sees a new configure file, runs it again, and something then triggers many packages to be rebuilt: patch, pkgconf, zlib, yasm, ... This needs to be fixed before 8.2 is released. I've opened https://trac.sagemath.org/ticket/25221. -- John -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Sage 8.2.rc4 released
On Friday, April 20, 2018 at 1:28:15 PM UTC-7, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > As with rc3, it is not self-contained: there is no gcc tarball. -- John -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
