On Wed, Jan 27, 2016 at 02:12:52PM -0800, Junio C Hamano wrote: > More seriously, are we confident that the overall worktree support > is mature enough by now that once we add an experimental feature X > at version 1, we can promise to keep maintaining it forever at > version N for any positive integer N? I hate to sound overly > negative, but I am getting an impression that we are not quite > there, and it is still not ready for production use. The worktree feature has been used by several people already (me included), and do far the only issue which requires change in repository layout is the config separation. Isn't it enough to be confident? As I noted in another email, I would not expect to be N>2 soon. At least not more likely than incompatible change because of some other reason. And the support for an older version can be as little as one-time upgrade to the current N (preferably with confirmation from user). > It would be beneficial both for us and our users if we can keep our > hand untied for at least several more releases to allow us try > various random experimental features, fully intending to drop any of > them if the ideas do not pan out. Users definitely would not benefit if there is release feature with note "anything you do can be lost after you install next version of git" -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html