# An announcement from the Steering Council regarding the JIT project **URL:** \ **Category:** Core Development\ **Tags:** steering-council\ **Created:** [June 5, 2026, 12:56pm UTC](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638 "2026-06-05T12:56:17Z")\ **Posts on this page:** 1\ **Showing post:** 27
**Author:** ![ncoghlan](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ncoghlan/32/14266_2.png) [@ncoghlan](https://discuss.python.org/u/ncoghlan)\ **Post date:** [June 7, 2026, 1:02pm UTC](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638/27 "2026-06-07T13:02:23Z")
> [@corona10](#): > > To make the current situation clear from the SC’s perspective, especially for new volunteers: continuing any kind of activity in a forked repository is, of course, totally fine. The main case where I think a grace period may be warranted is any currently in flight PRs (especially those from external contributors). (I am assuming there are some open PRs, since that concern was raised above, but I haven’t specifically checked how many there are myself) Saying “no new PRs on this topic until a PEP is approved” is one thing, shifting the goal posts for already in progress changes is something else (it may even sometimes be an appropriate step to take, but having the main branch JIT include a few merged PRs that aren’t present in Python 3.15 isn’t going to meaningfully affect the PEP discussions, but abruptly halting pending PR reviews has an immediate negative effect on the contributor experience) --- _[View the full topic](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638)._