You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with @thestr4ng3r on Mattermost, it would be beneficial to have a more-or-less clear roadmap to 1.0.0.
From the blog it can be learned that the Projects feature is a high priority that should be stable when reaching 1.0.0. On the other hand, there is broken functionality (#45, #334, #400, #579, #617, #619, #678, and #679), as well as the newshell changes, and code refactor + testing, plus some other major syntax rework.
Currently the milestones seem a bit arbitrary (0.1.1 is the next release, but then there's a jump to 0.2.0?) and don't allow getting an idea of the progress nor time for their completion.
Because of this, I propose discussing here (in the most friendly way possible) what are the true next priorities in order to start creating more consistent (and shorter) milestones that allow a faster release cycle.
Now, let's place (for example) 6 "features" in the 0.2.0 milestone, another 6 "features" in 0.3.0, and then let's create the 0.1.2 with just 3 "bugs", 0.1.3 with 3 "refactor" issues, etc until there's the feeling that the code coverage and overall APIs are ready for to build over them (thus moving to 0.2.0 and feature development).
Then, for each milestone, a separate discussion could be created to learn better about the specific challenges instead of having to search in a very big thread.
So, what are the true next 3 priorities that should have been solved yesterday? 🙂
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As discussed with @thestr4ng3r on Mattermost, it would be beneficial to have a more-or-less clear roadmap to 1.0.0.
From the blog it can be learned that the Projects feature is a high priority that should be stable when reaching 1.0.0. On the other hand, there is broken functionality (#45, #334, #400, #579, #617, #619, #678, and #679), as well as the newshell changes, and code refactor + testing, plus some other major syntax rework.
Currently the milestones seem a bit arbitrary (0.1.1 is the next release, but then there's a jump to 0.2.0?) and don't allow getting an idea of the progress nor time for their completion.
Because of this, I propose discussing here (in the most friendly way possible) what are the true next priorities in order to start creating more consistent (and shorter) milestones that allow a faster release cycle.
Now, let's place (for example) 6 "features" in the 0.2.0 milestone, another 6 "features" in 0.3.0, and then let's create the 0.1.2 with just 3 "bugs", 0.1.3 with 3 "refactor" issues, etc until there's the feeling that the code coverage and overall APIs are ready for to build over them (thus moving to 0.2.0 and feature development).
Then, for each milestone, a separate discussion could be created to learn better about the specific challenges instead of having to search in a very big thread.
So, what are the true next 3 priorities that should have been solved yesterday? 🙂
Beta Was this translation helpful? Give feedback.
All reactions