>-----Original Message----- >From: [email protected] >[mailto:[email protected]] On >Behalf Of ext Alan Alpert
>> Disadvantages: >> >> * People have to clone the whole repo for just a few examples. (People >> that compile Qt from source will have to live with this, if you use the >> SDK this should not impact these people) >> * If the API of a module >> changes and an example breaks it will not be caught by the CI system the >> moment the change is going into mainline. >> >> I am wondering if any of you has opinions about this? > >This sounds to me like it's missing a key point of our examples. They aren't >just there for documentation, they're also very useful for validation and >testing. The examples for a feature are currently one of the few ways we >have >for the implementer and maintainer of that feature to have it running, on its >own, somewhere in the Qt code base. They need to be written by the >maintainers >because they need to show the way it's meant to be used. And they need to >be >maintained by the feature maintainers because if the usage pattern evolves >that's an important consideration for the API. > >When they're used like that, then the people who work on those examples >already have that repo - and not some generic repo - cloned. The changes to >the example will likely follow directly from API changes leading to the >aforementioned CI problems. On top of that you won't be sole maintainer of >it, >which makes some of the advantages less necessary. Just to put more weight behind Alan's argument. I fully agree with his statement. The disadvantages are far more significant than the benefits. I would go as far as saying that the main purpose of the example is quick testing and the doc aspect is just sugar on top. Let's not make the current repo split situation worse than it is already. -- Alex _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
