0.4.0 Release Plan

We want to get release 0.4.0 to master ASAP.

Our starting branch is issue/216-B. A new branch called release/0.4.0 has been made with the same HEAD commit as issue/216-B (3dad157). All work leading up to the 0.4.0 release will be made to release/0.4.0.

We have work on 4 other branches that needs to be reconciled and merged:

• issue/216
• issue/216-G
• master
• issue/150

The merging of the issue/150 branch might be pushed back until after the 0.4.0 release.

The following tasks should be considered. Each of these will be made into an issue and then added to the Release 0.4.0 Project.

• #279 - Reconcile/merge tasks from issue/216-G
• #281 - Reconcile/merge tasks from issue/216
• #282 - Reconcile/merge tasks from master
• #280 - Full source review of issue/216-B
• Review oustanding issues
• Add --merge option for pull
• Pull requires --merge or --rebase or --force or a .gitrepo 'method'
• --update option adds method (merge|rebase|force) to .gitrepo for pull command
• --method= option adds method (merge|rebase|force) to .gitrepo for clone and init
• push command should not pull. pull must be done iby user first.
• fix --edit bug (whatever that is (old notes))
• tests for new stuff
• update docs
  • https://gist.github.com/anonymous/76b73dceda253756d860d9c5afad87f8 might be useful

Release 0.4.0 Project.

Project Columns:

• All items about will go into the 'Tasks' column.
• Only Ingy will move things from Tasks to 'Next Tasks' column.
• Anyone (Magnus or Ingy) or can take an issue from Next Tasks to In Progress
  • They should self assign the issue when they do that
• When they are done they move it to Needs Review
• Ingy will review and move to Done or back to In Progress