mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-06-26 10:54:26 +02:00
Docs: Updated URLs
This commit is contained in:
parent
05e0091212
commit
765db3093a
9 changed files with 23 additions and 24 deletions
1
AUTHORS
1
AUTHORS
|
@ -142,6 +142,7 @@ The following submitted code, packages or analysis, and deserve special thanks:
|
|||
Paul J. Fenwick
|
||||
Michael Neumann
|
||||
Mark Scannell
|
||||
buhtz
|
||||
|
||||
Thanks to the following, who submitted detailed bug reports and excellent
|
||||
suggestions:
|
||||
|
|
10
DEVELOPER.md
10
DEVELOPER.md
|
@ -18,7 +18,6 @@
|
|||
# Alternately 'export MAKEFLAGS=-j 4'
|
||||
```
|
||||
## Running Test Suite:
|
||||
|
||||
```
|
||||
$ cd tests
|
||||
$ make VERBOSE=1 # Shows details
|
||||
|
@ -117,9 +116,10 @@
|
|||
|
||||
## Tests needed
|
||||
|
||||
* Take a look at the bug database (https://bug.tasktools.org) and notice that
|
||||
many issues, open and closed, have the "needsTest" label. These are things
|
||||
that we would like to see in the test suite, as regression tests.
|
||||
* Take a look at the bug database (https://github.com/GothenburgBitFactory/taskwarrior/issues)
|
||||
and notice that many issues, open and closed, have the "needsTest" label.
|
||||
These are things that we would like to see in the test suite, as regression
|
||||
tests.
|
||||
|
||||
All new unit tests should follow the test/template.t standard.
|
||||
|
||||
|
@ -153,5 +153,3 @@
|
|||
* Current development branch no plans yet.
|
||||
|
||||
---
|
||||
|
||||
__2017-02-28__ Updated for 2.6.0
|
||||
|
|
6
NEWS
6
NEWS
|
@ -44,7 +44,7 @@ Removed Features in 2.6.0
|
|||
|
||||
Known Issues
|
||||
|
||||
- https://bug.tasktools.org/
|
||||
- https://github.com/GothenburgBitFactory/taskwarrior
|
||||
|
||||
Taskwarrior has been built and tested on the following configurations:
|
||||
|
||||
|
@ -61,11 +61,11 @@ Taskwarrior has been built and tested on the following configurations:
|
|||
While Taskwarrior has undergone testing, bugs are sure to remain. If you
|
||||
encounter a bug, please enter a new issue at:
|
||||
|
||||
https://bug.tasktools.org
|
||||
https://github.com/GothenburgBitFactory/taskwarrior<Paste>
|
||||
|
||||
Or just send a message to:
|
||||
|
||||
support@taskwarrior.org
|
||||
support@GothenburgBitFactory.org
|
||||
|
||||
Thank you.
|
||||
|
||||
|
|
|
@ -33,11 +33,12 @@ For support options, take a look at:
|
|||
|
||||
http://taskwarrior.org/support
|
||||
|
||||
Please send your code patches to:
|
||||
Please use pull requests, or send your code patches to:
|
||||
|
||||
support@taskwarrior.org
|
||||
support@GothenburgBitFactory.org
|
||||
|
||||
Consider joining bug.tasktools.org and participating in the future of Taskwarrior.
|
||||
Visit https://github.com/GothenburgBitFactory/taskwarrior and participate in
|
||||
the future of Taskwarrior.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
@ -321,7 +321,7 @@ The official site at
|
|||
|
||||
.TP
|
||||
The official code repository at
|
||||
<https://git.tasktools.org/scm/tm/task.git>
|
||||
<https://github.com/GothenburgBitFactory/taskwarrior>
|
||||
|
||||
.TP
|
||||
You can contact the project by writing an email to
|
||||
|
|
|
@ -173,11 +173,11 @@ The official site at
|
|||
|
||||
.TP
|
||||
The official code repository at
|
||||
<https://git.tasktools.org/scm/tm/task.git>
|
||||
<https://github.com/GothenburgBitFactory/taskwarrior>
|
||||
|
||||
.TP
|
||||
You can contact the project by writing an email to
|
||||
<support@taskwarrior.org>
|
||||
<support@gothenburgBitFactory.org>
|
||||
|
||||
.SH REPORTING BUGS
|
||||
.TP
|
||||
|
|
|
@ -1326,13 +1326,13 @@ The official site at
|
|||
|
||||
.TP
|
||||
The official code repository at
|
||||
<https://git.tasktools.org/scm/tm/task.git>
|
||||
<https://github.com/GothenburgBitFactory/taskwarrior>
|
||||
|
||||
.TP
|
||||
You can contact the project by emailing
|
||||
<support@taskwarrior.org>
|
||||
<support@GothenburgBitFactory.org>
|
||||
|
||||
.SH REPORTING BUGS
|
||||
.TP
|
||||
Bugs in Taskwarrior may be reported to the issue-tracker at
|
||||
<https://bug.tasktools.org/>
|
||||
<https://github.com/GothenburgBitFactory/taskwarrior/issues>
|
||||
|
|
|
@ -1531,14 +1531,13 @@ The official site at
|
|||
|
||||
.TP
|
||||
The official code repository at
|
||||
<https://git.tasktools.org/scm/tm/task.git>
|
||||
<https://github.com/GothenburgBitFactory/taskwarrior>
|
||||
|
||||
.TP
|
||||
You can contact the project by emailing
|
||||
<support@taskwarrior.org>
|
||||
<support@GothenburgBitFactory.org>
|
||||
|
||||
.SH REPORTING BUGS
|
||||
.TP
|
||||
Bugs in Taskwarrior may be reported to the issue-tracker at
|
||||
<https://bug.tasktools.org/>
|
||||
|
||||
<https://github.com/GothenburgBitFactory/taskwarrior/issues>
|
||||
|
|
|
@ -91,8 +91,8 @@ If you wish to contribute tests, please consider the following guidelines:
|
|||
test script, such as filter.t, export.t, whichever is appropriate.
|
||||
|
||||
* Tests created after bugs or feature requests should (ideally) have an entry
|
||||
on https://bug.tasktools.org/ and should include the issue ID in a
|
||||
docstring or comment.
|
||||
on https://github.com/GothenburgBitFactory/taskwarrior/issues and should
|
||||
include the issue ID in a docstring or comment.
|
||||
|
||||
* Class and method names should be descriptive of what they are testing.
|
||||
Example: TestFilterOnReports
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue