Define "getting started" user stories, improve APIs to support

[badgerwithagun]

Morf grew organically with Alfa Systems, so we have never actually documented how to implement it from scratch in a new project. In finalising these user stories, we will be both documenting them for new users and implementing any new APIs necessary to make the experience right.

[badgerwithagun]

In progress

[badgerwithagun]

Main issues:

• No way of using Upgrade or Deployment without Guice (addressed partially by Partial #6: Allow upgrade/deployment without Guice #37)
• Jira ID should be removed from Morf's UpgradeStep interface
• Lack of functional consistency in where annotations or methods are used on UpgradeStep

[Jaffa]

Jira ID should be removed from Morf's UpgradeStep interface

Presumably you're imagining replacing it with an annotation? There's some niceness to having a get change id method. We could have an AbstractUpgradeStep that implemented that by reading the UUID annotation; but projects that do have overarching change control (whether github, JIRA, ...) still have a place to ensure the metadata is captured.

[badgerwithagun]

An annotation was the thinking, yes, but it'd probably not be part of Morf, unless we generalised it (e.g. @TicketNumber or something).

[badgerwithagun]

@Jaffa, @tsg21, could you have a look at https://github.com/alfasoftware/morf/wiki/Start-Here and make any changes you think appropriate?

That's stage 1 out of the way...

[tsg21]

I've tweaked that to fix some typos, plus added wiki/Key-Features

[badgerwithagun]

Sweet, cheers!

[badgerwithagun]

Made some progress here.

Main remaining issues:

• Lack of fluent SQL execution support (with me)
• Removing JIRA ID from UpgradeStep

Then I think we can close this bit off and start working on documenting/improving the rest of the toolset.