-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse Server 6 release #8225
Comments
This comment was marked as resolved.
This comment was marked as resolved.
I've added your suggestions to the list above, except:
|
The feature section are just some suggestions for features we can aim to ship by Parse Server 6, not necessarily breaking. The problem with #7563 is that it will result in a lot of open PRs having huge merge conflicts, so internally breaking in a way. Maybe we can aim to close all PRs as complete or stale by V6, and do the overhaul of modernizing the codebase in V6.0.1, and then normal PRs can continue. |
Yes, #7563 is somewhat complex; we'd want to a void 1 huge PR so we'd try to section the code base and modernize section by section. This way we would also require only selected PRs to be merged. |
I haven't looked into #7979, it seems like a large effort. Given the other (required and planned) tasks we already have, it seems a bit much? I estimate that alone to take ~2-3 months getting done on the side. |
I guess the features are probably lower priority as they can always be shipped in Parse Server 6.0.1 |
Agree. What about #7527, could that be breaking / easier to implement as breaking? |
Yes, I think that is a good one. We can support it as a non-breaking change, but it's not really ideal to have 2 different startup methods, one that exposes routes before they are ready |
Added to "planned". |
#7440 should be considered IMO. I don’t see any PR’s open for any of the alternatives others discussed in the linked thread |
Added to "tbd". Seems to require further discussion and may affect Parse client SDKs? So maybe something we should take our time with and tackle in 2023, but that's definitely an important fix and improvement. |
I believe the update for redis should be considered #7987. It will be a breaking change (see migration guide, particularly the client configuration guide) unless someone provides a converter from the old-style config options to the new redis options. The version of redis the server supports was released 4/21 which is pretty old. |
Good one, added to "planned". |
@parse-community/server All required PRs (and a few of the optional PRs) for Parse Server 6 have been merged. Thanks everyone for their work. If there is no additional suggestion, we'll release Parse Server 6 with the commits on the alpha branch. |
Yep, I think we're ready to go! |
Presumed release date is Jan 30 or 31, since we're also consolidating the legal notes and that takes some time. At least we'll still be in Jan, so apart from skipping the beta phase we're on schedule. Nice! |
Closing, release published |
Parse Server 6
This is to prepare for Parse Server 6 release in Jan 2023.
Schedule
alpha
to create6.0.0-alpha
releasesalpha
branch until Parse Server 6.0 releasebeta
intorelease
to release last Parse Server 5 stable version before LTSalpha
intobeta
to release6.0.0-beta
beta
intorelease
to release6.0.0
Issues / PRs to merge in Nov 2022
The following items are required or reasonable to do before a major release, since they involve breaking changes or relate to obsolete features that should be dropped. The list does not consider features or bugs that are unrelated to the aforementioned aspects and can therefore be merged at any time, unrelated to a major release.
Required
DEPPS1
: Native MongoDB syntax in aggregation pipeline #8268DEPPS2
: Config option directAccess defaults to true #8269DEPPS3
: Config optionenforcePrivateUsers
defaults totrue
#8270DEPPS4
: Remove convenience method for http requestParse.Cloud.httpRequest
#8271verifyServerUrl
does not work with new startup methods #8380Optional (planned)
Date
type attributes are saved differently at different levels #7575masterKey
to localhost by default #8245Improve transparency of reset password flow #7434(not a braking change)fix: GraphIQL offline install #8153(not a braking change)LiveQuery fields does not work as expected #8027(not a breaking change)Optional (to be discussed)
package-lock.json
as v2 #8274Remove Node 14 support (EOL will be in Apr 2023)(we'll keep Node 14 until Parse Server 7 (2024))The text was updated successfully, but these errors were encountered: