Mercurial > pidgin

comparison README.SVN @ 20400:ea9a5566a156

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
propagate from branch 'im.pidgin.rlaager.merging.msnp13-and-sf-1621854-4' (head 36b8a3e05397b5918f311a046fa580c5bb8846e0) to branch 'im.pidgin.cpw.khc.msnp14' (head 39ac2e1b7754245b292605b0e3055ebb1b954c5d)
author Richard Laager <rlaager@wiktel.com>
date Sun, 15 Apr 2007 05:00:56 +0000
parents 361c15e0b320
children
comparison
equal deleted inserted replaced
20395:bb940f08c820 20400:ea9a5566a156
1 If you plan to use gaim SVN, PLEASE read this message in its entirety! 1 If you plan to use Pidgin, Finch & libpurple mtn, PLEASE read this message in its entirety!
2 2
3 Gaim is a fast-moving project with a somewhat regular release schedule. 3 Pidgin, Finch & libpurple is a fast-moving project with a somewhat regular
4 Due to the rate of gaim development, SVN undergoes frequent bursts of 4 release schedule. Due to the rate of Pidgin, Finch & libpurple development,
5 massive changes, often leaving behind brokenness and partial 5 mtn undergoes frequent bursts of massive changes, often leaving behind
6 functionality while the responsible developers rewrite some portion of 6 brokenness and partial functionality while the responsible developers rewrite
7 code or seek to add new features. 7 some portion of code or seek to add new features.
8 8
9 What this all boils down to is that SVN _WILL_ sometimes be broken. 9 What this all boils down to is that mtn _WILL_ sometimes be broken.
10 Because of this, we ask that users who are not interested in 10 Because of this, we ask that users who are not interested in
11 personally tracking down bugs and fixing them (without a lot of 11 personally tracking down bugs and fixing them (without a lot of
12 assistance from the developers!) avoid SVN and use releases. Since 12 assistance from the developers!) avoid mtn and use releases. Since
13 releases will be made often, this should not prevent anyone from using 13 releases will be made often, this should not prevent anyone from using
14 the newest, shiniest features -- but it will prevent users from having 14 the newest, shiniest features -- but it will prevent users from having
15 to deal with ugly development bugs that we already know about but 15 to deal with ugly development bugs that we already know about but
16 haven't gotten around to fixing. 16 haven't gotten around to fixing.
17 17
18 If you are interested in hacking on gaim, please read README and 18 If you are interested in hacking on Pidgin, Finch & libpurple, please read
19 HACKING, and take note of the issues in PROGRAMMING_NOTES. (Note that 19 README and HACKING, and take note of the issues in PROGRAMMING_NOTES. (Note
20 they may be somewhat out of date at times.) Win32 developers, please 20 that they may be somewhat out of date at times.) Win32 developers, please
21 read README.mingw. 21 read README.mingw.
22 22
23 By far the best documentation, however, is the documented code. Not 23 By far the best documentation, however, is the documented code. Not
24 all parts of gaim have yet been documented, but the major subsystems 24 all parts of Pidgin, Finch & libpurple have yet been documented, but the major
25 are falling fast. If you have doxygen, you can use the Doxyfile in 25 subsystems are falling fast. If you have doxygen, you can use the Doxyfile in
26 the toplevel directory to generate pretty documentation. Otherwise 26 the toplevel directory to generate pretty documentation. Otherwise
27 (or even if you do!), the header files for each subsystem contain 27 (or even if you do!), the header files for each subsystem contain
28 documentation for the functions they contain. For instance, 28 documentation for the functions they contain. For instance,
29 conversation.h contains documentation for the entire 29 conversation.h contains documentation for the entire purple_conversation_*
30 gaim_conversation_* API, and account.h contains documentation for the 30 API, and account.h contains documentation for the purple_account_* API.
31 gaim_account_* API.
32 31
33 If you have questions, please feel free to contact the gaim developers 32 If you have questions, please feel free to contact the Pidgin, Finch &
34 by email at gaim-devel@lists.sourceforge.net, on IRC at 33 libpurple developers by email at devel@pidgin.im or on IRC at irc.freenode.net
35 irc.freenode.net in #gaim, or via the sourceforge forums at 34 in #pidgin. Please do as much homework as you can before contacting us; the
36 http://www.sourceforge.net/projects/gaim. Please do as much homework 35 more you know about your question, the faster and more effectively we can help
37 as you can before contacting us; the more you know about your 36 you!
38 question, the faster and more effectively we can help you!
39 37
40 Send patches to gaim-devel@lists.sourceforge.net or post them in the 38 Send patches to Pidgin, Finch & libpurple mailing list, devel@pidgin.im, or
41 Sourceforge forums at http://www.sourceforge.net/projects/gaim. 39 post them in the tracker at http://developer.pidgin.im.