OB loads fine in 1.4 too, so... you don't need to use 1.3 even if you are attached to it :)
On Jun 12, 2012, at 5:27 AM, Yanni Chiu wrote: > On 11/06/12 10:35 PM, Cameron Sanders wrote: >> Do you need 1.4, and why? -- if you do not mind sharing. > > I was building on 1.3, and had a second automated build which tracked > 1.4. Periodically, I would manually update the 1.4 base image of the > build to the then latest 1.4. Each of the builds would load the > framework packages I needed, then load my code base. > > This way I could see problems with the frameworks or my code, as 1.4 > progressed. At some point 1.4 was stable enough that I switched over > (about 6 months ago). > >> ... I only recently abandoned my Pharo-1.2 one-click derived image >> when I had troubles connecting to a DB. I figured it was time to do a >> complete upgrade. But it has turned into a nightmare, and my project >> has hit a standstill, > > Yep, you don't want to be caught by surprise, when upgrading. > >> Pending your answers to my query about why you chose 1.4 over 1.3, I >> will start fresh again. > > In your situation, I would choose 1.4, because Seaside, Magritte2/3, DBXTalk > should work on 1.4 or will be fixed to work on 1.4 - which may not hold true > (i.e. the fixing) for 1.3. AFAIK, unless you're heavily attached to > Omnibrowser, then there is no reason to use 1.3. > >
