Milestones
List view
Release Flight Training Exercises to the membership.
No due date•22/22 issues closedThis upgrade will require modifications to various parts of the system. All are documented in issues so we can keep track in the future. All work should be done on the feature/laravel-5.4 branch. 5.4 is not officially supported/released yet.
Due by February 19, 2017•27/27 issues closedBasic Pilot Tracking
Due by December 31, 2016•3/3 issues closedConvert "emails" to Laravel Notifications. Tidy up the superfluous email sending process.
Due by December 31, 2016•22/22 issues closedBasic tracking of ATC Sessions.
Due by December 31, 2016•2/2 issues closedOverhaul the /adm/mship/account listing page as it can exceed 30 seconds of execution time, at times.
Due by December 16, 2016•2/2 issues closedMembers ability to deploy themselves to a community group within the UK.
No due date•4/4 issues closedFollowing on from the Feedback consultation, this milestone will mark the introduction of version 1 of the new feedback system. https://community.vatsim-uk.co.uk/news/operations/she-generally-gave-herself-good-advice-though-she-very-seldom-followed-it-r29/
No due date•8/8 issues closedStats tracking user interface.
No due date•7/7 issues closedAdd BugSnag, TavisCI, StyleCI and other 3rd Party Services now we are an OSS.
Due by December 3, 2016•1/1 issues closedThis is a code improvement release.
Due by December 19, 2015•3/3 issues closedInitial release of the visiting & transferring system: * User * Submit new application * Review old applications * Request references * Admin * Review applications * Reject applications * Accept applications * View application statistics * Review references * Reject references * Accept references
Due by August 21, 2016•18/18 issues closed- Due by October 2, 2016•11/11 issues closed
**Visiting/Transfer** * Pre-requisites for facilities.
No due date•16/16 issues closedUpgrade to Laravel 5.3
No due date•33/33 issues closedThis is a code improvement release. * Implement initial events and listeners (establishing as baseline for their use) * Final postmaster tidy ups * Improve the initial jobs into more useful entities.
Due by January 13, 2016•26/26 issues closedFocus for this release is going to be data cleanup and database changes. * Go through and remove any softDelete references to remove data we really don't care about any more. * Modify MySQL tables to fit inline with our dev guidelines of primary column being "id" and foreign then referencing the table name as a prefix. * Refactor models where appropriate.
Due by July 30, 2016•53/53 issues closedImprovements to SSO & Membership handling: * Secondary Password for when CERT is offline. * Update AutoTools processing * General code improvements
Due by September 28, 2013•9/9 issues closed* Visiting/Transferring * Cosmetic Fixes in ACP * Added V/T Status to dashboard for applicants
No due date•12/12 issues closed* Community Groups * Removal of Legacy Data
No due date•7/7 issues closedMigrate from Kohana (due no ongoing support) to Laravel 4.2.
Due by January 5, 2015•18/18 issues closedFuture membership data storage improvements: * Storage of membership emails * Handling of email changes from AutoTools * Implemented some postmaster stuff.
Due by November 16, 2013•57/57 issues closed- No due date•2/2 issues closed
* Visiting/Transferring * Fixed unauthorized errors on withdrawal * Added auto cancellation * Added extra VT menus in ACP * Preent adding self as referee
No due date•4/4 issues closed* Overhaul of authentication process * We need the ability to challenge a user for their secondary password, anywhere * We require a return to referral page, prior to login and auth challenge as above * Further SSO improvements * NF to review potential SSO implementations. * Reduce the requests/calls made in the entire SSO process. * Decide on the stack of routes to take a user to, at a single point, rather than just keep forwarding until you hit the jackpot.
Due by February 3, 2016•20/20 issues closedIntroduce of Core: * Full SSO Module * Full membership data processing
Due by July 23, 2013* Visiting/Transferring * Membership States are now stored many-to-many * Membership states now store region/division * Verify the region of a referee is the same as the applicant * Application ID is always passed in the URL
No due date•2/2 issues closed* Differentiate between visit/transfer facilities * Allow facilities to be open/closed * Allow training to be required with infinite places
No due date•6/6 issues closedUpgraded from Laravel 4.2 to 5.1 * Ensure PSR-4 namespacing throughout * Retirement of Postmaster (Pat) * Improved membership banning (full system bans are possible) * Ensured nightly scripts honour SSO email assignments * Security improvements * Minor bug fixes
Due by December 16, 2015•9/9 issues closedMigrate teamspeak into Laravel framework: * Automated kicks (bot) * Automated registrations * Better ban handling
Due by March 11, 2015•7/7 issues closed- Due by February 6, 2016•11/11 issues closed
Resolve minor issues with 2.2.4
No due date•5/5 issues closedMoving the defined Mship states from a Model definition to a database relationship. Challenges include: - Soft Deleting M2M - Ensuring that temporary can exist multiple times - Primary (div) can be the only one in existence - There is a hierarchy to determine which is the most important.
No due date•3/3 issues closedImplemented admin control panel: * Full graded permission system * Membership data managed centrally * Improvements to SSO * AutoTools updates * Built in Laravel commands handle many tasks * Push data outward to Community and RTS.
Due by February 26, 2015•40/40 issues closed