Honza, I think you posted this in the wrong discussion group. Anyway, here are my comments.
I have spent time today testing some of the extensions we have listed: >> >> https://docs.google.com/spreadsheet/ccc?key=0ArzNE_OHjXkQdFMySmRxV2xOYjNJTDBZU1BQSk9aS3c#gid=0 >> >> Testing with Firebug 1.12 beta 3 >> >> Specifically: >> >> - ConsoleExport, also blogging: http://bit.ly/14die5r >> >> - Firebug Paint Events (I wouldn't recommend to use) >> >> - FireRainbow, >> >> - FireQuery (one exception found, pull request sent) >> >> - FireLogger (fixed the Persist feature, pull request sent) >> >> I'll also want to blog more about extensions working OK with Firebug 1.12 >> > great work > Agree. Really good job! One question regarding your blog post for ConsoleExport: Since when do we use the github issue tracker for our extensions? E.g. for ConsoleExport there are still two inside the Google Code issue tracker<http://code.google.com/p/fbug/issues/list?can=2&q=label%3Aconsoleexport>. We should discuss what to do with extension issues in the next conf call. > I added two columns in the Spreadsheet. >> >> 1) Status: I am using "OK" when I test the extension and I think it's >> compatible. We could also use something shorter than "I wouldn't recommend >> to use." >> > what do you think about "deprecated" > 2) Notes: Just some notes about the testing, explanation of the decision, >> links, etc. >> >> I dropped them at the beginning just after "Name", since especially >> "Status" is what we want to see eventually. >> > There were already two columns at the end of the spread sheet named "1.12" and "Hint" I originally used for that. Should they be merged? It would be great if everyone tests at least one extension from the list >> till the end of the week :-) >> >> Do you think I should mention the results in the release blog post? >> > yes. > If they are positive, definitely. I'm sure many (most?) Firebug users don't know there are extensions for it. > Perhaps we could encourage extension developers to participate? >> > would be great, perhapse also encourage extension developers to make their > extension compatible (for thus who aren't) > Of course. I assume sometimes it just needs a little change to make the compatible again. Sebastian -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/f202affd-70ff-430b-8c24-7986ac6f6566%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
