[GH-ISSUE #420] Branch develop #353

Open
opened 2026-02-28 01:24:54 +03:00 by kerem · 5 comments
Owner

Originally created by @tablatronix on GitHub (Sep 13, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/420

@tzapu what versioning do you think we should use for this release ?
Do we want to stay pre v1, esp8266 core is still a little unstable, 3.4.0 should be alot more so.

Let me know your thoughts, and ill update the milestones and future releases

Originally created by @tablatronix on GitHub (Sep 13, 2017). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/420 @tzapu what versioning do you think we should use for this release ? Do we want to stay pre v1, esp8266 core is still a little unstable, 3.4.0 should be alot more so. Let me know your thoughts, and ill update the milestones and future releases
Author
Owner

@tzapu commented on GitHub (Sep 14, 2017):

Hi Shawn, it looks like you will include a massive amount of things in the next release.
I guess it merits a new major version number as well if you think that's right
Whatever you think is best i'm ok with with the mention that if there are breaking changes, it really SHOULD be a major version change

<!-- gh-comment-id:329385510 --> @tzapu commented on GitHub (Sep 14, 2017): Hi Shawn, it looks like you will include a massive amount of things in the next release. I guess it merits a new major version number as well if you think that's right Whatever you think is best i'm ok with with the mention that if there are breaking changes, it really SHOULD be a major version change
Author
Owner

@dontsovcmc commented on GitHub (Nov 5, 2019):

There are huge number of features on development branch, but there is no release =(. I think, the main goal - to make main features without any customizations.

Priority:

  • handlers, core optimizations
  • new libraries support

Not needed for everybody:

  • a lot of customizations (styles)
  • ESP32 support (this is a second step)

I think the most users can't undersand what 'persist' means in you docs.., but this option has a lot of source code in the library.

For myself: no release - no pull requests =(.

<!-- gh-comment-id:549917124 --> @dontsovcmc commented on GitHub (Nov 5, 2019): There are huge number of features on development branch, but there is no release =(. I think, the main goal - to make main features without any customizations. Priority: - handlers, core optimizations - new libraries support Not needed for everybody: - a lot of customizations (styles) - ESP32 support (this is a second step) I think the most users can't undersand what 'persist' means in you docs.., but this option has a lot of source code in the library. For myself: no release - no pull requests =(.
Author
Owner

@tablatronix commented on GitHub (Nov 5, 2019):

The docs need to be written before I release it, I will release an alpha version to get people started and volunteering.

what do you mean no pull request?

<!-- gh-comment-id:549967802 --> @tablatronix commented on GitHub (Nov 5, 2019): The docs need to be written before I release it, I will release an alpha version to get people started and volunteering. what do you mean no pull request?
Author
Owner

@dontsovcmc commented on GitHub (Nov 5, 2019):

what do you mean no pull request?

I mean refactoring. It's difficult, cause no releases on dev branch

<!-- gh-comment-id:549989200 --> @dontsovcmc commented on GitHub (Nov 5, 2019): > what do you mean no pull request? I mean refactoring. It's difficult, cause no releases on dev branch
Author
Owner

@tablatronix commented on GitHub (Nov 5, 2019):

what refactoring ?

<!-- gh-comment-id:550024668 --> @tablatronix commented on GitHub (Nov 5, 2019): what refactoring ?
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#353
No description provided.