> > >> > 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 could keep the dev scripts for those who choose to want to have a "sealed" environment where they can do all Sage work from within Sage? -- 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.
