On 1/4/14 10:33 , "Paul Tarjan" <p...@fb.com> wrote: >>I can't answer this question. Still, I expect that HHVM will follow >>ABI changes very fast. Paul? >>Anyway, I think having a separate package and let users get knowledge >>of that doesn't mean HHVM can't use an embedded copy if it needs to. >>But it should be a separate package whenever it's possible. > >We pin HHVM to certain git hashes. If there is a folly change we need >(which is rare) we will update the hash of the git submodule. I don't know >the details of how folly does backwards compatibility but if the hashes we >have correspond to folly package version, then you could just pin our hhvm >versions to folly versions, right? > >+Jordan and Sara who know more about the folly process.
Folly doesn't have a version release process, actually. It's just continuous master branch development, no tagging, no branches. -Sara
