MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 14 · Source control, environments and publishing

Versions, and living with two

Lesson 138 of 176 · 3 min

Working on THE NEXT ONE while THE CURRENT ONE IS IN USE, and what happens to SOMEBODY MID-TASK WHEN YOU PUBLISH. Versions are what let you develop without disturbing the people using what you already shipped, and the interesting part is the handover. THE MODEL IS THAT ONE VERSION IS LIVE AND YOU WORK ON THE NEXT. Users are unaffected by anything you do until you publish, which is what makes ordinary development possible at all — and it is worth stating because it is easy to forget which one you are looking at. WHICH IS THE FIRST HAZARD: EDITING THE LIVE VERSION BY MISTAKE. Everything behaves normally and the change is in front of users far sooner than intended. Know which version you have open, especially when returning to an application after a gap. AND THE PERSON MID-TASK IS THE PART NOBODY PLANS FOR. A user three pages into…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 14 · Source control, environments and publishing

  1. 1What a publish actually doesFree preview
  2. 2Versions, and living with two
  3. 3Source control, and why a visual tool still needs it
  4. 4Branching and more than one developer
  5. 5Environments, and what differs between them
  6. 6Making endpoints configurable
  7. 7The promotion checklist
  8. 8Rolling back
  9. 9Automating it
  10. 10What breaks: four promotion failures
  11. 11Lab briefing · Promote and prove it is isolated