300 PRs

[daniluk4000]

Hey guys. I think this is a perfect place to ask this. I've been watching some issues for a while. If I didn't know I'm wrong I would say this repo is dead.

In PRs there are tons on fixes that await for approval and merge. Some PRs exists for like a year and vue team tells to "be patient".

I don't feel like I can do this but I would like to ask core team for some kind of deadline of they to start dealing with those PRs. Vue 3.3.0? Next minor release? Vue 4 (?) is in development so all those bug fixes will be irrelevant?

@znck @antfu I can see great activity from you guys in last weeks. Does this mean you have closest plans to reduce the number of PRs that are open and merge/close them? 300 seems to be very big number.

Talking with @yyx990803 in Twitter did help to merge one of PRs, but that's not the way to do this for all existing issues/PRs. Most of issues are important for someone and merging fixes would improve stability on framework greatly.

[yyx990803]

I appreciate your input and thank you for raising your concerns in a respectful manner. Let me put this into perspective.

Vue has close to 2 million users worldwide. We receive multiple new issues / PRs every single day. If you look at the number of PRs open vs. closed (as of now it's 274 vs. 2895), you'll see that we've processed more than 10 times of currently open ones. 300 PRs without context may seem like a lot, but please be aware of the sheer amount of incoming work we are dealing with. Every PR demands time to review, it's not as simple as clicking the merge button. Sometimes a PR may take hours or days to review, modify and merge.

Vue core is also not our only responsibility. Other team members have other repos / projects in the Vue ecosystem, and their day job that they need to spend time on.

Personally, I have to split time between short term maintenance of Vue 2 + Vue 3 + Vite, implementing new features, research and prototyping for long term directions (vapor mode), community management, and taking care of two young-aged kids. To avoid context switching I have to do focus periods, for example focusing on Vite or research for a month. There are also life events that sometimes force me to take time off from work entirely. During such periods some repos may not receive much attention or activity, but that doesn't mean it's "dead".

One downside of this is sometimes issues / PRs filed during those period may slip through and left hanging for a very long time. This is definitely something we could and should improve. In fact I am working on combing through the long standing PRs / issues right now and plan to do a focus period to cut down open issue / PR count.

[daniluk4000]

Thank you. Never said it's dead thought, I said I know I'm wrong in this feeling.

I appreciate your time spent writting this response. I have much respect to Vue team and I love this framework, this is why I started this discussion in first place. Thanks for explaining current situation and what you and team deal with. It becomes more clear now.

Focus period seems like a great idea! Looking forward to see more fixes ride it's way to merge, latest releases are also great and contain many fixes and merged PRs.

Again, thank you and best luck.

[martinszeltins]

@yyx990803 Happy to hear that Vue 3 will get more attention in 2023. I am also waiting on a bug fix where HMR does not work - #7234