On Apr 24, 2010, at 6:14 AM, Robert Vehse wrote: > > Am 24.04.2010 um 07:59 schrieb Christopher Forsythe: > >> I'm sorry, I mistook the 11 tickets not to a severity of Major or Regression >> to mean that weren't as important as the 4 in those severities. If you think >> that keeping tickets which are "minor" in the milestone, I guess the meaning >> of the minor severity has changed in a way that I was not aware of. >> >> My apologies for any offense, none was meant. I was only pointing out that >> the easiest thing to do to to get a release out is to get a few things off >> the list which can wait for a later release. > > No worries. I think I overreacted. Some of the tickets are not marked as they > should be though. >
Easy guys. I just went through and shuffled a couple around and I'll continue to go through and look at some of the others this weekend as I get a chance. I also think that getting a quick 1.3.11 up is our most immediate priority. As I said, I would rather not have to but with protocols being completely broken and that being the current release (and last release for Tiger) we don't have much of a choice. I think we can probably get away with just the immediate fixes that the libpurple update will give us unless there's some huge other bug that someone really feels strongly enough about fixing to take the time to do so. If it's in any way possible, I'd love to see at least a 1.3.11b up by Monday (since I assume that none of us have Y! Japan accounts to verify) followed by a quick release once we know it works. After that, full speed ahead on 1.4. -Eric
