Would it be possible to get Fix master startup on Windows by stevenyoungs · Pull Request #2201 · gramps-project/gramps merged as soon as it hits 3 weeks? master is currently broken on Windows which is annoying for me; I have to keep this commit in every branch I work on and then remember to not commit it
Is there any consideration of doing a 6.2 sooner and a 6.3 (7.0?) with FamilySearch support?
I’ll have a look at merging it early.
The plan is to release v6.1 in October. My main focus is with the FamilySearch integration at the moment. Our goal has been to meet the FamilySearch certification requirements and become a solution provider. By working closely together, and with the hard work of @SourceAirbender, I think that we are almost there. We still have the deployment details to discuss and the contractual side to finalise.
The pull request is of course open for review like any other. We would welcome any feedback.
Two questions:
Thanks!
Sorry for talking to myself, but: making it an addon would also allow to quickly resolve bugs without needing a Gramps release. This might be quite useful for compliance reasons etc.
The key word is “integration”. The goal was to produce a FamilySearch compatible Gramps rather than third-party addon functionality. I can see the FamilySearch library in core Gramps being used in addons in the future.
The FamilySearch integration doesn’t dictate the release schedule. The plan is still to release v6.1 in early October (possibly over the weekend of 3rd/4th Oct).
However, the FamilySearch integration is nearing completion and I may need to release a version for compatibility and compliance reasons shortly. This will probably be called v6.1 and we will rename v6.1 to v6.2.
In a meeting yesterday, FamilySearch agreed to issue us with an API key to their production system. I’ll keep everyone updated with the progress when I can. Expect an announcement shortly.
I’ll update the roadmaps.
So, there will not be any MAin- /Sub- Events or Events on places in Gramps ever, since those things is not compatible with FamilySearch and lineage-linked research?
No. The FamilySearch integration doesn’t prevent us from making enhancements like this.
I like the Main/Sub events idea and would approve it for v6.2 if someone can code it before 1 Aug 2026. However, the events on places idea needs more discussion.
WikiContributors have been putting off some wiki article work on Place subjects because the GEPS 045 was announced as a 5.2 target. (The GEPS summary still has it as “in progress” for that release.) And the detailed GEPS implied that such wiki work would have to be redone.
Is GEPS 045 actually stalled? Can it be tabled in the Roadmap?
Yes, it is stalled.
Large parts of it could be implemented, but we need to open up the discussion about events on places and place types again.
I looked at and ‘tested’ the proposed changes. I put together an event on a place record and it seemed to work. But I never understood how to apply it to a person’s record.
Likewise, place record types changing based upon a date?!? Sure, the date of an event but when would that be seen or come into play?
These two changes were probably advocated by users doing ‘place studies’. But if implemented, what happens with the information would take more work to produce ‘results’.
What I saw in my test had events on places and dates added to types. I suppose they could be considered done. Those that requested these changes would then need to take the next steps by producing the reports to make use of the information
I see the roadmap now says:
The primary purpose of this release is for FamilySearch Integration compatibility and compliance. Most goals will move to v6.2.
There are bug fixes + small enhancements that have significant impact on performance that should be address in 6.1. These are small PRs and easy to review. What is happening?
All we are doing is fitting in an extra release for the FamilySearch Integration. This is not much more than v6.0 with the FamilySearch Integration pull request merged.
The new v6.2 is planned to be released on the original release date for v6.1 which is early October (probably the weekend of 3rd/4th).
Can you push in the Multiple named Dashboards PR2215 and the Welcome to Gramps! markdown-based gramplet into that 6.1 release too? Getting a few months of field testing by actual newbies will tell us a lot about what needs to be tweaked for the 6.2 release in October.
It is not often that Gramps has Enhancement Releases scheduled so closely to one another. We should take advantage of the opportunity.
I’ll consider some small bug fixes and enhancements, but remember this is not a normal release and possibly may never progress past the beta.
If you are looking for things for a betatest, please considered these two:
Both of these open up addons that could be developed and tested outside of core gramps. The second one can also have an huge performance impact on gramps-web and that would give us time to develop that in preparation for 6.2.
There are two PRs with schema changes:
https://github.com/gramps-project/gramps/pulls?q=is%3Apr+is%3Aopen+label%3A"schema+change"+
We might consider doing those in one upgrade step, rather than two. So that would suggest including:
In the next release.
and we multiple AIO improvements, including variants of a .gitignore change in 3 different PRs
(and that’s before me doing two different PRs to add type hints to db code 
)
I’ve fixed the O(N**2) → O(N) filter bug twice in two different ways.
@Nick-Hall the roadmap still doesn’t contain anything useful and my request below is still relevant.
In particular, is this
still the plan? So, no further maintenance releases ad then a final release in October?
That’s all fine for me but it would be good to have a reference point in the Wiki. When we switched to 6.0, there was an unfortunate delay in updating Gramps Web that confused users and I’d like to avoid that this time, especially given that our user base has grown significantly.
Thanks!
Yes, but v6.1 is now v6.2. There will be maintenance releases on the gramps61 branch.