-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
August - September 2023 iteration plan #1618
Comments
Friendly reminder: the following appear as "Moved to next cycle" in the previous iteration plan but are not listed above:
|
As folks might have noticed, we're reaching the end of September already. The next release is currently scheduled to be around Oct 4th, give or take a couple of days. Main reason for the delay was that I was on vacation. There is some talks if we should move to a 6 weeks cycle, given that this matches what the v8 team is doing. I'm open to experiment with different models, although I like the monthly cadence as it's easier to remember for me. |
This cycle took a bit longer and I've moved the open tasks to the current one #1891 . My main takeaway this time is that I had too many projects running simultaneously in the last cycle. That lead to me being spread a bit too thin and whilst lots of thing progressed further, most of it needs a bit more work to bring over the finish line. |
@waldyrious yup, you're absolutely right. Not sure what happened there 😅 |
A new Fresh version is cut on a monthly basis around the middle of the month and this post intends to capture the main tasks we want to focus on. A monthly plan matches the release cycle and allows for more flexibility by making it easier to account for shifts in priorities.
The current list of tickets included in this release can always be found in the related GitHub milestone: https://github.com/denoland/fresh/milestone/4
Plan items
The current plan of main features planned for this cycle:
[to be done]
Note that this list is not set in stone. Random ideas occur spontaneously and the async route components in last release for example were only added later in the cycle based on an evening exploration I did.
The text was updated successfully, but these errors were encountered: