Changes between Version 6 and Version 7 of pm-svn-releases


Ignore:
Timestamp:
Sep 19, 2006 12:36:08 PM (15 years ago)
Author:
tkr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • pm-svn-releases

    v6 v7  
    2323
    2424 1. For casual users and those who do not want to be bothered with frequent updates or installing SVN, they should download the latest tarball (point release) in either source or binary form. To report bugs, they can use the three-digit release number of the tarball they downloaded. To get a new version containing a bug fix (or a capability they want that has been added), they will need to download a new tarball. Such users can expect the version they check out to be mature and mostly bug-free.
    25 
    2625 1. For power users who want to get updates and bug fixes as soon as they are committed, but want a stable API that will not change out from under them, they should use SVN to check out the latest stable release in {{{stable/*.*}}}. Such users would have to report bugs based on the SVN version number they are using (a little more of a pain for the developers), but can get the fixes using "svn update". Such users may experience a slightly bumpier ride, as there may occasionally be incorrect patches committed to {{{stable/}}} and other minor difficulties. Most of the time, however, this code should be mature and stable.
    27 
    2826 1. Developers and any really adventurous power users who want the bleeding edge can check out {{{trunk/}}}. This probably not to be encouraged for users and certainly the PM won't be expected to be too responsive to bug reports from people using the code in {{{trunk/}}}, since it is not intended to be bug-free.
    2927