[FLOW3-general] SVN checkout trunk => report errors as issues?

[Rik]

Hi,

today I thought I might tryout the the flow3 framework, and in development 
as it is, I decided it would probably save me a lot of trouble updating by 
exporting from https://svn.typo3.org/FLOW3/Distributions/Base/trunk/ and use 
that as the base, periodically updating it.

I certainly expected some errors there, and indeed, the very first tutorial  
/ kickstarter fails because the following constants are not defined:

\F3\FLOW3\Package\Package::DIRECTORY_TESTS_UNIT
\F3\FLOW3\Package\Package::DIRECTORY_TESTS_INTEGRATION
\F3\FLOW3\Package\Package::DIRECTORY_TESTS_SYSTEM

Easily fixed locally of course, the question is, should I:
a) treat it as work in progress, just write the local fix, and solve the 
inevitable clash on update when the constants will be defined, and use 
http://forge.typo3.org/projects/package-flow3/issues only to report issues 
from the latest download from http://flow3.typo3.org/download/?

b) treat it as current bug in the system, and report it as an issue on 
http://forge.typo3.org/projects/package-flow3/issues?

Regards,
-- 
Rik