sounds like we are in a less is more stage we always have time for new nice surprises let the incomplete stuff for later keep the great work sebastian o/ On Nov 21, 2012, at 8:58 PM, Esteban Lorenzano wrote:
new class builder is NOT marked for inclusion, I'm sorry (even as a preview)
On Nov 21, 2012, at 11:56 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, Nov 21, 2012 at 11:47 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2012-11-21, at 19:41, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Nov 21, 2012, at 11:37 PM, Mariano Martinez Peck wrote:
+1 for including only NB and then just bug fixes. No new stuff. So...slots and new classbuilder will be for next release. Same for Opal I guess.
No Opal should be in previous as well as Athens. These projects should come back to light. Else this will never happen.
I think that the thing we did with filesystem in 1.4 was good - integrate the detached project - apply the refactorings during development
then in the next release - change tools to use the new infrastructure - remove old code
I think we did almost the same with Zinc, no?
What about NOT including new class builder nor Opal in 2.0 but as soon as we create the initial repo for 2.1 (or whatever), the first 2 things we do is to integrate them?
-- Mariano http://marianopeck.wordpress.com