[Adium-devl] (1.0b22 == 1.0rc1)

[Evan Schoenberg]

Zac wrote:
> I vote that the adium servers are going to buckle when 1.0 is  
> released.

I disagree - I think Trac is going to buckle, because it can barely  
handle day-to-day load, but hopefully that'll be better with the  
upgrade Chris is working on.  Whether the upgrade is a major  
improvement or not, I fully expect Trac to be problematic in the days  
following the release; there doesn't seem to be anything we can do  
about that besides deal.

adiumx.com (the website server) is on a solid, dedicated box on  
networkredux which has been upgraded to 2 gb of RAM and should be  
able to handle it - that box does nothing besides adiumx.com and  
adiumxtras.com, and Thomas has mentioned several times that someone's  
ultratight php code keeps resource usage down (Zac!).

Downloads are on the distributed cachefly network in which I have  
complete faith; we'll also upload it to the Sourceforge site so we  
have a place to fallback (in terms of redirecting where download.php  
goes) if the unthinkable thunks.

On Jan 9, 2007, at 5:20 PM, Colin Barrett wrote:

> On Jan 9, 2007, at 12:51 PM, Evan Schoenberg wrote:
>
>> Any objections to 1.0b22 being a silent release candidate plus debug
>> logging, followed by a 1.0b23 which will match but have debug
>> logging turned off (as the release does), with an actual release by
>> the end of next week?
>
> Are we ready to release, form an infrastructure standpoint?
I think so.  See above, with the addition that someone needs to  
update the screenshots, and we need to compile a final version  
history (and an abbreviated top-10 or top-15 for use on the version  
tracking sites).

> What about  any sort of hyping/advertising/marketing we want to do?
By the end of next week, I think we can brainstorm who and how to  
contact and do so.  Did you have anything in particular in mind?

> Is 0.89.2  still going to come out concurrently for 10.3 users?
10.2, you mean?  What does 0.89.2 offer? The only change committed to  
the adium-0.8 since [15719] (0.89.1's revision) is a fix for Google  
Mail checking.
	(for the record: I haven't heard a single support request from a  
10.2 user regarding the beta.  Are they that complacent not to say,  
"hey, adium won't launch on my machine but 0.89.1 works fine", that  
uninterested in betas [likely], or that nonexistent?)

> Also, we aren't logging groupchats, which imajes pointed out. This is
> a regression from 0.89. I left it out intentionally because the group
> chat API wasn't robust enough to match up with the file name and UI
> and XML stuff I was doing. I was intending to fix it, but I've gotten
> busy. I also kind of forgot about it....

> That might be something we want to fix before doing 1.0.

The filename doesn't use more data than it did before, as far as i  
can tell, except specifying the date/time with greater precision. Do  
you recall what specific problems you found?  In any case, yes, this  
should probably be fixed.  Can you take it on this week?  Unless I'm  
greatly misunderstanding, it really shouldn't be a huge departure  
from what's already being done...

> We also might want to set a release day (feb 1?) just to let some hype
> build up.
I guess I feel like being in beta since July 4, 2006, is enough  
buildup already and I want to see this through, get excited, and be  
able to get back to development being fun. I'm willing to be  
overridden if the overriding feeling is that announcing a date and  
doing something to build up to it isthe way to go... but I'd rather  
announce it perhaps to a couple of the big mac news sites with a  
request to wait until the day to run the press release and spring it  
on the world.

-Evan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070109/cdec7e52/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070109/cdec7e52/attachment.sig>