BREAKING CHANGE: RunnerOptions.IncludeUntaggedMaintenanceMigratrions will now default to true

[jzabroski]

Is your feature request related to a problem? Please describe.
See #1062, #1607, #1591

Describe the solution you'd like
To make the default behavior of fluent migrator to include untagged maintenance migrations, consistent with untagged migrations. This legacy behavior has caused a lot of confusion.

[rhegner]

Could you please provide an example of such an "untagged maintenance migration"?

I've been using fluentmigrator for a long time, but based on this pretty short description I'm not sure if/how this breaking change is affecting my codebase.

[jzabroski]

Great question.

[Maintenance(Stage.AfterAll)]
//Tags("NonProduction")] // uncommenting this would make it a tagged migration 
public SetUpNonProductionTestDependencies : Migration
{
    public void Up() 
    {
        // code
    }
}

Let me know if it's not clear.

In general, it seems a lot of people were thrown off by this behavior, and it makes configuring Dependency Injection harder and less intuitive. I thought about refactoring the whole way we handled maintenence migrations, but I realized the simplest fix is to just make the overall approach consistent between regular migrations and maintenance migrations.

[rhegner]

Thanks for the quick response (and for this great library)!
It is clear now.