Your SlideShare is downloading. ×
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Apereo OAE development and release process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Apereo OAE development and release process

206

Published on

Brief overview of the Apereo OAE development and release process.

Brief overview of the Apereo OAE development and release process.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
206
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Development and release process
  • 2. • Perfect slice • Stakeholders • Design process • Development process • Performance testing • Release process
  • 3. Perfect slice • Develop feature from top to bottom • Design, testing, development, review, performance testing, model loader additions, internationalisation reach-out, QA, release, roll out into production, further testing • Make it ready to be used in large-scale production environment • Prioritising slices becomes very important
  • 4. Stakeholders • OAE has multiple institutions as stakeholders • All have unique (edge case) requirements • Need to deal with this as an OS project • Need to keep the UI simple • Shared edge cases can be layered away
  • 5. Design • Starts with a need • Create wireframes • Go through user testing • Deliver finished designs to development
  • 6. Development • HTML, CSS and JavaScript implementation in front-end • Back-end REST APIs • Write tests to verify the implementation • Front-end: CasperJS (headless webkit) • Back-end: Mocha (through REST APIs) • Code review • Merge into master (more on this later)
  • 7. Performance testing • Tsung • Simulate users in order to test scalability (stress testing) • Decrease in performance === investigate/hold off release • Before every release (major or maintenance) • Analysis of Tsung graphs and Circonus data
  • 8. Release • A major OAE release is usually defined by the implementation of a new user facing piece of functionality (e.g. `Following` feature) • An OAE maintenance release is usually defined by a set of refinements to already existing functionality (e.g. Design refinements to `Following` feature or non-user facing functionality) • All releases (major or maintenance) go through the same workflow
  • 9. Release • Decide to release • • Triage bugs, fix blockers first • • Bug bash (on optimised build) Reiterate Start final release process
  • 10. Release front-end • Update version in package.json • Fix versions for used node modules • Note: In development we use the latest modules to detect any problems when those change to a newer version • Clean out node_modules and test with fresh install one final time • Tag new version in Github (e.g. 1.0, 2.3) • • Tagging ‘copies’ and ‘freezes’ the code at the point the tag was created. `grunt release` and publish to a VM and test
  • 11. Release back-end • Update version in package.json • Fix versions for used node modules • Note: In development we use the latest modules to detect any problems when those change to a newer version • Clean out node_modules and test with fresh install one final time • Tag new version in Github (e.g. 1.0, 2.3) • Tagging ‘copies’ and ‘freezes’ the code at the point the tag was created. • Publish PPA • `grunt release` and publish to a VM and test
  • 12. Sources • https://www.slideshare.net/bertpareyn/oaedevelopment-and-release-process/ • http://oaeproject.org/blog • http://crowdin.net/project/apereo-oae • https://github.com/oaeproject/3akai-ux • https://github.com/oaeproject/Hilary • https://oae.oae-qa0.oaeproject.org/

×