Release planning: v0.5.0, v0.6.0, v0.7.0 and beyond #2335
myitcv
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have just released v0.5.0 and v0.6.0-alpha.1.
v0.5.0 comes almost a year after v0.4.3, and v0.6.0-alpha.1 is being released at the same time as v0.5.0.
This might leave you wondering, "What on earth is happening?!" and "Can we expect a more regular release cycle?"
This discussion aims to explain where we find ourselves today, share details of future release plans, and answer some frequently asked questions.
For more details on the CUE project's current areas of our focus, please see the 2023-04-12 Community Call, which will include a video recording.
Release plan
letfields.Release calendar
To provide some visibility on likely release cadence, we are aiming to publish two feature release per year. Ideally one every six months, although this might differ slightly depending on the size of each release. We will provide regular updates on current status at each community call.
Improving release quality and cadence: Unity
We are very grateful to everyone who helped with the testing of the v0.5.0 pre releases. A large number of you diligently and carefully reported issues in the issue tracker and on Slack. Thank you!
The challenge with any software project is that you can never be sure when you are "done" with finding bugs in a release candidate. Not only that, it's hard to have real confidence in a release candidate without positive verification that nothing has broken (at least according to a set of evaluations or test cases).
CUE is not immune to these challenges.
As we have previously discussed, we are addressing this challenge via
unity, our regression and performance testing setup.unityis used to ensure that a project's CUE evaluations do not unexpectedly stop working, or regress in terms of performance.unitycontinues to catch multiple issues with each release. Adding your project tounitynot only guarantees that we will not break your tests (if we do, we will work with you to fix your CUE code), but it also helps to improve the quality of each CUE release.unitywill become increasingly important as we move to work on v0.7.0. Indeed, ensuring your code is inunitywill help us to prioritize and target performance improvements based on the most obvious "hotspots" in the corpus.We are currently in the process of releasing Unity as a GitHub App on the public Marketplace. Sign up to receive updates; we will be in touch as soon as the GitHub App is ready.
Frequently asked questions
If your questions/concern is not addressed above or in the FAQs that follow, please reply to the discussion and we will update this headline description.
Q1: v0.5.0 does not work for me - what can I do?
Firstly, please make sure there is an issue that accurately captures the problem you are experiencing, and that we have accurately labelled the issue to indicate it did not get fixed in v0.5.0.
Secondly, apologies for not getting to all of the bugs/issues for v0.5.0. We had to draw a line somewhere. Some of the bugs identified in the later pre-releases were proving hard to fix with the evaluator architecture of v0.5.0. v0.7.0 addresses these structural problem, making many of the fixes much easier, and some of them even trivial. In addition, these changes in v0.7.0 are key building blocks for performance improvements that will benefit the entire CUE community. We therefore took a judgement call on switching our efforts to v0.7.0.
Q2: When can I expect to be able to try the initial WebAssembly (WASM) support?
We are targeting v0.6.0-alpha.2 for a release of initial support with a C ABI. Details will follow in the release notes. Please subscribe to #2035 for updates.
Q3: What version will include an initial implementation of the modules proposal?
We are targeting v0.6.0-alpha.3 for the first modules implementation. See the recently published modules and package management proposal v2 for more details, and subscribe to #2032 for future updates.
Q4: What will happen to issues that were previously part of the v0.5.0 milestone?
Now that v0.5.0 has been released we will reassign issues previously attached to the v0.5.0 milestone to future releases. We will clearly label those issues that we could not address as part of v0.5.0, so that they are a priority within either v0.6.0 or v0.7.0.
Q5: When is feature request ABC or bug DEF going to be implemented?
The CUE project uses GitHub issues for its issue tracker. Milestones group issues, and are used to plan what features/bugs will be implemented/fixed when. Milestones correspond to upcoming releases, identified by the version number. Labels are used to categorize feature requests and bugs for easier search and classification. The "Triage" label is automatically added to new issues to help the project maintainers identify which issues require an initial look and triage.
With the epic that is v0.5.0 behind us, we can start the process of tidying up issues. This will involve updating the milestone of some issues. Issues that were previously marked as v0.5.0 or v0.5.x will be reassigned to a later release.
To answer "when will feature ABC be implemented?" or "when will bug DEF be fixed?" we first need to be clear that the feature request/bug is accurately captured in an issue. Has a project maintainer replied to your issue? Has the "Triage" label been removed? To be certain that an issue will be addressed, it must be assigned to a milestone. If an issue you are interested in does not have a milestone, please comment on the issue to request its prioritization. Better still, encourage others who are also interested in the issue to upvote your request using emoji to show support.
Feedback
Please use this discussion to bring up anything you would like relating to the CUE project, especially release planning.
Beta Was this translation helpful? Give feedback.
All reactions