Skip to content

Remove duplicate source trees #8

Open
@roachspray

Description

@roachspray

In the steps leading to what apps are in the suite now, we did the following process:

  • Gather known bugs related to a version(s) or date-time/commit
  • If there seems to be more than 1 version that holds the bugs, compile a few likely versions and run the inputs through to determine which of those versions has the most known bugs.
  • Use the version with the most known bugs as the starting point.

In my (ridiculous and perhaps unwarranted) haste to push this to GitHub to coincide with the Japan summit, I left duplicate trees here and committed them. Fix this so there is only one.

Realize it may also be worthwhile to document the above known-bugs version vetting.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions