On Friday, 5 September 2014 12:38:00 UTC+8, John Little wrote: > Don't you mean Continuous Integration? > My thoughts... > vim is built on so many platforms, in a variety of configurations, that full > CI of vim would have to be distributed, using volunteered resources; I > imagine that would be difficult to organize. > I imagine we'd need a lot more tests, including platform specific rendering > tests. > As it is, there are many who build vim on their own environments who pull > frequently, and report problems to this list promptly. > Regards, John Little
Yep, I assume that, the built issue is the easiest bug can be found. Building stuff can be finished by CI. The CI， not the "Tradition CI" (Tradition CI means: commit code -> trigger CI [Compile -> Unit Test -> Deploy -> ...]). The tradition CI CANNOT avoid the issue-code be committed into the repository. The CI what I mean is, when someone commit the code -> CI system is triggered -> If the job is failed -> the code will NOT be committed into the repository. Actually, the code was committed into a TEMP-REPOSITORY for triggered the CI system, if there something wrong with the code, this commit will not be merged into the real-repository. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
