VERY IMPORTANT!
This is not the same as trunk at rev892! Please treat it as a completely different product than trunk at revision 892. Technically, this is revision 1002, but that means nothing other than the fact that it represents a changeset to the 0.9.1 branch (not trunk) and just happens to be commit #1002 to our entire repository. Just don’t expect any features or bug fixes beyond rev892 in trunk (other than the security patches) to be in this (the reason why I marked it as rev 892). None of the new manager stuff is ready for release, so it is not included here.
I spent the last two days hand merging and patching all of this code from trunk on top of 0.9.1, selectively merging only what does work and I am confident in releasing. I did this because of the large amount of stuff that is not working in trunk (which I am very displeased with, but that’s another story), we keep adding more and more to get done before the next 0.9.x release, the fact that the current download is completely broken, and the fact that we had additional security patches that needed to be applied but that are completely dependent on check-in’s that lead nothing but broken code. So, this is the remedy to get a decent release out without everyone having to re-patch their installations again, with all the little hacks floating around the community. We’ve either got to learn to keep up with or respond to hacks that are published in this community by releasing more often or rejecting more hacks/approaches as risky to use if you plan on upgrading.
As you can imagine, besides being mentally exhausted, I will not let this happen again! Effective immediately, we will be enstating a formal development policy for two groups, Contributors and Committers. Contributors will be everyone but me for now. I will be the Committer, because I’d rather spend 30 mins merging and reviewing every contributor’s submission from their branch than spend another entire day and night straightening out a mess like this when we have to get a security release out the door! I can’t imagine what would happen if we already had public access to SVN announced and in widespread use with the state of the current trunk. The trunk should strive to be stable at all times.
So, that said, if you currently have commit priveleges to the trunk, and you are working on anything in the current trunk, and you plan on committing it to the trunk, please wrap it up as soon as possible (i.e. today or tomorrow), or move your work in progress to your branch. Everyone will be losing commit priveleges to the trunk until the new development process is completely defined and implemented. All contributions to the trunk must be committed to a personal or feature-specific branch, must be tested by the contributor against the latest trunk (i.e. you must get latest, merge your changesets into latest and test it thoroughly before submitting), and submitted to a Committer for merging with the trunk along with references to appropriate Flyspray Task # (i.e. no commits should be made without a request in the tracker).
More on these new policies as they are completely fleshed out and formalized. Let me know if you have any concerns, questions, suggestions for, or opposition to this for any reason. It’s just obvious to me that without a more formal approach to this, and some additional training on using SVN, we’re going to keep take two steps forward and one step back. I prefer to keep walking forward myself.
MODX Staff
MODX Staff
MODX Staff