Do we have a testing framework in place for the jQuery enabled release? I'd like to suggest that all refactoring be accompanied with unit tests for the corresponding code. This will help catch possible bugs and lead to better code coverage which will be helpful in the long run, and I don't think the cost in terms of time or effort will be very high. The key is just getting a recipe/vertical in order for such unit testing, unless we already have one?
Saq On Mar 4, 8:20 pm, Saq Imtiaz <[email protected]> wrote: > On Mar 4, 4:21 pm, FND <[email protected]> wrote: > > > > I'd love to help with this in any way that I can. Let me know what I > > > can do > > > We're thinking of coordinating this primarily via Trac, perhaps > > supported by this thread and possibly IRC. > > For each file (e.g. TiddlyWiki.js, Story.js etc.) we create a ticket to > > which we can subsequently attach the respective patches. > > If further discussion is required on a particular issue, we can do that > > on Trac and/or here on [twdev]. > > Simultaneously Martin, Phil and I will keep the spreadhseet up to date. > > I think that sounds very good actually. Just enough structure to keep > things from getting chaotic but not so much that it would get in the > way. My one concern is to make sure avoid duplication and don't end up > having multiple people working on the same code. If the spreadsheet is > updated often enough it should be sufficient to just check it before > starting working on a particular function. > > Saq > > > > > Does this sound feasible? > > > -- F. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
