Hi!
> Why can't I expect SWSusp work better and more reliable from release to
> release?
Patches welcome. Or employ someone to do swsusp development for you.
> Some possible things that could help:
>
> *Addopt a no-regressions-allowed policy and everthing stops until any
> identified regressions (in performance, functionally or stability) is fixed
> or the changes are all rolled back. This works really well if in addition
> organized pre-flight testing is done before calling a new version number.
> You simply cannot rely on ad-hock regression testing and reporting. Its got
> too much latency.
This would also mean "no development at all".
> * assign validation folks that the developer need to appease before changes
> are allowed to be accepted into the tree.
So... get me someone to test swsusp in each -rc and -mm
release... that would help. If you can't provide the manpower, why are
you whining?
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |