List view
Post-launch release with the stuff Intercon didn't need at launch, but will need before signups
Due by June 1, 2018•4/4 issues closedThe goal of the 2.2 release is to generalize the concept of "event categories" so that it's easier to support non-larp events and much less has to be hardcoded about this business logic.
No due dateDEPRECATED - we're using project boards for this, not milestones. Sorry for confusion. Goals: * Make it possible to replace Concentral (aka ProCon) with Intercode * Make event categories adminable on a per-convention basis * Clean up tech debt (Note: this milestone is a merge of the previous 2.1 and 2.2 milestones; the event categories feature turns out to be important for replacing Concentral.)
No due date•11/15 issues closedThe first stable release of Intercode 2. Welp, we didn't hit the end-of-June-2017 deadline, so I'm setting a new deadline of February 1, 2018 so that we could (hopefully) roll this out for Intercon S. The mission statement of this release: "do everything Intercon needs Intercode 1 to do, but in a modern web application." Features Intercode 1 doesn't do may be pushed to later releases accordingly.
Due by February 1, 2018•32/32 issues closed