search

132nd-vWing / 132nd-Virtual-Wing-Training-Mission-Tblisi

Training Mission used by the 132nd Virtual Wing flying DCS World
The Unlicense
6 stars 1 forks source link

MOOSE updating policy #24

Closed theendsofinvention closed 7 years ago

theendsofinvention commented 7 years ago

The TRMT uses the well known MOOSE framework.

I would like to discuss our policy on updating it.

A) On one hand, we can stick with the "stable" version, and update very seldom.

B) On the other hand, we could update more often to the latest dev version, and enjoy the latest bugfixes and features, while taking the risk of bugs. This approach would also have the indirect added benefit of helping MOOSE's creator in finding & fixing bugs.

When it comes to implementation, there are 5 options that I can think of:

  1. update moose.lua manually.
  2. have appveyor automatically pull the latest version during the build (that one raises question about propagating the change back to GH)
  3. use a Git hook to pull the file before pushing
  4. add the MOOSE repository as a submodule
  5. add the MOOSE repository as a subtree

Votes are open ! Mine goes for B5.

132nd-Entropy commented 7 years ago

I agree and also vote B5

132ndNeck commented 7 years ago

I do not know enough about this to cast a vote. But from my limited view, a version of option B is likely the best choice.

theendsofinvention commented 7 years ago

Understood, the consensus for B is obvious.

@132nd-Entropy would you mind building & pushing the latest MOOSE from time to time for the time being ? I'll assign this to myself and will work on an automated solution.

132nd-Entropy commented 7 years ago

totally dont mind at all

132nd-Entropy commented 7 years ago

I will periodically update moose and closing this issue