There has been a lot of active discussion in IRC over the last week or two on some of the tools and processes we would like to implement to improve our QA and testing processes.
I'd like to have a conversation in email to capture some of those thoughts, and lay out a plan (that we can also document in JIRA for next steps) to work on this. We have a skeleton page on the wiki for the QA team here: https://wiki.foresightlinux.org/display/teams/Quality+Assurance QA team members should be running the fl:2-qa branch for testing, not fl:2-devel I don't remember all of the conversations we've had, but some things off the top of my head (and I don't have a lot of answers, so please add your thoughts and comments): * Better workflows in JIRA (gxti may be able to help after completing the caching appliance and mirror for doniphon) * RyanK has worked on a web application (I need more details on what this is, what it does, and the benefits) * Define a process for testing packages vs. underlying OS (such as new kernels, video card drivers, splashy, etc) * Define a process for testing packages in contrib repos (such as Zinden's or etanks) and when it is feasible to promote them to fl:2-devel / fl:2-qa * Define a process for testing new ISOs for all editions and documenting feedback * Use cases - when do we want to apply use case testing? * How / when does all of the above lead to promoting packages from 2-qa to fl:2? If possible, I'd like to gain comments and feedback over the next week, and have a follow-up conversation in our Focus meeting next Friday. Thanks. Paul _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
