Upcoming AIRAC - 1704

[Chris Pawley]

Hello

 

Tomorrow is AIRAC day again, we will begin a 4 week sprint to add as many new features, updates and bug fixes to the UK Sector File. I'm keen to develop a functional workflow for all of us! I've been happy with the development we have achieved in the last two cycles; but I really want to make sure we can reduce as much the man-hours it it necessitates.

 

I propose some kind of standard workflow for every 28 day cycle along the following lines:

 

Timeline (AIRAC +28 means the AIRAC change is 28 days from this moment in our timeline)

AIRAC +28 I will take care of downloading the AIRAC change documents to our local google drive folder (for correct linking in issues) (and provide the URL here)

AIRAC +28 -> AIRAC +22 - we take some time to scan through changes proposed from AIP - make issues in Github tagged to 1704 Milestone and ensure that nothing gets missed and linked to the documents from the first step.

[Behind the scenes, I will identify all the other tasks generated by this AIRAC change (non-sector file related) and create a working list of these for me and other staff to work on.]

AIRAC +22 -> AIRAC +10 - The Sector File team (you!) complete outstanding issues

AIRAC +10 -> AIRAC +7 - I'll build a DEV version of sector file generated and shared for testing of big or complex changes (and provide the link here)

[Behind the scenes, the controller pack is also updated in this time]

Approx AIRAC +3 Development Freeze - after this time I like to start packaging things for download.

Approx AIRAC +2 Release versions of SCT/ESE etc. build and double checked

Approx AIRAC +1 Forum Posts Updated, Download links Updated, Euroscope's Automated Download Tool Updated

 

As we go through these stages, I'll update this post to show what we're all working on right now.

As ever, if you want to contribute, please do! Find our repo at www.github.com/vatsim-uk/uk-sector-file. If you have questions, find me on Slack or in the Helpdesk.

 

Chris.

Edited April 1, 2017 by Chris Pawley

[Chris Pawley]

So we're now at the end of the development cycle. I am afraid with CTP happening last week, I was unable to focus on Operations as much as I should, and couldn't release the DEV version.

 

Never the less, I am now building the release versions in time for tomorrow.

 

Chris.

[Chris Pawley]

So everything is ready for release. Waiting on a small technical fix and we'll get everything online.

Chris.

[Chris Pawley]

Everything is released now for 2017/04

 

Thanks everyone who contributed.