5 Mar
2014
5 Mar
'14
11:52 a.m.
On Wed, Mar 5, 2014 at 11:25 AM, Diego Lont <diego.lont(a)delware.nl> wrote:
Please check on regular basis if you can still run
Pier and if it looks good. This is the second time you broke Pier and I do not want to
debug your code.
With other words: use an image that has Pier and all add ons loaded when you do your
re-factorings!
I can imagine this is frustrating for you. But, I'm not a stupid
random clicker. How can I make sure I'm not breaking anything by just
randomly clicking here and there? I trust tests. I can see multiple
options, please comment:
- someone interested in Pier increases test coverage of the parts he
cares about (this can be web-based tests with something like Selenium
as well as unit tests). I will subscribe to any additional CI job that
gets created to get informed when I break something and I will fix it
if I can.
- someone interested in Pier changes the Pier configuration to use a
fixed version of Pillar and not the latest one. Then, when this guy
wants the latest Pillar features and fixes, he can change the
dependency version and fix Pier (this is the standard process for all
developments that depend on an external library). In this case I will
help this guy use the latest Pillar.
- as a last resort, someone interested in Pier could setup an
automatic deployment of a full pier-based website (on seasidehosting
for example) where I could randomly click from time to time.
Any other idea?
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill