Processes

These are the processes I follow when working on the project. Please follow them as well. If you have any suggestions for changes, please let me know.

---

Creating an Issue

1. Create issue with informative title and description
2. Label as bug, feature, code
3. Label as willfix, wontfix, notmyproblem, invalid (Eventually, at least)
4. Assign to a milestone if necessary

---

Fixing an Issue

1. Find Issue to fix
2. Comment the issue to indicate that you're working on it, or assign to yourself
3. Actually code stuff to fix it, run, test
4. Commit with "fixes #1234", push (this will close the issue)

---

Release Beta version

1. Determine that IGN++ is sufficiently stable/cool to release to beta channel
2. Run build.sh to get a xpi and zip file
3. Upload xpi to addons.mozilla.org as a new version
4. Upload xpi to vestitools.pbworks.com
5. Increment version in install.rdf according to whatever plan you have (like go from a1 to a2, or decide to go to b1)
6. Change Chrome manifest.json to match next version (see versioning.txt)

---

Release Public Version

1. Determine that this version of IGN++ is sufficiently stable/complete to release to the public
2. Release beta version that will be (almost) identical to final version
3. Merge version branch into master, change version to final (see Release Beta Version step 6-7), tag commit with version tag
4. Perform release Beta Version steps 2-5
5. Write up Revision History entry on wiki (see previous ones)
6. Post a topic on vesti about new release which includes Revision History entry (made more digestible if necessary), link to revision history, link to wiki, link to installation instructions, link to github. See this thread: http://boards.ign.com/teh_vestibule/b5296/195805639/p1
7. Stick around in thread to answer questions, pray you pass Mozilla review
8. Increment version to alpha and start a new version branch