Software Lifecycle
PVFA has establised the following process for Renewing/Distributing Software:
This primarily effects Classrooms and Computer Labs but if Faculty/Staff are using the builds made available to them they will update via this same process.
When possible we align to industry standard lists such as the VFXReferencePlatform
Kickoff Meeting
Timeframe: January - February
- The Pipeline Engineer puts out a notice to the VizTechCommittee (sent to the entire faculty/staff listserv) that there will be a meeting to evaluate software
- Conduct Kickoff Meeting and show off currently available software, anticipated versions for subsequent academic year and take comments and or additional requests
Present Software Build Plan
Timeframe: March - April
Compile and collate feedback and requests into an overall Software Build Plan factoring in budget to present to the VizTechCommittee for Approval. This list will be posted as a Proposed software list on our Classroom Software page
If changes need to be made it will be done at this time with the overall goal of having an approved plan completed by May.
Finalize Software Build Plan
Timeframe: May 1st
Finalize Software Build Plan and submit to Technology Services.
Execute Software Build Plan
Timeframe: May - June
Technology Services builds requested software packages in the test environment and configures licensing as necessary.
Test Software
Timeframe: June - July
Pipeline Team tests software workflows to ensure compatibility and reliability.
Move to Production
Timeframe: Mid-July (minimum 2 weeks before start of fall semester)
Technology Services moves packages to production environment, updates the Classroom Software List page and proceeds with the mass reimage of Classroom Podium and Lab computers with the goal of having this complete by August 1st.