Hi Nathann, Karl,
On Fri, Mar 07, 2014 at 07:37:12AM -0800, kcrisman wrote:
> Again, note it says "deviate even more". Sage-combinat does release early
> and often, but not to the main Sage branch, if I understand it right,
> because it's often not ready (?).
Off topic, but since this was brought out :-)
Over the five years of its existence, the Sage-Combinat queue did
release a lot of stuff to the standard Sage library. Any volunteer for
doing some real stats? In the mean time, as a far fetched guess, I
would say a good 90% of what was developed there ended up in Sage. The
10% remaining is now either being worked on in the form of branches,
or rotting away waiting for someone to take it over, or not.
So long the queue, and thanks for the fish. It played its role to let
people collaborate together while we had a crappy Sage workflow. Now
it's much easier to informally form small teams to work on a project
by project basis. Also, as we grow up, people are progressively moving
out of the core and working on peripheral features, which means less
interactions and smaller teams.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--
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.
