March 24, 2013
7:55 p.m.
I guess I missed the point, but can't we just make the configuration do whatever the jenkins job does and declare it as the development version for 2.0?
We (as the Pharo community) will most probably have to do that, but it is not the right way or the best for the future.
Seaside has currently two main versions 3.0.x and 3.1 and targets many platforms, that is what Metacello is for, but it makes the config complex. Normally, the main Seaside developers should have to do this, it is their (communities') code.
Yes but we will probably have to do it because we could use Seaside as a nice regression tests for Pharo 30 apha. Stef