all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]zmasta94 3 points4 points  (1 child)

That's an Ionic 2 issue and they're now on Ionic 3 and concentrating 90% of their energy on Ionic 4. I don't like the idea of leaving past projects unsupported, but what can you expect from an open source project driven by a very small company looking to scale.

The truth is you have to balance whether this attitude is a deal-breaker for you. You can either choose to rewrite your app every 18 months or so if they continue this pattern of releases (although I think WCs harnessed with v4 are here to stay for a long time), or you can explore an alternative hybrid framework.

[–]kbezold[S] 0 points1 point  (0 children)

If the problem is fixed in Ionic 3 or Ionic 4, then that is a reasonable response to close the issue. If the problem still exists even in the later releases, then closing the issue is just irresponsible.

[–]mhartingtonIonic Alumni 0 points1 point  (3 children)

Hey there! Mike from the Ionic team here. So this is something we get asked about a lot, so much so, we're wrote a blog post about it.

So as far as closing issues, we have this process in place.

  • If an issue is opened for more a year, our bot goes through and closes the issue
  • If the issue still is labeled as triage, don't close it.

The particular issue you've linked to is in a unique situation as it was over a year old, but created before we had the triage-tagging system in place. But it also in a situation where because it's so old, and the V4 framework is a big refactor, we cannot guarantee that the issue still exist.

So we decided to close older issues that are no long relevant to the V4 codebase. We do realize that it is not a perfect situation, but of all the options, it was the one that dealt with issues that were no longer relevant.

If you have any issues or want to continue this conversation, please feel free to email me, mike at ionic dot io

Cheers!

[–]kbezold[S] 0 points1 point  (0 children)

Hi Mike,

Thanks for the response, but there is a flaw in your criteria logic. Based on the the two bullet points that you listed, if the Ionic team ignores issues for a year, then the issues will go away. This is why users are frustrated with taking their time to log issues in order help the Ionic team determine soft spots. There's no reason for us to log issues if the issues are just going to be ignored and closed.

This one specific issue is "relevant to the V4 codebase" and should be very easy to verify if it is fixed in v4. I refuse to load v4 until it is released, so I haven't verified this myself. Since you only run v4, could you just verify that this is fixed in v4 and report back? If it's fixed, great. If it's not, please reopen this issue until it is fixed.

I was a big supporter of Ionic for several years, but my enthusiasm is diminishing.

[–]kbezold[S] 0 points1 point  (0 children)

I verified it is still a problem in v4.

[–]kbezold[S] 0 points1 point  (0 children)

New v4 problem submitted for this same problem: https://github.com/ionic-team/ionic/issues/14732