Re: webapp testing (was Re: pcp updates: python fix, build, qa, and docs tweaks (+lberk+mgoodwin+minnus merges))

["Frank Ch. Eigler" <fche@xxxxxxxxxx>]

Hi -


> If the level of testing on upstream Vector releases is concerning you
> (bear in mind there are many browsers that will be rendering Vector,
> so its a hard problem) consider making a pre-release checklist. [...]

That is a good idea; assembled notes for all the webapps [1].

[1] https://sourceware.org/git/gitweb.cgi?p=pcpfans.git;a=blob;f=qa-notes.txt


> At this stage our best strategy is getting new code out in a more
> timely fashion, so that we increase the base of potential testers
> [...]

Perhaps, though newer is not necessarily better, and newer is not
necessarily going to be selected for a next pcp+webjs release anyway,
so end-user rawhide testing effort may be wasted.  I'm tempted to
expend qualification effort when specific interest is expressed,
and otherwise leave working things alone.

> Likewise for grafana/graphite.

In grafana's case specifically they've switched to a model that makes
a pure webapp deployment trickier than formerly.  [2]

[2] https://elastic.org/~fche/blog3/archive/2015/09/17/pcp-and-grafana-v2


- FChE