From: Sam H. <sh...@ma...> - 2007-05-13 17:32:12
|
on 05/13/2007 11:48 AM Davide P. Cervone said the following: > This is really for Sam, I guess, but I thought we should all know the > answer: what branch of the CVS tree should we be using for > development work these days? I've been putting jsMath changes in > HEAD, and letting Sam deal with backports to wherever they are > supposed to really go, but I'm not sure of that is the way it is > supposed to work. That's how it's supposed to work. You can give me a hint in the CVS commit message if you think something should be backported, otherwise I'll use my own judgment or ask you. > Last summer (if I remember right) we had a development branch and a > stable branch, and there was a fairly complicated means of updating > these, but after the release of 2.3.1 (I think) that seemed to go > away. Sam, can up refresh us on the protocol for making changes? I > have some fairly substantial updates that I want to make to the > MathObjects internals, and I'd like to do it in the safest way > possible. These should not change the author or end-user experience, > but the internals will undergo some adjustments that may take some > shaking down. I'm hoping to streamline a few things in preparation > for the conference this summer, and make some changes based on a > better understanding of things now that MathObjects have been around > for a while. HEAD is for bleeding-edge development -- perfect for large architectural changes or disruptive user-visible changes. rel-2-3-dev is the 2.3.x development branch, which should only get bug fixes and small feature non-disruptive enhancements. Pretty soon I'm going to create rel-2-4-dev from the current HEAD. I think that should probably happen before you start with the MathObjects work. No need to wait on that though if you want to get started, I can branch off of some arbitrary point, before you started with that. Then we can merge the MathObjects changes back in after things have calmed down. -sam |