On Mar 17, 2010, at 8:04 AM, Markus Roberts wrote:
is edition contains more code and fails fewer tests then the
previous ones, thought it still fails over two hundred at the head.
Today I'm going to be working on fixing test failures (by fixing the
code or the test, as needed) and Jesse's finishing up the REST
conversions.
[...]
First, this output format is *awesome* - I can now see why it took so
long to build the testing branch. IMO, this totally validates the
approach of having the testing branch.
Second, it's pretty clear that a lot of the failures are my fault -
each of my three primary branches seems to cause 10+ new errors.
What's the best plan to work on these? Rebase them on current master
and just fix everything I can? Or should we make a new "testfix"
branch fixes most of the failures in master and only then start on our
other failures?
Lastly, the futures branch is obviously still throwing a heckuva lot
of failures. Is it actually functional yet? That is, does Puppet
actually work with it merged in and these are just broken tests, or
are they actually indicative of real problems?
--
A lot of people mistake a short memory for a clear conscience.
-- Doug Larson
---------------------------------------------------------------------
Luke Kanies -|- http://reductivelabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
