From 4ab083fd946b527a29321d2b6515fa6fc5bdc221 Mon Sep 17 00:00:00 2001 From: Paul Beckingham Date: Wed, 25 Jan 2017 17:45:03 -0500 Subject: [PATCH] Docs: Updated compiler version --- DEVELOPER | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/DEVELOPER b/DEVELOPER index 8d3b462db..6bf0140fa 100644 --- a/DEVELOPER +++ b/DEVELOPER @@ -1,8 +1,8 @@ How to Build Taskwarrior Satisfy the Requirements: - - gcc 4.7 or later, clang 3.3 or later or equivalent. This is because C++11 - is now used. + - gcc 4.9 or later, clang 3.3 or later or equivalent. This is because C++11 + is now used throughout the source. - libuuid - gnutls (optional) - python 2.7 or 3 (optional, for running the test suite) @@ -31,6 +31,7 @@ How to Build Taskwarrior against git HEAD on the development branch. We cannot apply patches made against the tarball source, or master. + General Statement This file is intended to convey the current efforts, priorities and needs of the codebase. It is for anyone looking for a way to start contributing. @@ -103,6 +104,7 @@ General Statement Next are some specific areas that need attention. + New Code Needs This is code that needs to be written. @@ -118,6 +120,7 @@ New Code Needs lie outside of the core product, and will be implemented as external scripts by anyone who wishes to participate. + Unit Tests Needed There are always more unit tests needed. More specifically, better unit tests are always needed. The convention is that there are four types of unit test: @@ -157,4 +160,4 @@ Current Codebase Condition --- -2016-12-18 Updated for 2.6.0 +2017-01-24 Updated for 2.6.0