Hello,
While we're discussing other "strategic" things, I'd like to also return
to something that was mentioned a couple of times in the past but without
any definitive conclusion, unless I missed it: could we start using CATCH
(http://catch-lib.net/) in the unit tests?
Currently the tests use
On 25 March 2015 at 16:02, Vadim Zeitlin wrote:
> On Wed, 25 Mar 2015 10:19:27 +0100 Mateusz Loskot wrote:
>
> ML> Having master checked out, I'm ready to submit patches back straight away.
>
> Sure, you can submit them -- but currently, i.e. when using git flow with
> Github, they can't be merg
On Wed, 25 Mar 2015 10:19:27 +0100 Mateusz Loskot wrote:
ML> Having master checked out, I'm ready to submit patches back straight away.
Sure, you can submit them -- but currently, i.e. when using git flow with
Github, they can't be merged easily (i.e. using the single button in the
web interfac
On 22 March 2015 at 23:52, Vadim Zeitlin wrote:
> On Sun, 22 Mar 2015 11:36:23 -0700 Pawel Aleksander Fedorynski
> wrote:
>
> PAF> I'd really prefer to defer this decision to Mateusz.
>
> This is not a problem for this particular decision but I'm not sure if
> Mateusz has time for SOCI nowadays
On 17 March 2015 at 14:13, Vadim Zeitlin wrote:
> On Tue, 17 Mar 2015 10:11:26 +0100 Sebastian Lauwers
> wrote:
>
> SL> - Most users who just want the source code don't necessarily need to
> SL> know what the development workflow is. As soon as you start tracking
> SL> the `develop` branch, you
On 17 March 2015 at 10:11, Sebastian Lauwers
wrote:
> Hi all,
>
> I'd like to recommend /against/ this. There are two major implications:
>
> - All PRs will default against `develop`, which is what you're asking,
> - Upon cloning, the checked-out branch will be `develop`.
Yes, this doesn't sound
On 17 March 2015 at 13:02, Asif Lodhi wrote:
> Hi,
>
> Any change that creates more hassle for users instead of the developers must
> not be made. Let the developers deal with the hassle, not the users.
That was part of my reasoning as well.
I assumed developers know the workflow, the GitHub, how
On 16 March 2015 at 13:11, Vadim Zeitlin wrote:
> On Sun, 15 Mar 2015 20:31:12 -0700 Pawel Aleksander Fedorynski
> wrote:
>
> PAF> I don't really understand the implications of what you're asking for,
>
> Sorry, let me try to explain it better: when somebody creates a pull
> request for SOCI re
