Mercurial > pidgin

comparison STATUS @ 2318:a7bfb5dfab25

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[gaim-migrate @ 2328] documentation updates. committer: Tailor Script <tailor@pidgin.im>
author Eric Warmenhoven <eric@warmenhoven.org>
date Thu, 20 Sep 2001 08:13:25 +0000
parents 922d8505ae5a
children 0e0a54e5819a
comparison
equal deleted inserted replaced
2317:ab8ca5d75dcd 2318:a7bfb5dfab25
1 STATUS of GAIM CVS tree. Last modified $Date: 2001-05-23 07:39:05 -0400 (Wed, 23 May 2001) $ by 1 STATUS of GAIM CVS tree. Last modified $Date: 2001-09-20 04:13:25 -0400 (Thu, 20 Sep 2001) $ by
2 $Author: warmenhoven $. 2 $Author: warmenhoven $.
3 3
4 This file is meant to provide gaim users who use the CVS version to see whether 4 This file is meant to provide gaim users who use the CVS version to see whether
5 they actually want to compile what they just checked out. Gaim CVS is usually 5 they actually want to compile what they just checked out. Gaim CVS is usually
6 relatively stable (we use it all the time), but has tendencies to be quirky at 6 relatively stable (we use it all the time), but has tendencies to be quirky at
7 times. 7 times.
8
9 There always seems to be some iffy-ness by a lot of people about whether to
10 use the CVS version or stick with a stable release. Use the CVS version. If
11 you need a version that you know is reliable, then keep your favorite one in
12 case of an emergency. But for the most part, gaim is not mission-critical
13 software, and if you can help us find a few bugs before we release, all the
14 better. (Also, CVS tends to be more stable than releases, since we get 10 or
15 12 bug reports right after we make a release, and all those bugs are fixed
16 within a day or two usually.)
8 17
9 Each protocol is hacked by both Rob and Eric, though there is one person that 18 Each protocol is hacked by both Rob and Eric, though there is one person that
10 kind of "owns" a protocol (mostly indicating that they were the person that 19 kind of "owns" a protocol (mostly indicating that they were the person that
11 originally wrote it). Their name will be next to the protocol; they're the 20 originally wrote it). Their name will be next to the protocol; they're the
12 people to complain to when something doesn't work ;). 21 people to complain to when something doesn't work ;).
13 22
14 23
15 OVERALL 24 OVERALL
16 ======= 25 =======
17 26
18 The current CVS tree is more or less back to "normal". It seems to be stable, 27 Everything right now is more or less peachy. I regularly use seven protocols
19 and allows multiple connections (which should also be stable). 28 at the same time and don't have any problems (all of them except Napster and
20 29 Zephyr). You shouldn't be using 0.10.3; there are serious bugs in it (including
21 There have been a lot of changes since 0.10.x; I think all of the bugs have 30 a remote exploit). Always use CVS, or if not, the most recent release.
22 been worked out but I'm sure there are still a lot remaining. Please, if you
23 get bored one day, go on a big bug hunt.
24
25 There always seems to be some iffy-ness by a lot of people about whether to
26 use the CVS version or stick with a stable release. Use the CVS version. If
27 you need a version that you know is reliable, then keep your favorite one in
28 case of an emergency. But for the most part, gaim is not mission-critical
29 software, and if you can help us find a few bugs before we release, all the
30 better. (Also, CVS tends to be more stable than releases, since we get 10 or
31 12 bug reports right after we make a release, and all those bugs are fixed
32 within a day or two usually.)
33 31
34 32
35 Buddy List 33 Buddy List
36 ========== 34 ==========
37 35
57 55
58 56
59 Perl 57 Perl
60 ==== 58 ====
61 59
62 Perl also got a good reworking, but also has a few more features now. Again, 60 Perl has its good side and bad side. It didn't completely survive the transition
63 porting from 0.10.x to 0.11.0 should be simple, but read the docs to see what's 61 to multiple connections, but it was never really intended for more than a chatbot
64 going on. 62 anyway, which should still work just wonderfully.
65 63
66 64
67 TOC (Rob) 65 TOC (Rob)
68 === 66 ===
69 67
102 implemented. Yahoo servers are flaky at best so if you're having problems it's 100 implemented. Yahoo servers are flaky at best so if you're having problems it's
103 probably not my fault. Make sure to watch the debug window if you're having any 101 probably not my fault. Make sure to watch the debug window if you're having any
104 problems. 102 problems.
105 103
106 104
107 IRC (Rob) 105 IRC (Eric)
108 === 106 ===
109 107
110 IRC currently supports signing on/off, sending and receiving messages, 108 IRC currently supports signing on/off, sending and receiving messages,
111 joining chat rooms and holding conversations within them. The buddylist 109 joining chat rooms and holding conversations within them. The buddylist
112 also works and users have the ability to send ping requests to the user 110 also works. Several /commands work as well, /help in any window will show
113 by right clicking their name. /me support is also added. Other commands 111 you a full list.
114 and functionality are planned but not yet implemented.
115 112
116 113
117 MSN (Rob) 114 MSN (Eric)
118 === 115 ===
119 116
120 MSN currently supports signing on/off, sending and receiving messages, adding 117 MSN currently supports signing on/off, sending and receiving messages, and going
121 and removing people to your permit/deny list and going away / idle. 118 away/idle. You can also change your friendly name.
122 119
123 120
124 ICQ (Eric) 121 ICQ (Eric)
125 === 122 ===
126 123