Skip to content

Milestone development process specification template(Old)

ChenMo edited this page Feb 11, 2022 · 1 revision

The total time of the milestone is 8 weeks, divided into three stages: planning, development, and release. PM controls the overall rhythm and process, and the person in charge of the module controls the details.

image.png

PM:

  • Engine issues:
  • Editor issues:

Planning

Planning milestone content, please check ✅ after the person in charge of each module has completed the planning.

Core:

Second party library:

Development

  • Due to the uncertainty caused by the workload of the milestone development content or the energy allocation of the development students, please communicate with the PM in time for feedback.
  • There are parallel and serial problems in the development of each content of the milestone. For the specific timeline, please refer to the figure below. Pay attention to the rhythm and control.

image.png

Development milestone content, please check ✅ after the acceptance of each module leader.

Core:

Second party library:

Release

image.png

Release milestones, please check ✅ after each release person in charge completes.

Release pre-release version

Publish pre-release npm packages and prepare pre-release content. During the development phase, link local debugging is usually used. After the alpha version of the npm package is released, the real npm workflow can be used for testing.

Release Engine alpha version npm package @GuoLei1990

  • NPM

Release Spine alpha npm package @johanzhu

  • NPM

Release the Lottie alpha npm package @eyworldwide

  • NPM

Release Mars alpha npm package @singlecoder

  • NPM

  • Prepare the Editor alpha version @czizzy

Pre-release regression testing

Regression testing and inspection of the milestone functions and content of the pre-release version. Please fix it in time after finding the BUG.

Engine:

  • Performance check @GuoLei1990

Editor:

  • User flow check @czizzy
  • Features check @czizzy
  • Script API tips check @gz65555

Editor‘s second party library:

  • Mars function check @singlecoder
  • Spine function check @johanzhu
  • Lottie function check @eyworldwide

Official website:

  • Official website function check in dev branch @eyworldwide
  • PlayGround case check @zhuxudong
  • Documents and case checks in documents @cptbtptpbcptdtptp
  • GLTF Viewer @zhuxudong

Release stable version

elease the stable version of the npm package and prepare the official version of the content. Prepare the final release content.

Release Engine stable version package @GuoLei1990

  • NPM
  • CDN

Release Spine stable version package @johanzhu

  • NPM
  • CDN

Release Lottie stable version package @eyworldwide

  • NPM
  • CDN

Release Mars stable version package @singlecoder

  • NPM

  • CDN

  • Prepare Editor stable version @czizzy

Stable version regression test

Regression test and check on the milestone functions and content of the official version. The last process to ensure the normal release of the engine.

Editor:

  • User flow check @czizzy
  • Features check @czizzy
  • Script API tips check @gz65555

Editor‘s second party library:

  • Mars function check @singlecoder
  • Spine function check @johanzhu
  • Lottie function check @eyworldwide

Official website:

  • Official website function check in dev branch @eyworldwide
  • PlayGround case check @zhuxudong
  • Documents and case checks in documents @cptbtptpbcptdtptp
  • GLTF Viewer @zhuxudong

Tool:

Officially released

  • Publish logs @GuoLei1990
  • Online the official version of the editor @czizzy
  • Online official website @eyworldwide
  • Blog publish-Zhihu @singlecoder
  • Blog publish-Nuggets @singlecoder
  • Blog publish-WeChat @singlecoder
  • Blog publish-ATA @singlecoder