For the QA side we could do a system like for the track hunt. We should try at least one to see if it helps. Maybe the day before a "Feature lock before release"
trac-hunted - fixed at patched trac-hunted-confirmed - where a second party confirms it before being sent to trac trac-hunted-irrelivent - and then close it trac-hunted-sendnext - and send to next release On Dec 16, 2007 3:49 AM, Jacob <[EMAIL PROTECTED]> wrote: > Matt wrote: > > On Dec 15, 2007 10:46 PM, spencerp <[EMAIL PROTECTED]> wrote: > > > > > >> Actually, what would be nice is, if you had a "developer super duper > >> pooper" version or something like that. I know Trunk is an unstable / > >> test version as such. But I mean to have a "developer super duper > >> pooper" version... Where you could just UNLOAD / COMMIT all those > >> tickets in one swoop. > >> > >> Then us crazy testers can grab a copy of THAT version as well. Report > >> back, what worked, what went wrong, submit fixes, commit those fixes, > >> report back again. Then whatever passes without fail, or whatever... > >> then decide if "those" get submitted to Trunk for the next soon-to-be > >> release of WordPress.. > >> > >> > > > > Instead of a bug hunt, we should have a "Trac hunt". Search Trac for > bugs > > marked for 2.4, check if they're still relevant, make a patch, and tag > it > > something like "trac-hunted", to let the commiters know that it's ready. > > Then, well, I'm sure you know the rest. ;) > > > > > > > > No. The point of "hunts" is to gain motivation for doing what should > already be done anyway. Going through some of the tickets from over 6 > months ago, you can pretty much find tickets that are no longer relevant > and if you can prove it, then close it. There isn't any point having > irrelevant tickets open when they can be closed as invalid. > > Also, with any open source project, people write patches for areas they > are concerned about. I'm more likely to write a patch for anything that > has to do with plugins than for security, because I'm more interested in > plugin API and I'm not very good at security. So I mean. There are a lot > of bugs I won't touch because they either bore me or I'm too scared or > they are beyond my current ability. > > I adopted 6 or 7 tickets recently and I plan on providing patches for > them. I would totally love to see them closed out. However, most of them > are *enhancements* which is to say that they don't fix anything. > However, still that is 6 or 7 tickets that hopefully won't be pushed to > release after release. > > Quality Assurance for open source is a bitch! However, I'm not really a > tester besides writing occasional unit tests, so I wouldn't really know > about some of the bugs. > > -- > > Jacob Santos > > http://www.santosj.name - blog > http://wordpress.svn.dragonu.net/unittest/ - unofficial WP unit test > suite. > > Also known as darkdragon and santosj on WP trac. > > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > -- -------------------------------- Charles E. Frees-Melvin [EMAIL PROTECTED] www.cefm.ca _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
