Bug evaluation before release

[iamareebjamal]

It has been a lot of time since last release, so there should be a release before GSoC and then we follow fortnightly release pattern

So, calling all contributors to report any serious bug before 0.1.0a release

[anhanh11001]

In summary, I think here are the current major bugs in the app:

1. Bottom Navigation doesn't retain old fragments Bottom Navigation issues #1139. I can try to fix this issue this weekend.
2. The QR code of the tickets under an order is not distinguishable as we have discussed in the open-event-server #5701 .
3. Payment is still blocked now, Paypal is not integrated.
4. Other issues I think are small and mostly about the UI (some horizontal views doesn't look really good, ...)

Besides, can I ask what's fortnightly release pattern as i have googled it but didn't find any clear results

[iamareebjamal]

It just means we'll release every 2 weeks. 4 of those issues are not major bugs. Major bugs would constitute crashes and bugs which were not there in previous releases. 1 is major but due to Nav Component, so can be passed on for next release

[addiegupta]

I think Issue #1454 might count as a crash that should be fixed before release

[iamanbansal]

Please check #1453

[iamareebjamal]

And nevertheless won't be considered a critical bug unless it was a crash or hindered from basic functioning of app

[addiegupta]

@iamareebjamal #1474 please have a look at this issue

[addiegupta]

@iamareebjamal #1474 please have a look at this issue

And #1475 too

[angmas1]

@addiegupta these crashes weren't happening two days back, there has been some recent change which may be causing these crashes.

[somenath1435]

No crashes were there yesterday

[angmas1]

Now, it's crashing on searchfragment as well.

[iamanbansal]

Could be shared element transition.

[addiegupta]

On selecting favoritefragment, EventsFragment is also being created. And on selecting eventsfragment, it is being created twice

[addiegupta]

Could be shared element transition.

I think so too.

#1443 introduced these crashes for sure I just checked

[somenath1435]

I think our priority should be to fix the crash issue as soon as possible