7 Questions for you!
We know your time is precious, so this year we thinned out our survey to comprise of only seven questions. The seventh question is just an open box, where we hope you can tell us anything that you might think is useful to help us improve Pulp.
Pulp is Leaving Freenode
This probably isn’t the first time you’re hearing that many FOSS communities have left Freenode IRC and moved elsewhere. Pulp is no different. We now consider Matrix our Primary channel for communication. If you’d like to hang out and chat with the Pulp community, you can do so on the following Matrix channels:
If you want to use IRC, you can find corresponding rooms on Libera.Chat that are bridged to our new Matrix rooms.
You can find an up-to-date list of our channels and their purpose on our Chat to us page.
After a recent Pulp Open Floor meeting, we decided to test the possibility of retiring our mailing lists. User feedback has suggested that the barrier of entry is high (you need to join the list to ask one question) and the mode of communication is outdated. We want to remove as many barriers of entry for users and contributors as possible. For these reasons, we are centralizing all of our discussions and meeting notes on a Community Github Discussions. We would love to know what you think about it! If it works out, we might decommission our mailing lists.
Move to GitHub Issues?
In a further effort to incorporate feedback from the Pulp community about our contribution process, we plan to migrate from our Pulp Redmine to GitHub Issues. We hope that with this move, we will reduce some of the overhead of contributing to Pulp. If you’d like to join in the discussion and share your experience, see Github Issues migration meeting.
Installing Pulp on Openshift
Fabricio has shared an end-to-end demo of how you can set up and deploy Pulp on Openshift. You can also find corresponding documentation for this process here. If you’re interested to see this in action, you can watch here:
If you’ve any questions or feedback, start a discussion.
5 reasons to host your container registry with Pulp
If you’re looking for a better way to manage your containers, check out this opensource.com article about how Pulp can help you take control of your container management!
3.13 contained several bugfixes and the ability to control how many repo versions are retained. You can watch a demo here, and read all about the release announcement.
The Pulpcore 3.14 release is scheduled for the end of June. You can find updates on releaste dates and progress here.
Pulp RPM 3.12.0
The main feature of this release is support for automatic publishing and distributing. As well as this, the Pulp RPM plugin now has support for synching Oracle ULN repositories using ULN remotes. You can set an instance wide ULN server base URL using the
Earlier in the month, 3.11 was released and included support for the new changes in modularity (
static_context), as well as some important bug fixes, such as a fix that was causing high memory consumption during syncs of large repositories. An update, 3.11.1, came later in the month and provided additional bugfixes. For more information, see the changelog.
Pulp Debian 2.13.0
Pulp Debian 2.13.0 was primarily a compatibility release for Pulpcore 3.13 and for the future Pulpcore 3.14 release. 2.13.0 also contains some bug fixes. For more information, see the changelog.
This month, translation file synchronization was disabled from the Debian plugin. The feature was incomplete and the cause of various sync failures This update was ported to and released in the following versions: 2.9.2, 2.10.2, 2.11.2, and 2.12.1.
Translation file synchronization may be reintroduced in the future.
Pulp Python 3.3.0
Pulp Container 2.6.0
The 2.6.0 release adds support for adding a default remote to a repository for syncing, as well as a slew of bug fixes. For more information, see the changlog.