My thanks to all of you for using, discussing, reporting and contributing to the ruby-libxml extension. As more people become involved and as the quantity of contributions and issues grows, it has become more difficult to keep track of what needs to be done. With this in mind, the following protocol is necessary for better execution:
Non-developer: 1. the libxml-devel mailing list is for support and discussion 2. Feature changes, bug reports, patches must be submitted to the tracker at http://rubyforge.org/tracker/?group_id=494 Developer: 1. The trunk must always be in working order. 2. Narrow scoped bug fixes may be applied directly to the trunk. 3. Each developer should use a self named branch (i.e. danj-devel) for making larger changes that may result in prolonged brokenness. The developer should track the trunk and merge as required. 4. Larger branch based changes should be packaged into Release Candidates using a change name and the SVN number for public evaluation. i.e. xpath-1234 or build-1234. 5. Successful RC evaluation should result in a merge back to the trunk, assignment of a release number, then publication. I hope this will make it easier to apply consistent and productive time slices for continuing work on the code base. If you find a problem with anything said here or something omitted, please discuss. Dan _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
