Alpha Development cycle

[BradleyChatha]

Each Alpha version should have a Github Project created for it, to easily keep track of it.

All features, bugs, and any other things of interest should have an issue created for them, these issues assigned to the version's project.

If possible, assign a time frame for non-minor issues, to try and "gently" motivate me to actually do things that don't involve rewriting a million different things. To keep things simple, time frames are on the span of days. If anything takes even less than a day, still put it as [1 Day] or [<1 Day].

Once a version is complete, allow Andy a week or two to test the new version, taking in feedback.

Create new alpha version based on feedback, as well as features that still need to be implemented.

Repeat over and over until both me and Andy are happy with the website, finalise some things like a Terms of use and Privacy Policy, then begin a Beta Development Cycle that includes general staff using the website.

P.S. I still have no idea what I want to do about testing yet. I'm still clueless about automated website testing, so a manual test plan might need to be developed and practiced before each release.

After the beta dev cycle, the website is considered production ready, and then we need to look into whether we want to start selling it, which also includes setting up automation to create new instances of FarmMaster, instructions on pointing our customer's domain there, etc.

[BradleyChatha]

Can I still pin this while it's closed?