This is a small update to the LuaJIT roadmap for 2012/2013: //www.freelists.org/post/luajit/LuaJIT-Roadmap-20122013 Update Rationale ---------------- The original release plan was to make the new garbage collector the main feature of LuaJIT 2.1. A major change such as this will inevitably cause some instabilities in the code base. It might take a long time to get it back into good shape, possibly a year or longer. OTOH LuaJIT 2.0 is definitely frozen (no new features) to comply with general versioning practice and distro requirements. Alas, that would put an effective halt on the development of new features that are independent of the new garbage collector. Some changes, like a port to a new architecture really need to start with a stable code base, i.e. LuaJIT 2.0. But such a port could not be merged into 2.0, since it's really a new feature. There are quite a few features in the queue that would have to be put in limbo, without a good place to merge them. To solve this dilemma, I'm proposing a change of the release plan. New Release Plan ---------------- LuaJIT 2.0 -- Stable branch - First 2.0.0 release candidate end of October 2012 (next week). - Bug fixes only. - Existing git repository will continue. - Dot release tarballs whenever appropriate (2.0.1, 2.0.2, ...). LuaJIT 2.1 -- Development branch - New features that do NOT depend on the new GC. - New ports. - Mostly evolutionary improvements, no radical changes. - Separate git repo will open in a couple weeks. - First tarball releases expected in 2013. LuaJIT 3.0 -- Experimental branch - Major code base cleanup. - New garbage collector. - New features that depend on the new GC. - Periodic merges from 2.1 branch. - Code may not be fully functional in the beginning -- YMMV. - Git repo will open in 2013, no tarballs for a while. Note: This doesn't change much with respect to the new GC. It won't be completed later or earlier -- it'll simply be tagged with a different version. You can substitute LuaJIT 3.0 for most that has been written in the past about LuaJIT 2.1. Feedback welcome! --Mike