While writing more automated tests is clearly a reasonable thing to do, it is only one small part of the decision-making process for determining which core changes should be made and when they should be released. In addition to various formal testing paradigms (unit, regression, integration, platform, and performance/stress tests), other non-automated, decision-process issues also should be addressed.
I think that we are really dancing around some practical, as well as philosophical, differences of opinion related to the overarching question: "Why, when, and how should a given core change be made?" Of course, since we are talking about writing code, software engineering principles -- such as robustness, complexity, ease of implementation, architecture, and expansion capabilities -- are always relevant, both for core developers and plugin developers, alike. In many instances, a decision can made by a simple comparison of "costs" vs "benefits" which, while sometimes discussed at length, are more often glossed over when the benefits seem to be readily apparent, regardless of value; and the costs, while perhaps not obvious, seem to be minimal at worst. However, regardless of the elegance and technical correctness of any engineering principles that are applied, these engineering considerations should be, in my view, secondary to the needs and interests of the TiddlyWiki end-user/author community. This includes timely delivery of fixes for known bugs, as well as issues of reliability, ease/consistency of use, customization, performance, compatibility and, of course, providing specific feature enhancements to actually help them achieve their goals. thoughts? -e --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
