List view
- Due by January 30, 2026•1/1 issues closed
- No due date•5/5 issues closed
- Due by June 27, 2025•10/10 issues closed
- Due by January 3, 2025•7/7 issues closed
- Due by February 29, 2024•23/23 issues closed
- Due by December 1, 2023•8/8 issues closed
- Due by November 1, 2023•3/3 issues closed
- No due date•9/9 issues closed
- Due by June 1, 2022•13/13 issues closed
- No due date•21/21 issues closed
- No due date•8/8 issues closed
- No due date•5/5 issues closed
- No due date•1/2 issues closed
QoL update
No due date•9/9 issues closed- Due by January 31, 2019•6/6 issues closed
- Due by January 15, 2019•6/6 issues closed
- No due date•5/5 issues closed
- No due date•13/13 issues closed
- No due date•6/6 issues closed
Django 2.2 LTS is expected to release in April 2019. Devilry 3.x supports Django 1.11 LTS, which is the last Django version to support Python 2. Upgrading could therefore entails some major changes to Devilry. Django 1.11 LTS is supported to (at least) April 2020, but since the production environments are constrained by academic semesters the transition should be done before the Spring semester of 2020. A realistic deadline with time to do production adjustments would therefore be in the Fall of 2019.
Due by October 31, 2019•2/2 issues closed- Due by April 13, 2018•9/9 issues closed
Add user documentation for Devilry 3.x.x. A branch has been created for this called `milestone-devilry-3-minimal-user-documentation` which is the branch that will be merged with master after updates.
Due by April 13, 2018•4/4 issues closed#949 Manglende tag-filtrering (#943 Bestått tidligere semestre (halvferdig i 3.0.0) - hvis dette er ferdig/kreves for å få på plass #953) #953 Manuell godkjenning (kanskje noe kun department administrators eller høyere skal kunne gjøre?) #945 Navigasjonskræsj Dataporten (browser back navigation)
Due by February 16, 2018•4/4 issues closed- Due by January 29, 2018•5/5 issues closed
Oppgaver som må løses før Devilry kan rulles ut til testkurs gjennom vårsemesteret 2018
Due by January 19, 2018•5/5 issues closedEndringer som skal vurderes før 22. mars.
Due by March 22, 2017•2/2 issues closedPrimary focus: Make user management far more powerful and streamlined without the need of an external user/role system.
No due date•100/100 issues closed- No due date•2/2 issues closed
- No due date•4/4 issues closed
- No due date•51/51 issues closed
- Due by February 3, 2015•23/23 issues closed
- No due date•2/2 issues closed
The stuff that had to mature a couple of days after 1.2.1
Due by January 21, 2013•3/3 issues closedWe put all minor issues from 1.2.1 that we do not believe to be critical here. These issues will most likely be released as minor versions 1.2.1 (1.2.1.X), and then we will release 1.2.2 when all issues are closed.
No due date•14/14 issues closedUpdate and modernize the examiner interface.
No due date•28/28 issues closedIn this milestone, we will add a few more utilities to the subject administrator UI from 1.2. We will also create a completely new but very simple UI for node (faculty, department) admins.
Due by January 18, 2013•11/11 issues closedIn this milestone we will add views that are not explicitly required for the new Subjectadmin UI. However these new views will probably help a lot of people. Note that we may choose to split this milestone into multiple minor releases.
No due date•8/8 issues closedThe 1.2 version of Devilry will include a brand new administrator user interface for administrators.
Due by December 21, 2012•39/39 issues closedThings we did not prioritize for 1.1.
Due by August 29, 2011•5/5 issues closedStable ugly GUI
Due by July 21, 2011•2/2 issues closedThings left over from 1.0 that we could postpone for a week.
Due by July 19, 2011•10/10 issues closedAdds features/sugar to the stable release, and improves integration with other systems.
Due by August 2, 2011•11/11 issues closedFirst stable release.
Due by July 11, 2011•16/16 issues closed