Michael Meeks-5 wrote
...
From the first days I worked on gnumeric, many of our best test
documents were sent to the developers, and maintained in a semi-private
collection that we used like our crash-testing suite for regression
testing...
If someone wants to start contributing, he'll begin to git clone LO repo so
he'll automatically retrieve all test documents (and that's what we want,
don't we?).
If we'd begin to put specific document in a kind of "semi-private" (which
can be accessed by some TBs/Jenkins and core dev/QA people only) repo, in
case a commit breaks something concerning a document from this repo, it'll
be more difficult to debug this for people who don't have access to this
repo.
Given the fact that it's not so often to see all TBs green or Jenkins review
OK, it'd be even more difficult to achieve this goal.
But above all, putting in place a system to manage private files is time
consuming + a cost (in terms of money this time). Accepting money for this
service wouldn't be a solution since it would remove TDF's independance.
Julien
--
View this message in context:
http://nabble.documentfoundation.org/Please-add-an-option-to-set-bug-reports-to-Private-tp4203277p4203378.html
Sent from the Dev mailing list archive at Nabble.com.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.