plan for making breaking changes

vmware-archive / cloudformation-resource

Concourse CI resource for AWS CloudFormation

BSD 2-Clause "Simplified" License

7 stars 16 forks source link

plan for making breaking changes #5

Open mmb opened 8 years ago

mmb commented 8 years ago

leave existing master / pipeline as is
create new branch (dev?) and put all new code there
create a DockerHub automated build and create a docker tag with the new code
at some point in the future, notify users and merge that branch to master

Thoughts?

/cc @dpb587

dpb587 commented 8 years ago

Sounds practical. Alternatively, just keep breaking change PRs unmerged until you/users have had enough notice and time to test.

Do you have a preference for DockerHub automated build vs building from a Concourse pipeline? In my PR pipeline I had been creating the image and testing it before promoting it to DockerHub.

Noticed an issue with my PR in showing AWS errors that ought to be fixed first. Haven't gotten back to that yet.