> If it's incorporated, then I also think it should be part of a branch > only and the package should come with huge warnings.
Actually, I don't think we need to branch just to add this feature. We can add it to the 2.0 HEAD. The branch I suggested was actually to allow you to start committing your code to a 2.2 [1] line. At this point, it would probably make sense to make 2.2 the main branch and move the 2.0 code to /branches as it marches towards release. [1] For those that are wondering what happened to 2.1, it's just that there's a convention in many open source projects that even numbers are "stable" releases, and uneven numbers are "unstable". Hence, 2.2 would be the next public release. While we were working on it, we could call it 2.1, but I don't think enough people in the Windows community are familiar enough with the convention to make it clear what's going on there. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
