List view
- Overdue by 6 year(s)•Due by November 2, 2018•17/17 issues closed
- Overdue by 6 year(s)•Due by September 6, 2018•28/28 issues closed
- Overdue by 7 year(s)•Due by May 23, 2018•12/12 issues closed
- Overdue by 7 year(s)•Due by February 1, 2018•27/27 issues closed
- Overdue by 7 year(s)•Due by April 9, 2018•25/25 issues closed
- Overdue by 7 year(s)•Due by December 21, 2017•22/22 issues closed
Schedule: Code Freeze: Monday October 23rd 9AM PR merged: Monday October 23rd 3PM Release candidate deployment: Monday October 23rd 3PM Release candidate testing deadline: Friday October 27th 3PM Main system deployment: Wednesday November 1st 7AM
Overdue by 7 year(s)•Due by November 1, 2017•34/34 issues closedSchedule --------- Code freeze: Monday September 18th 9AM PR merged: Monday September 18th 3PM Release Candidate deployment: Monday September 18th 3PM Release Candidate testing deadline: Friday September 22nd 3PM Main System deployment: Wednesday September 27th 7 AM Main functionality (see issue list for full description) ------------------ - RedBiom - CMI-Workshop issues
Overdue by 7 year(s)•Due by September 27, 2017•9/9 issues closed- No due date•108/108 issues closed
- No due date•203/203 issues closed
The first Qiita release. It should include: 1. RESTfull API 2. Bug-fixes 3. Usability testing
No due date- Overdue by 10 year(s)•Due by July 3, 2015•136/136 issues closed
Qiita should be fully functional and the developers are feeling great with the code that we have. At this stage, minimal API changes should be done. A detailed description of the goals: 1. Easy deployment 2. Sphinx documentation 3. Support other tools/datatypes i. Metabolomics ii. WGS iii. Single Strain WGS 4. Revisit all db objects, with special attention to: i. Job ii. Analysis iii. Collection and Investigation objects iv. Reference object - should include the already indexed DB. 5. Refactor job submission 6. Refactor all handlers. Testing handlers is tricky. The best way to do this will be to move all code out from the handlers, into a qiita_pet module (or qiita_ware if needed) and the handlers only parse the arguments and call this new API. 7. Improve testing framework and raise coverage (with good testing) to at least 97%. i. This should also include user usability testing. 8. UI for adding new references and parameters set 9. Stable API
No due date•19/19 issues closedThis milestone keeps track of the minimal set of features, improvements, and bug fixes that are required before we release qiita to a wider audience.
Overdue by 10 year(s)•Due by November 22, 2014•42/42 issues closed- Overdue by 10 year(s)•Due by April 17, 2015•134/134 issues closed
Features and bugfixes we want done for the pre-alpha release
Overdue by 10 year(s)•Due by September 19, 2014•13/13 issues closed- Overdue by 10 year(s)•Due by August 23, 2014•13/13 issues closed
This milestone contains all the issues that need to be solved in order to be able to insert data into the database through the command line interface.
No due date•4/4 issues closedImplement all the classes needed to interact with the DB from Python.
Overdue by 11 year(s)•Due by June 3, 2014•16/16 issues closed