You leave behind a portion of the 10.6 base that is on 32 bit. If you go 10.7 only it's 64 bit only of course, but since 1.5 is 10.6+ then you will be dropping some people who use 64 bit.
And then you have to explain that to them. "Adium supports 10.6. But if you have 32 bit intel on 10.6, that's not supported". At that point you might as well just drop 10.6, it's easier to explain and gives you bigger payoffs for dropping a section of the user base (yay new api's). At least that's my thought on it. Chris On Tue, Jul 26, 2011 at 6:00 PM, Adrian Godoroja <robot...@me.com> wrote: > Ok, > > what are the downsides of moving now? > > Adrian. > > On Jul 27, 2011, at 01:55 , Stephen Holt wrote: > > > Disagreed for 1.5. > > > > This brings us no benefit for 1.5's current codebase which I'd prefer we > start shaping up for release. > > > > Suggest postponing this for 1.6 > > > > -- > > Steve > > > > Typed with thumbs > > > > On Jul 26, 2011, at 3:49 PM, Adrian Godoroja <robot...@me.com> wrote: > > > >> Hi, > >> > >> as we all know, some time ago we agreed that 1.5 will be 10.6+ only. > >> > >> We wanted to let everybody know, that 1.5hg is moving to 64 bit only > builds, of course if most of us agree with this. > >> > >> Thanks, > >> Adrian. > >> > > > > >
