On Sun, Jan 11, 2015 at 3:00 AM, Simon King <simon.k...@uni-jena.de> wrote: > Hi! > > On 2015-01-11, Nils Bruin <nbr...@sfu.ca> wrote: >> On Sunday, January 11, 2015 at 12:54:56 AM UTC-8, Martin von Gagern wrote: >>> >>> On 11.01.2015 09:38, Robert Bradshaw wrote: >>> > Hopefully it's becoming stable enough that >>> > we should start shipping it as part of Sage? >>> >>> At first I thought so, too. But now I'm no longer sure: if you ship it >>> with Sage, then it will be difficult to use it if you want to work with >>> a patch from an older branch. >> >> >> So we should *ship* it with sage but not *use* it yet. In a year or so, >> git-trac will have been stable enough for long enough that most people can >> start using the version shipped with sage, because any branch they meet >> will have about the same git-trac. > > Or: We should ship it with Sage, but it should live in a repository that > is independent of the rest of Sage. Hence, if one works on an old branch > of Sage, git-trac would still be available.
Yes, I meant that it should be an spkg. You can install it in old sage's, you can have a different version, but at least you get some version by default. -- 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 email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
