Back to the main page.
Bug 282 - make specest development documentation on wiki conform to the other sections
Status | CLOSED FIXED |
Reported | 2010-12-08 15:26:00 +0100 |
Modified | 2012-02-07 11:47:11 +0100 |
Product: | FieldTrip |
Component: | documentation |
Version: | unspecified |
Hardware: | PC |
Operating System: | Windows |
Importance: | P1 normal |
Assigned to: | Roemer van der Meij |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Roemer van der Meij - 2010-12-08 15:26:49 +0100
Robert Oostenveld - 2011-01-16 22:50:47 +0100
changed the status for all ASSIGNED bugs to joint development user (fieldtrip-bugs) to status NEW, otherwise we don't see the in the Wednesday meetings.
Robert Oostenveld - 2011-01-28 15:15:41 +0100
reassigned from fieldtrip-bugs@listserv.surfnet to fieldtrip-bugs@donders, no other change
Robert Oostenveld - 2011-04-27 20:55:24 +0200
changed multiple bugs that already had names attached from NEW into ASSIGNED. If you (as the assignee) don't agree, please reassign it to fieldtrip-bugs and change the status back into NEW.
Roemer van der Meij - 2012-02-02 12:05:24 +0100
Updated the documentation. Robert, could you give it a quick read-through as to whether this is appropriate for module-users?
Boris Reuderink - 2012-02-03 16:30:43 +0100
Roemer, could you add the link to the updated docs?
Roemer van der Meij - 2012-02-06 11:34:01 +0100
There is only one module documentation page, Robert will surely find it? http://fieldtrip.fcdonders.nl/development/specest Is it necessary to use bugzilla as a reference dairy (can't find a better term)? (question also in regards to question on bug 254)
Boris Reuderink - 2012-02-06 15:47:34 +0100
Thanks. On topic of the log/diary issue; I am supposed to verify that bugs are indeed closed, and I need some information to base my judgement on. Further, it might help in transferring detailed knowledge and save time if a bug needs to be transferred or reopened in the future. So I fully understand it feels like a waste of time, but it will save quite a bit of mine :). I think it conforms to the FieldTrip documentation style, so I close this issue.