It's been proposed that we setup another list that just contains the 'updates-testing' reports for folks who are interested in testing updates, but don't want to see all the rawhide/branched discussion.
I suppose we could also expand it to have all testing/qa related non branched/rawhide discussion?
We could also send them here of course...
Any thoughts on this idea?
kevin
On Wed, 2011-09-28 at 12:13 -0600, Kevin Fenzi wrote:
It's been proposed that we setup another list that just contains the 'updates-testing' reports for folks who are interested in testing updates, but don't want to see all the rawhide/branched discussion.
I suppose we could also expand it to have all testing/qa related non branched/rawhide discussion?
Why not to just the test/beta list where it would be used during testing, meaning this list?
I have a filter that sends that email to my "info" folder so doesn't bother me at all.
On 09/28/2011 03:48 PM, Mike Chambers wrote:
On Wed, 2011-09-28 at 12:13 -0600, Kevin Fenzi wrote:
It's been proposed that we setup another list that just contains the 'updates-testing' reports for folks who are interested in testing updates, but don't want to see all the rawhide/branched discussion.
<snip>
I have a filter that sends that email to my "info" folder so doesn't bother me at all.
I use a filter also...they go to their own folder.
Kevin Fenzi wrote:
It's been proposed that we setup another list that just contains the 'updates-testing' reports for folks who are interested in testing updates, but don't want to see all the rawhide/branched discussion.
I suppose we could also expand it to have all testing/qa related non branched/rawhide discussion?
We could also send them here of course...
Any thoughts on this idea?
What? Because there's so much traffic on this list? /sarcasm
The idea sucks. IMHO.
On Wed, Sep 28, 2011 at 12:13:03 -0600, Kevin Fenzi kevin@scrye.com wrote:
It's been proposed that we setup another list that just contains the 'updates-testing' reports for folks who are interested in testing updates, but don't want to see all the rawhide/branched discussion.
I suppose we could also expand it to have all testing/qa related non branched/rawhide discussion?
We could also send them here of course...
Any thoughts on this idea?
Would an automatically generated web page make more sense? I don't think the old data has much value, so I would expect that going to a web page to get the latest info when you want it makes more sense then getting email messages continuously.
Bruno Wolff III wrote:
Would an automatically generated web page make more sense? I don't think the old data has much value, so I would expect that going to a web page to get the latest info when you want it makes more sense then getting email messages continuously.
You mean like this?
--Fedora 15 pending updates website: https://admin.fedoraproject.org/updates/F15/pending?_csrf_token=d681c079014f...
rss feed: https://admin.fedoraproject.org/updates/rss/rss2.0?release=F15&status=pe...
There's enough existing infrastructure to help testers get their job done. I don't see a need to touch the updates-testing e-mails.
On Wed, Sep 28, 2011 at 15:11:10 -0500, Michael Cronenworth mike@cchtml.com wrote:
Bruno Wolff III wrote:
Would an automatically generated web page make more sense? I don't think the old data has much value, so I would expect that going to a web page to get the latest info when you want it makes more sense then getting email messages continuously.
You mean like this?
Not really. There are messages that limit the updates to those that still need testing and are grouped by crit path and security as well.
While you could start with the general updates page it's useful to have something help prioritize targets for proventesters with limited time.
Bruno Wolff III on 09/28/2011 04:20 PM wrote:
Not really. There are messages that limit the updates to those that still need testing and are grouped by crit path and security as well.
While you could start with the general updates page it's useful to have something help prioritize targets for proventesters with limited time.
Sounds like Luke could add a filter to that page for critpath and a sort for number of karma.
No need to create a whole new mailing list.
On Wed, Sep 28, 2011 at 16:29:19 -0500, Michael Cronenworth mike@cchtml.com wrote:
Bruno Wolff III on 09/28/2011 04:20 PM wrote:
Not really. There are messages that limit the updates to those that still need testing and are grouped by crit path and security as well.
While you could start with the general updates page it's useful to have something help prioritize targets for proventesters with limited time.
Sounds like Luke could add a filter to that page for critpath and a sort for number of karma.
No need to create a whole new mailing list.
I don't like the mailing list idea myself.
On Wed, 28 Sep 2011 16:35:39 -0500 Bruno Wolff III bruno@wolff.to wrote:
On Wed, Sep 28, 2011 at 16:29:19 -0500, Michael Cronenworth mike@cchtml.com wrote:
Bruno Wolff III on 09/28/2011 04:20 PM wrote:
Not really. There are messages that limit the updates to those that still need testing and are grouped by crit path and security as well.
While you could start with the general updates page it's useful to have something help prioritize targets for proventesters with limited time.
Sounds like Luke could add a filter to that page for critpath and a sort for number of karma.
No need to create a whole new mailing list.
I don't like the mailing list idea myself.
Yeah, I was just floating the idea because several folks seemed to like it at the proventesters meetup.
Perhaps we could look at gathering all the resources in some easy single shopping place? a wiki page?
kevin
On Wed, 28 Sep 2011 16:20:12 -0500 Bruno Wolff III bruno@wolff.to wrote:
On Wed, Sep 28, 2011 at 15:11:10 -0500, Michael Cronenworth mike@cchtml.com wrote:
Bruno Wolff III wrote:
Would an automatically generated web page make more sense? I don't think the old data has much value, so I would expect that going to a web page to get the latest info when you want it makes more sense then getting email messages continuously.
You mean like this?
Not really. There are messages that limit the updates to those that still need testing and are grouped by crit path and security as well.
While you could start with the general updates page it's useful to have something help prioritize targets for proventesters with limited time.
I think that there are things planned for bodhi, but for now I'm generating a list of critpath packages in updates-testing sorted by time spent in testing.
http://tflink.fedorapeople.org/testing_stats/
Once beta is released, I'm planning to go back and make those easier to read and prettier.
If anyone has suggestions on how to make that data more useful or other stats that would help, we can make changes.
Tim
On Wednesday, September 28, 2011, 9:23:52 PM, Tim wrote:
I think that there are things planned for bodhi, but for now I'm generating a list of critpath packages in updates-testing sorted by time spent in testing.
Once beta is released, I'm planning to go back and make those easier to read and prettier.
If anyone has suggestions on how to make that data more useful or other stats that would help, we can make changes.
Tim
Tim,
I made a very similar suggestion two weeks ago (using what to me seems to be a tad easier to read layout) in https://fedorahosted.org/bodhi/ticket/639.
I suggested 3 columns for the days value, so the URLs line up nicely like they do in the current report. That seemed to be a practical limit.
Al
-
Al Dunsmuir -
Bruno Wolff III -
Clyde E. Kunkel -
Kevin Fenzi -
Michael Cronenworth -
Mike Chambers -
Tim Flink