You've already forked pgbackrest
mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2026-06-18 00:57:09 +02:00
David Steele
69 lines
7.4 KiB
XML
69 lines
7.4 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE doc SYSTEM "doc.dtd">
|
|
<doc title="{[project]}" subtitle="News" toc="n">
|
|
<description>News</description>
|
|
|
|
<!-- ======================================================================================================================= -->
|
|
<section id="will-continue">
|
|
<title><backrest/> Will Continue!</title>
|
|
|
|
<p><b>May 18, 2026</b></p>
|
|
|
|
<p>I am pleased to announce that <backrest/> will continue! Over the last few weeks, a coalition of sponsors has come together to fund ongoing development. Their support means the project is no longer reliant on a single sponsor, giving <backrest/> the stability it needs for the long term.</p>
|
|
|
|
<p>I'd like to thank each of our sponsors:</p>
|
|
|
|
<p><link url="https://aws.amazon.com">Amazon Web Services</link> provides on-demand cloud computing resources to individuals, companies, and governments. Access computing power, storage, databases, machine learning, and over 200 services, paying only for what you use. Built to grow with you, investing in the communities we share.</p>
|
|
|
|
<p><link url="https://supabase.com">Supabase</link>, a complete backend platform built on PostgreSQL, enables developers to build and scale applications quickly without managing infrastructure. It includes a Postgres database, user authentication, real-time subscriptions, file storage, edge functions, and serverless functions, all backed by an active open-source community.</p>
|
|
|
|
<p><link url="https://pgedge.com">pgEdge</link> is an enterprise-class open source Postgres platform for AI, high availability and more, with Agentic AI native tooling and DBA workbench, monitoring and incident response, flexible deployment, and zero downtime maintenance. It scales from a single node to active-active multi-master within the cloud, on-premises, or air-gapped environments.</p>
|
|
|
|
<p><link url="https://tigerdata.com">Tiger Data</link>, the creators of TimescaleDB, develops the open-source time-series database built on PostgreSQL and operates Tiger Cloud, a managed platform for time-series, analytics, and AI workloads. Both self-managed and cloud options enable organizations to capture, store, and analyze time-series data at scale, from edge to centralized cloud deployments.</p>
|
|
|
|
<p><link url="https://percona.com">Percona</link> is an open source database software, support, and services company focused on helping organizations maintain full control over their data infrastructure. They help businesses run MySQL, PostgreSQL, MongoDB, Valkey, and Redis securely and efficiently through freely available open source software, 24/7 expert support, and hands-on database expertise.</p>
|
|
|
|
<p><link url="https://eon.io">Eon.io</link> is an intelligent cloud infrastructure for backup, recovery, and data management, helps teams store and access backups more efficiently, making data accessible for analytics and AI workflows. It offers fast, granular recovery and significantly lower storage costs for Postgres and data-intensive workloads across all clouds, including recovery from accidental data loss and AI agent regressions.</p>
|
|
|
|
<p>These organizations rely on <backrest/> to provide reliable disaster recovery for their products and customers. Their investment reflects the critical role that <backrest/> plays in the PostgreSQL ecosystem, and their collective support ensures the project's long-term sustainability.</p>
|
|
|
|
<p>I'm looking forward to getting back to work. There are features and optimizations in the pipeline that I'm excited to share in upcoming releases. Thank you to our sponsors for making this possible, and thank you to the community for your patience and support during this transition.</p>
|
|
</section>
|
|
|
|
<!-- ======================================================================================================================= -->
|
|
<section id="maintenance-update">
|
|
<title>Maintenance Update</title>
|
|
|
|
<p><b>May 4, 2026</b></p>
|
|
|
|
<p>After I announced that I am no longer maintaining <backrest/> my inbox blew up. It took a while to sort through the messages &mdash; many of them were well wishes and thank-yous for my work over the years.</p>
|
|
|
|
<p>But a pattern soon emerged. It is clear that many <backrest/> users, especially those with <backrest/> users of their own to support, would prefer the project to continue with me as the primary maintainer. I would like nothing more, but after months of fundraising I had just decided it wasn't going to happen.</p>
|
|
|
|
<p>Now the situation has changed, and it appears all but certain that I will be able to secure enough funding to continue the project. This time <backrest/> will be funded by a coalition of sponsors so that a single acquisition will no longer affect my ability to continue work on the project. We should also be able to bring on another maintainer to distribute the workload and provide continuity in the future.</p>
|
|
|
|
<p>I know this has been a shock and there is a lot of uncertainty. Please be patient &mdash; the current version of <backrest/> works, and there are no critical outstanding bugs or security issues so there is no need to immediately fork the project.</p>
|
|
|
|
<p>I expect to make a more definitive announcement by the end of the week. Until then, please hold tight and know that we are actively working to revive <backrest/>.</p>
|
|
</section>
|
|
|
|
<!-- ======================================================================================================================= -->
|
|
<section id="no-longer-maintained">
|
|
<title><backrest/> Is No Longer Being Maintained</title>
|
|
|
|
<p><b>April 27, 2026</b></p>
|
|
|
|
<p>TL;DR: <backrest/> is no longer being maintained. If you fork <backrest/>, please select a new name for your project.</p>
|
|
|
|
<p>After a lot of thought, I have decided to stop working on <backrest/>. I did not come to this decision lightly. <backrest/> has been my passion project for the last thirteen years, and I was fortunate to have corporate sponsorship for much of this time, but there were also many late nights and weekends as I worked to make <backrest/> the project it is today, aided by numerous contributors. Every open-source developer knows exactly what I mean and how much of your life gets devoted to a special project.</p>
|
|
|
|
<p>Since Crunchy Data was sold, I have been maintaining <backrest/> and looking for a position that would allow me to continue the work, but so far I have not been successful. Likewise, my efforts to secure sponsorship have also fallen far short of what I need to make the project viable.</p>
|
|
|
|
<p>Like everyone else, I need to make a living, and the range of <backrest/>-related roles is very limited. I can now consider a wider variety of opportunities, but those will not leave me time to work on <backrest/>, which requires a fair amount of time for maintenance, bug fixes, PR reviews, answering issues, etc. That does not even include time to write new features, which is what I really love to do. Rather than do the work poorly and/or sporadically, I think it makes more sense to have a hard stop.</p>
|
|
|
|
<p>I imagine at some point <backrest/> will be forked, but that will be a new project with new maintainers, and they will need to build trust the same way we did.</p>
|
|
|
|
<p>Again, many thanks to all the <backrest/> contributors over the years. It was a pleasure working with you!</p>
|
|
</section>
|
|
</doc>
|