I noticed a couple of the list contributors releasing patches
made against the latest CVS snapshot, and wondered if this is
a good idea?
Pros:
The code which is the base for the patch is the most error-free[1]
stock circle available.
Everyone can download the latest CVS snapshots.
Cons:
A CVS snapshot is a working document.[2]
Not everyone will be able to find the correct version based on a
10 digit version number. It's easier to find the official bpl21
release, and it won't change - ever. Next release will be bpl22,
period[3].
If you have a patch against a CVS snapshot, you may have problems
patching it against both the previous and the next official releases,
since some of the functions may be/have changed.
Welcor
[1] in theory, a CVS snapshot contains the fixes of the reported bugs
since last official release.
[2] in practical use, a CVS snapshot will contain untested and perhaps
half unfinished code changes (->in_room => IN_ROOM() migration
springs to mind as a long trek).
[3] Unless it'll be CircleMud3.1 bpl 1 :P
--
+---------------------------------------------------------------+
| FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
| Archives: http://post.queensu.ca/listserv/wwwarch/circle.html |
| Newbie List: http://groups.yahoo.com/group/circle-newbies/ |
+---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 06/25/03 PDT