[sage-release] Re: Sage 8.2 released
I tried it.. I failed the first time because I did not used ./configure and gcc package was not used. With ./configure, gcc was loaded, python2 is OK but python3 still fails because of crypt module. El lunes, 7 de mayo de 2018, 16:41:43 (UTC+2), John H Palmieri escribió: > > You could try setting the environment variable SAGE_INSTALL_GCC=yes to > force Sage to build its own version of gcc. > > > On Monday, May 7, 2018 at 6:56:53 AM UTC-7, Enrique Artal wrote: >> >> I have tried, but there are too many dependences. I will wait for >> binaries. I tried to compile on two computers; In one of them python3 was >> compiled but python2 failed on both. thanks for the tip, anyway. >> >> El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió: >>> >>> You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's >>> known to Python people this this does not work... >>> Can you install gcc-7 and make it the default compiler? >>> >>> On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote: I was unable to compile it in Fedora 28. I attach the log giles. El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió: > > The "master" git branch has been updated to Sage-8.1. 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 > > There was no change over 8.2.rc4 > -- 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] Release process
2018-05-07 17:08 GMT+02:00 Erik Bray: > > On Mon, May 7, 2018 at 4:55 PM, Jeroen Demeyer: > > (starting a new thread for the discussion about the current very slow pace > > of merging tickets) > > > > On 2018-05-07 16:28, Erik Bray wrote: > >> > >> If it's not clear, shall I write up some more formal documentation for > >> my proposed process? > > > > > > To be honest, I think it's not very meaningful to do that without consulting > > the release manager. I mean, you can write up all the documentation that you > > want; in the end, it's the release manager who decides what happens. > > Sure, that goes without saying. That doesn't mean it isn't a good > idea to document an idea more carefully for the review of all those > involved. Such documentation would only be an initial draft. > Unfortunately Sage development does not have a PEP-like process in any > formal sense either. Maybe it should. There once was a list of Sage enhancement proposals or "SEP"s https://wiki.sagemath.org/devel/SEP Most of the pages it links to have been archived, you need to append ?action=info to their urls to get the history of each and see what they were about. 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] Release process
On Mon, May 7, 2018 at 4:55 PM, Jeroen Demeyer wrote: > (starting a new thread for the discussion about the current very slow pace > of merging tickets) > > On 2018-05-07 16:28, Erik Bray wrote: >> >> If it's not clear, shall I write up some more formal documentation for >> my proposed process? > > > To be honest, I think it's not very meaningful to do that without consulting > the release manager. I mean, you can write up all the documentation that you > want; in the end, it's the release manager who decides what happens. Sure, that goes without saying. That doesn't mean it isn't a good idea to document an idea more carefully for the review of all those involved. Such documentation would only be an initial draft. Unfortunately Sage development does not have a PEP-like process in any formal sense either. Maybe it should. -- 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] Release process
(starting a new thread for the discussion about the current very slow pace of merging tickets) On 2018-05-07 16:28, Erik Bray wrote: If it's not clear, shall I write up some more formal documentation for my proposed process? To be honest, I think it's not very meaningful to do that without consulting the release manager. I mean, you can write up all the documentation that you want; in the end, it's the release manager who decides what happens. I do agree that there is a problem though. We are close to 200 positively reviewed tickets just sitting there. And my fear of conflicts is certainly holding me back to do further Sage development for the moment (luckily, I had PEP 575 and the Cernay workshop to keep myself busy). So Volker, what's your opinion on this? -- 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 released
You could try setting the environment variable SAGE_INSTALL_GCC=yes to force Sage to build its own version of gcc. On Monday, May 7, 2018 at 6:56:53 AM UTC-7, Enrique Artal wrote: > > I have tried, but there are too many dependences. I will wait for > binaries. I tried to compile on two computers; In one of them python3 was > compiled but python2 failed on both. thanks for the tip, anyway. > > El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió: >> >> You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known >> to Python people this this does not work... >> Can you install gcc-7 and make it the default compiler? >> >> On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote: >>> >>> I was unable to compile it in Fedora 28. I attach the log giles. >>> >>> El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió: The "master" git branch has been updated to Sage-8.1. 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 There was no change over 8.2.rc4 >>> -- 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, 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.
[sage-release] Re: Sage 8.2 released
I have tried, but there are too many dependences. I will wait for binaries. I tried to compile on two computers; In one of them python3 was compiled but python2 failed on both. thanks for the tip, anyway. El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió: > > You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known > to Python people this this does not work... > Can you install gcc-7 and make it the default compiler? > > On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote: >> >> I was unable to compile it in Fedora 28. I attach the log giles. >> >> El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió: >>> >>> The "master" git branch has been updated to Sage-8.1. 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 >>> >>> There was no change over 8.2.rc4 >>> >> -- 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 released
You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known to Python people this this does not work... Can you install gcc-7 and make it the default compiler? On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote: > > I was unable to compile it in Fedora 28. I attach the log giles. > > El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió: >> >> The "master" git branch has been updated to Sage-8.1. 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 >> >> There was no change over 8.2.rc4 >> > -- 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.
