[#10330] - RFC - Remove testing data from distribution
- Closed
- 9 May 2016
- Medium
- Build: master
- # 10330
There really is no good reason to include the testing sample data in the released version of joomla - it only has a purpose and use during the staging lifecylcle
It is fairly trivial to add the testing sample data to the list of files excluded from a build if people agree.
I'd rather see the sample data (hell, joomla.sql too) rewritten to not be static SQL dumps. But hey, a guy can dream...
that would be even greater.
+1 (especially as it's been on our roadmap for a while now: https://developer.joomla.org/cms/roadmap.html)
Until someone actually does it words are great but don't change anything.
It's at least 6 months since PLT said someone said they were doing that. In
the meantime I can do this PR in ten minutes.
The PLT roadmap is only asking for the 10 minute PR. We can do the clever stuff another day. :-)
I guess I misread the minutes of the meeting in Germany.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-05-09 18:54:20 |
| Closed_By | ⇒ | zero-24 |
joomla-cms-bot
- 
Closing as we have a PR here #10364
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10330.
Set to "closed" on behalf of @zero-24 by The JTracker Application at issues.joomla.org/joomla-cms/10330
Actually, I did a PR once to make the sample data a postinstallation process using an admin module, a plugin per sample set and com_ajax (#7680). It was working with testing data, the others would still have to be done.
Reason it stopped was that with the upcoming webservice layer this would become simpler, which I agree to a degree.
i agree, also another suggestion. sample data should not create things that are already created by joomla.sql. ex: the component menu.