Matt

It would be possible to create a new source driver that introduces custom markup to combine the up and down migration into one file.

That's expected. I forced push to `master`. At this point, v3 is not a drop in replacement for v1. Especially since not all drivers are available, yet. In order to...

I apologize for the inconvenience and I can understand everyones frustration over this. What can we do to make this easier? I could update the import paths for the drivers...

For Postgres and Mysql, I just added upgrade guides: https://github.com/mattes/migrate/tree/master/database/postgres#upgrading-from-v1 https://github.com/mattes/migrate/tree/master/database/mysql#upgrading-from-v1 This doesn't solve the `go get v1` issue, yet. More updates on that in the next hours. Thanks for...

@UnrealKazu Re: no `create` command. There are several questions around the expected behavior for `create`: `timestamp or number?` _ migration_name _ `extension?` To get the extension, in v1 the driver...

@tfmertz Just check for `ErrNoChange`. If you see it, you know you can continue.

I renamed all import paths (https://github.com/mattes/migrate/pull/212) to point to `gopkg.in/mattes/migrate.v1`. Getting this error. Can someone help? ``` go get -v gopkg.in/mattes/migrate.v1 Fetching https://gopkg.in/mattes/migrate.v1?go-get=1 Parsing meta tags from https://gopkg.in/mattes/migrate.v1?go-get=1 (status code...

I'm sorry for the confusion and inconvenience @endophage Regarding the directories. Do you think it makes sense to refactor it?

I'm trying my best to improve docs. Please feel free to PR things in as well. Every help is appreciated!

Oh, interesting. I see. Let me try that. Thanks for your help!