[GH-ISSUE #791] 🔨 Quality Assurance Testing Needed #663

Open
opened 2026-02-28 01:26:27 +03:00 by kerem · 4 comments
Owner

Originally created by @tablatronix on GitHub (Dec 20, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/791

If anyone wants to help out with development release, Please QA it, and target any issues labelled QA thanks.

This will help test things that I cannot , or have not yet, and let me close issues and mark releases faster

https://github.com/tzapu/WiFiManager/issues?q=is%3Aopen+is%3Aissue+label%3AQA

Originally created by @tablatronix on GitHub (Dec 20, 2018). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/791 If anyone wants to help out with development release, Please QA it, and target any issues labelled QA thanks. This will help test things that I cannot , or have not yet, and let me close issues and mark releases faster https://github.com/tzapu/WiFiManager/issues?q=is%3Aopen+is%3Aissue+label%3AQA
Author
Owner

@dontsovcmc commented on GitHub (Mar 31, 2019):

Please, add info about debugging WiFiManager, ESPCore and so on.
What defines we should write and etc..

<!-- gh-comment-id:478389048 --> @dontsovcmc commented on GitHub (Mar 31, 2019): Please, add info about debugging WiFiManager, ESPCore and so on. What defines we should write and etc..
Author
Owner

@dontsovcmc commented on GitHub (Aug 30, 2019):

I can't imagine how huge errors and tickets are opened for WifiManager....
I think the most important think - to make release. But it's impossible with a lot of changes.
There is hard to understand bug versioning with unnamed 'development' branch...

Maybe we can separate issues by:

  • critical bugs, need help bugs
  • refactors
  • soft features
  • big features

Choose issues for next release and fix them.
What do you think about it?

<!-- gh-comment-id:526638980 --> @dontsovcmc commented on GitHub (Aug 30, 2019): I can't imagine how huge errors and tickets are opened for WifiManager.... I think the most important think - to make release. But it's impossible with a lot of changes. There is hard to understand bug versioning with unnamed 'development' branch... Maybe we can separate issues by: - critical bugs, need help bugs - refactors - soft features - big features Choose issues for next release and fix them. What do you think about it?
Author
Owner

@tablatronix commented on GitHub (Aug 30, 2019):

development is practically a complete refactor, it will be a major release, v1 or 2

<!-- gh-comment-id:526646727 --> @tablatronix commented on GitHub (Aug 30, 2019): development is practically a complete refactor, it will be a major release, v1 or 2
Author
Owner

@tablatronix commented on GitHub (Aug 30, 2019):

an overview of all changes is documented, and all code is commented.

https://github.com/tzapu/WiFiManager/issues/500

<!-- gh-comment-id:526647204 --> @tablatronix commented on GitHub (Aug 30, 2019): an overview of all changes is documented, and all code is commented. https://github.com/tzapu/WiFiManager/issues/500
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/WiFiManager#663
No description provided.