Sounds reasonable to me. Somebody wants to come up with a template for the plugin feature list?
Concerning all the great work we've done recently (:)), it shouldn't be too hard to extract the information from the entries in changes.xml. Maybe this could be implemented as part of the changes plugin?
-Lukas Brett Porter wrote:
Hi, We discussed this briefly before. From looking at that, this seems to be the most workable solution: - for any new features added in m1 or m2, we add a description to the plugin site so that we have a comparitive checklist - for any bugs fixed in m1 that potentially impact m2, when fixed, clone the issue and move it to the other project, linking the original (this should only be a small % of issues as they usually relate to jelly-isms, etc) - this would include minor features (ie other options or configurations). Of course, the best solution where practical is to have them share the code (eg JXR). My main concern is that all the great work Lukas, Arnaud and Carlos have done recently would need to be duplicated later and hard to track. Does this sound ok? - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
