my proposal so far is: - prepare the vms as "NB ready" (I was planning to work on that next week, using the new infraestructure) - include NB as "ready to use" - include Opal as "preview"
No more integrations for 2.0. We will be able to load Athens (since VMs and image will be prepared) with just a simple Metacello configuration. I don't know if including it as "preview" (like opal) Igor, what do you think? I need all next week to prepare that (with Marcus assistance, of course :P)... Are we ok with that? Esteban ps: If we don't go to beta next week will be really difficult to release in February (as is stipulated now) On Nov 21, 2012, at 11:47 PM, Camillo Bruni <[email protected]> wrote: > > On 2012-11-21, at 19:41, Stéphane Ducasse <[email protected]> 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?
