Hi Everyone, In the first quarter of 2017, we plan to release Packer 1.0. The 1.0 release can be thought of as a long term support release. Its feature-set will be remain stable, and we'll continue to fix bugs on those features. Major new features will come after 1.0.
Packer 1.0 will free us up to think about Packer 2.0, which may have a different architecture than 1.0. Nothing is set in stone yet, but we want to give ourselves room to potentially break backwards compatibility. In preparation for 1.0, we'll be going through the packer issue list, closing issues that we don't think will make it in to 1.0. We'll label them with "wontfix" and "pre-1.0". That way, they won't be lost to time. To be clear, if we close an issue, it's not because we don't think it's a good idea, or that it's not worth fixing, it's just that we won't be working on it for 1.0, and we'd still be very happy to receive PRs for it. Thanks, --Matt Hooker -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAEpfdnwt_JNzwAbT%2BvaJnqjrw8KFp1F7vV3ZUeHM6Yiz748mTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
