On 10/12/2010 03:43 PM, Adam Williamson wrote:
> On Mon, 2010-10-11 at 14:17 -0400, James Laska wrote:
>
>>> Sometime this week, I'll put up a wiki page with a general list of
>>> known critpath packages. This will give us a working set to start on.
>>> I'm thinking we can use that list to let
On Mon, 2010-10-11 at 14:17 -0400, James Laska wrote:
> >Sometime this week, I'll put up a wiki page with a general list of
> > known critpath packages. This will give us a working set to start on.
> > I'm thinking we can use that list to let folks "sign up" to track down
> > the maintainer a
On Mon, 2010-10-11 at 12:56 -0500, John Watzke wrote:
> On Mon, Oct 11, 2010 at 11:26 AM, James Laska
> wrote:
> On Mon, 2010-10-11 at 10:58 -0500, John Watzke wrote:
> >Thanks Thomas. This will work great. Now we just need
> to figure
> > out how to drive thi
On Mon, Oct 11, 2010 at 11:26 AM, James Laska wrote:
> On Mon, 2010-10-11 at 10:58 -0500, John Watzke wrote:
> >Thanks Thomas. This will work great. Now we just need to figure
> > out how to drive this initiative.
>
> I think you just did! Best way to start, is by discussing and following
On Mon, 2010-10-11 at 10:58 -0500, John Watzke wrote:
>Thanks Thomas. This will work great. Now we just need to figure
> out how to drive this initiative.
I think you just did! Best way to start, is by discussing and following
up.
> Perhaps a wiki page to at least identify the packages a
On Sun, 2010-10-10 at 22:09 -0500, Bruno Wolff III wrote:
> On Sun, Oct 10, 2010 at 18:49:10 -0400,
> Timothy Davis wrote:
> > When a critical path sits for any more than four weeks I suggest the
> > maintainer include test files and test cases
> > to help any tester. Things such as scripts/prog
Thanks Thomas. This will work great. Now we just need to figure out how
to drive this initiative. Perhaps a wiki page to at least identify the
packages and if we've worked with the maintainers yet to get an agreement to
try to provide some sort of testing information. From there we'll need s
On Mon, 11 Oct 2010 09:30:57 -0500
John Watzke wrote:
>That's the unapproved critical path updates on Bodhi that I was
> talking about and it is just a small subset of critical path packages
> where the package needs testing. What I mean is a listing of all
> packages that would be considered
That's the unapproved critical path updates on Bodhi that I was talking
about and it is just a small subset of critical path packages where the
package needs testing. What I mean is a listing of all packages that would
be considered critical path when an update is pushed out for that package.
I
On Sun, 10 Oct 2010 22:54:11 -0500
John Watzke wrote:
>I'm relatively new to proventesters. I know I can see unapproved
> critpath packages on Bodhi but is there a master list of all critpath
> packages in Fedora? That would help us in tracking down who to work
> with in hopefully getting th
>
> Having automated tests or even test plans would be useful for any package.
> But critical path packages are perhaps more worth doing this for. Maybe
> QA can slowly work through the list working with the package owners
> to try to develop reasonable tests.
>
>
Yes, it would be great if criti
On Sun, Oct 10, 2010 at 18:49:10 -0400,
Timothy Davis wrote:
> When a critical path sits for any more than four weeks I suggest the
> maintainer include test files and test cases
> to help any tester. Things such as scripts/programs to test with, or
> scenarios like do this and check that.
For
When a critical path sits for any more than four weeks I suggest the
maintainer include test files and test cases
to help any tester. Things such as scripts/programs to test with, or
scenarios like do this and check that.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://a
13 matches
Mail list logo
