With months of just bug fixing, without any new features, leading up to the LTS release. Most big frameworks that I've used choose their LTS versions very carefully to avoid having to do much work on them. There's no point in supporting an older version that might not be at a stage where it's worth making it an LTS version, if you get what I'm saying. If you are going to do it later on, then you should probably decide which versions you consider stable enough to actually maintain for a longer period. I think there shouldn't be too much effort being put into maintaining old versions right now. It would be cool to have a somewhat "regular" way to updates ourselfs on topics that need to be done and/or what we want to see in the future as features/improvements. What is the preferred way of communication? I am watching the issues here, the gitter channel and i think i am getting notified on the contributors team page here on github. I think the documentation could use some work, that could be something where i can start right now. I am still not very familiar with the codebase beyond the "entry level" Api surface. Said milestones could be a way but i don't know for sure. I would also want to see some milestones and or a rough way the project is going.
I think a good way to move forward could be to go over the current open issues and maybe try to categorize/label them. It is hard to see what actionable tasks are "laying around". To reiterate over the last attempt and repeat what my main problem was:
0 kommentar(er)
