# Release process is blocked

**URL:** <https://gramps.discourse.group/t/release-process-is-blocked/9822>\
**Category:** Development\
**Created:** [August 9, 2026, 1:34am UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822 "2026-08-09T01:34:44Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![dsblank](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/dsblank/32/3649_2.png) [@dsblank](https://gramps.discourse.group/u/dsblank)\
**Post date:** [August 9, 2026, 1:34am UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/1 "2026-08-09T01:34:44Z")

</div>

We have 76 bug fixes slated for Gramps 6.1. Regardless of what the FamiliySearch status is, we should proceed normally: merging bugs, and releasing release-candidates:

> **[gramps-project/gramps](https://github.com/gramps-project/gramps/milestone/3)**
>
> Source code for Gramps Genealogical program. Contribute to gramps-project/gramps development by creating an account on GitHub.

The FS integration seems to have put a major hurdle in our normal process, where I don’t think it needs to. We are going to really have to adjust our process to meet an October release goal for Gramps 6.2.

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [August 9, 2026, 10:20am UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/2 "2026-08-09T10:20:36Z")

</div>

I am extremely disappointed with the lack of progress with the FamilySearch integration. I have requested that @SourceAirbender be given admin access to our web server. However, since the project is run by volunteers, I can’t really put any pressure on people and I’m unwilling to do the job myself at this time.

Instead of taking on more work myself, I will look at the 76 outstanding bug fixes. I’ll probably just either approve or reject them and let others do the work of testing and merging.

Version 6.1 was always intended as an extra release that we needed for the FamilySearch integration. I did mention at the beginning that it may never make it past the beta stage. If we do decide to continue with v6.1, then it may be sensible to delay v6.2 for a couple of months.

---

<div class="post-metadata">

**Author:** ![SourceAirbender](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/sourceairbender/32/8555_2.png) [@SourceAirbender](https://gramps.discourse.group/u/SourceAirbender)\
**Post date:** [August 9, 2026, 1:39pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/3 "2026-08-09T13:39:18Z")

</div>

I’m surprised as well. This middleware has been done since April, all we need is one of the GRAMPS web admins to install it, and I’m happy to do it myself but someone needs to give me access to do that. All that’s left is to install the already working middleware and have our meeting with Gordon. We’re basically already finished.  
@Nick-Hall Maybe I could purchase a server to have it exclusively serve as the foundation’s middleware for now while we wait? You’d have to email Gordon and ask him to change the callback URL for the foundation’s Beta Key, though. I don’t mind the incurred cost for a few months. What are your thoughts?

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [August 9, 2026, 3:33pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/4 "2026-08-09T15:33:57Z")

</div>

@Nick-Hall and @gramps-project

The main server hosting that the [Gramps-project.org](http://Gramps-project.org) uses for WordPress, MediaWiki, MantisBT, and Sphinx community service is already frequently hit by [**DDoS** attacks that Cloudflare](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) blocks.

Will the traffic to this middleware aggravate that frequency? Would it be a good idea to contract separate hardware (domain? dedicated IP? SSL certificate?) with our hosting for it?

(Maybe we could use such separate hosting to put up a **Gramps Web** instance where a shared `example.gramps` could evolve. @DavidMStraub would that have multiple uses?)

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [August 9, 2026, 3:43pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/5 "2026-08-09T15:43:59Z")

</div>

> [@SourceAirbender](#):
>
> Maybe I could purchase a server to have it exclusively serve as the foundation’s middleware for now while we wait?

I have tried to gain access to our web server using some account details that @bmatherly gave me. Unfortunately, they do not work.

If we cannot gain access then setting up a new server is our only option. It is not a bad idea anyway.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [August 9, 2026, 7:45pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/6 "2026-08-09T19:45:00Z")

</div>

7 posts were split to a new topic: [Hosting options for a collaborative example.tree](https://gramps.discourse.group/t/hosting-options-for-a-collaborative-example-tree/9825)

---

<div class="post-metadata">

**Author:** ![SourceAirbender](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/sourceairbender/32/8555_2.png) [@SourceAirbender](https://gramps.discourse.group/u/SourceAirbender)\
**Post date:** [August 17, 2026, 2:45am UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/7 "2026-08-17T02:45:41Z")

</div>

Just finished setting up the foundation middleware. Now we just need to ask Gordon to setup the redirect for the FS oauth

---

<div class="post-metadata">

**Author:** ![DaveSch](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davesch/32/40_2.png) [@DaveSch](https://gramps.discourse.group/u/DaveSch)\
**Post date:** [August 24, 2026, 1:24pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/8 "2026-08-24T13:24:13Z")

</div>

Any progress? It is hard to test new features without access.

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [August 24, 2026, 1:29pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/9 "2026-08-24T13:29:16Z")

</div>

The Windows AIO [build](https://github.com/gramps-project/gramps/actions/runs/32670650282) is failing. Perhaps one of our Windows experts would look at it for us.

---

<div class="post-metadata">

**Author:** ![dsblank](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/dsblank/32/3649_2.png) [@dsblank](https://gramps.discourse.group/u/dsblank)\
**Post date:** [August 24, 2026, 1:44pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/10 "2026-08-24T13:44:31Z")

</div>

I’m creating a fix: [Make maclocale\_test independent of the host locale module by dsblank · Pull Request #2505 · gramps-project/gramps · GitHub](https://github.com/gramps-project/gramps/pull/2505)

It is basically just a bad test (testing a windows locale in a mac environment). Should be ready for review shortly.

---

<div class="post-metadata">

**Author:** ![dsblank](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/dsblank/32/3649_2.png) [@dsblank](https://gramps.discourse.group/u/dsblank)\
**Post date:** [August 24, 2026, 2:01pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/11 "2026-08-24T14:01:44Z")

</div>

Tests now passing 🎉 🎉

---

<div class="post-metadata">

**Author:** ![Woody](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/woody/32/3406_2.png) [@Woody](https://gramps.discourse.group/u/Woody)\
**Post date:** [August 28, 2026, 5:21am UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/12 "2026-08-28T05:21:37Z")

</div>

Is there anything new to report?

When is it happening?

This is more exciting than a crime movie…

---

<div class="post-metadata">

**Author:** ![SourceAirbender](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/sourceairbender/32/8555_2.png) [@SourceAirbender](https://gramps.discourse.group/u/SourceAirbender)\
**Post date:** [August 28, 2026, 2:15pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/13 "2026-08-28T14:15:18Z")

</div>

Just finished the meeting with the FamilySearch Rep and we’re good to go to start Beta access on their end. Whenever @Nick-Hall decides to start we can do the access request roll out

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [September 12, 2026, 12:49pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/14 "2026-09-12T12:49:31Z")

</div>

Ok. The middleware server is established, FamilySearch has given us a “go”.

What is the next roadblock to getting 6.1 beta2 released?

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [September 12, 2026, 2:42pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/15 "2026-09-12T14:42:28Z")

</div>

I’ll look at releasing _beta2_ today.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [September 12, 2026, 2:44pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/16 "2026-09-12T14:44:16Z")

</div>

That is the best news I have heard in months! Thank you @Nick-Hall

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [September 13, 2026, 10:50am UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/17 "2026-09-13T10:50:34Z")

</div>

Thanks to @Nick-Hall , @SourceAirbender and @clarkegj for the extra effort to overcome the stall in releases.

This one put up a fight, resisting being pre-released.

Well done and welcome to Gramps 6.1Beta2

---

<div class="post-metadata">

**Author:** ![Woody](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/woody/32/3406_2.png) [@Woody](https://gramps.discourse.group/u/Woody)\
**Post date:** [September 13, 2026, 1:38pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/18 "2026-09-13T13:38:12Z")

</div>

Many thanks to all the creators.

Here is the download link

> **[Releases · gramps-project/gramps](https://github.com/gramps-project/gramps/releases)**
>
> Source code for Gramps Genealogical program. Contribute to gramps-project/gramps development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\
**Post date:** [October 13, 2026, 1:38pm UTC](https://gramps.discourse.group/t/release-process-is-blocked/9822/19 "2026-10-13T13:38:17Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
