4 ms·
Needless to say, we’re incredibly excited about this release. If you’re in a hurry, you can just skim; the bolded sentences and code samples are the important t
by tomdale 12y ago
Needless to say, we’re incredibly excited about this release. If you’re in a hurry, you can just skim; the bolded sentences and code samples are the important takeaways.
The reason this is so long is that we’re doing the 2.0 release through our community RFC process[1]. Change can be scary when you’ve made serious investment in an open source tool, so we want to provide as much detail as we can while leaving open the opportunity to incorporate feedback.
I’d like to thank the members of the Ember core team, who paid out of pocket to spend this past weekend with me in Chicago for the face-to-face meeting where we banged out all of these details. Maintaining an indie open source project can be painful at times, but I think history demonstrates there’s no better way to foster a project that is as aligned with the goals of its users as possible.[2]
[1]: https://github.com/emberjs/rfcs https://github.com/emberjs/rfcs
[2]: http://blog.endpoint.com/2010/01/state-of-postgres-project.html http://blog.endpoint.com/2010/01/state-of-postgres-project.h...
- inglor 12y agoThe RFC process sounds very nice but be careful. PHP has been doing it for a while now and while it's working out nicely for them in some regards - pretty much every php person I talked to involved with it hates 'internals' with a passion.
- tomdale 12y agoWe do development of new features behind feature flags, and have automated tools to help enable, disable and strip them. We're planning on moving to a model where we do an approximately annual "garbage collection" pass on the framework (corresponding with a major version bump) and simply nuke all of the code that has been deprecated since the last major version release.
- oblio 12y agoMaybe a process similar to Django's would be helpful? https://docs.djangoproject.com/en/dev/internals/release-process/ https://docs.djangoproject.com/en/dev/internals/release-proc...
- steveklabnik 12y agoFun fact: Python's PEP process influenced Rust's RFC process, which influenced Ember's.
- porker 12y agoThere is a long history behind the hating of 'internals' in PHP land. The RFC process has improved matters, but can't get rid of all the poison that already existed.
- deleted 12y ago[deleted]