Fix a tiny typo

[holsety]

This is a little typo when I try to copy them from the summary doc, it would be very straight forward :)

Pull Request Checklist

• This pull request is submitted against the development branch.
• Inline documentation has been updated.
• README.md or another dedicated guide has been updated.
• Changes are tested.

[MartinP7r]

Thank you @holsety ! That is indeed very straightforward. 🙂

[groue]

Thanks to both of you :-)

[MartinP7r]

Sure thing. I hope it's ok to just go ahead for typos etc. as long as I'm minding the checklist.

BTW, @groue , I figured I don't need to worry about Travis failing as long as the project's tests are working?

[groue]

I figured I don't need to worry about Travis failing as long as the project's tests are working?

The current Travis setup is... painful. SQLCipher tests, particularly, timeout very easily. I often have to restart jobs. So, ideally, everything is green. But it ends up red most of the time.

On pull requests that do not change code, we can ignore Travis.

On pull requests that do change code, running tests is very important, and I inspect Travis failures.

[groue]

Sure thing. I hope it's ok to Judy go ahead for typos etc. as long as I'm minding the checklist.

Gentle contributors very often check everything in the checklist, even when it is not relevant, even when the pull request does not include the checked element. This has not created any real problem, though.

The important checkbox is "This pull request is submitted against the development branch" (because master contains the latest release, and its documentation). This checkbox most often has the desired effect: people submit against the development branch.

[MartinP7r]

Thanks again for the guidance and explanation!

Good to know about the possible timeouts. I've been looking through the Travis logs earlier but couldn't quite make sense of everything.

On pull requests that do not change code, we can ignore Travis.
On pull requests that do change code, running tests is very important, and I inspect Travis failures.

This matches my expectation. Thanks for clarifying!

The important checkbox is "This pull request is submitted against the development branch" (because master contains the latest release, and its documentation).

I have been very thorough to keep an I on the target branch. 👍

[groue]

Thanks for your patience, @MartinP7r :-) Many of my release practices are undocumented. I'll answer your questions if you have any, and we may find opportunities to clarify/strengthen some critical steps.

Meanwhile, here are a few commands that you may find useful one day:

• Run a few tests with the current Xcode version

  make smokeTest 
  

• Run all tests with the current Xcode version (long)

  make test 
  

• Generate reference documentation https://github.com/groue/GRDB.swift/tree/gh-pages

  make doc 
  

• Generate the performance report https://github.com/groue/GRDB.swift/wiki/Performance

  make test_performance | Tests/parsePerformanceTests.rb | Tests/generatePerformanceReport.rb
  

[MartinP7r]

Thank's for the pointer! That is some extensive Makefile you've got there 😳

[groue]

There's a lot of configurations to check!