Hi Skip, Skip Collins <skip.coll...@gmail.com> writes:
> Designating something as an expected failure seems to be a good way to > track minor issues that need eventually to be resolved. As a user, I > frequently update with make up2 just to avoid getting bitten by stupid > errors that might sneak into master. Is it really that much extra work > for a developer to run the same command before committing and either > fix the error or mark it as a known failure? I'm for a relaxed policy here. Users living on the master branch know they are testing an unstable version of Org, and such hiccups just happen. -- Bastien
