On Wednesday, July 25, 2012 at 4:24 PM, Robert Vehse wrote: > > Am 25.07.2012 um 21:59 schrieb Thijs Alkemade: > > > > > On 25 jul. 2012, at 17:41, Thijs Alkemade <thijsalkem...@gmail.com > > (mailto:thijsalkem...@gmail.com)> wrote: > > > > > <snip> > > > As far as I know, the rule has always been supporting the current and > > > previous version. Adium 1.5.x has supported 10.6.8 and up, and I propose > > > to leave that this way. I think 1.5.x has been a pretty stable release, > > > and with (*fingers crossed*) most of the transcript viewer related > > > crashes and bugs fixed, I don't think it'll need much extra work. > > > > > > > > > > http://trac.adium.im/wiki/SupportedOSPolicy has been more a rule of thumb > than a strict rule. Now that Apple is targeting a yearly update cycle we > might want to reconsider it. > > > > From my recent commit on (http://hg.adium.im/adium/rev/a8fef30df88b), > > > default will require 10.7 to build. This gives us two options for 1.6: > > > branch from just before this, let it stabilize for a while and then > > > release, with only the new preferences as a new major feature. Or make > > > 1.6 require 10.7+, add some more new features with the shiny new APIs, > > > and then release. > > > > > > My preference would be the second. If we update the UI that much, it > > > would be a lot nicer if we could use the new localization features of > > > Lion. I also don't think it would work very well having to test on 3 > > > different OS versions. > > > > > > But I just know some people are going to disagree with me. :) Our Sparkle > > > stats suggest the number of Lion users surpassed our number of SL users > > > only a couple of weeks ago while it has been out for more than a year. > > > > > > So, thoughts? > > I'm torn. > > The new localisation features of Lion really are a major plus from what I > have been told. What other "shiny new APIs" do you have in mind that Adium > can benefit from? > > On the other hand, the Sparkle statistics also suggest that more than 50% of > our current user base is using a version of OS X older than 10.7 (36% on > 10.6) which would miss out on 1.6. > > I guess our decision should be based on the scoping of 1.6. In my mind a > release of 1.6 consisting of the new preferences layout and updated graphics > for retina display support would make it a good one and it doesn't look to me > like it needs a whole lot of more work to get it ready for prime time. What > do others think? > > >
Looking at what's been done so far and where commit activity has been present, I think that the preferences and graphics updates currently done-to-in-progress would be a reasonable place to draw the line. Given that those are already not depending on 10.7+ APIs, if possible, let's clean up and release 1.6 sooner than later with 10.6 support. Very few of the tickets on the 1.6 milestone (http://trac.adium.im/query?status=assigned&status=new&group=severity&milestone=Adium+1.6) are focused on that scope, which I think is a reasonable one. If we can clearly layout - Paul, Thijs, Frank, could you put your thoughts down either in the milestone on in email - what still needs to be done, I be we'd find a release opportunity that would be satisfyingly solid. All that said, if there are reasons that this work shouldn't be wrapped up and released soon, I think that what really matters is what'll have us all excited to work on new features, regardless of whether we cut off some potential users. -Evan
