For more information, please see the discourse links below.
pulp_file: https://discourse.pulpproject.org/t/pulp-file-1-10-0-is-ga/181
pulp-cli:
https://discourse.pulpproject.org/t/pulp-cli-0-12-0-is-generally-available/185
David
___
Pulp-dev mailing
Please visit discourse to propose/vote on/view potential sessions for
PulpCon 2021.
https://discourse.pulpproject.org/t/pulpcon-2021-call-for-proposals/134
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
Please join us today for Docs Day. More info:
https://discourse.pulpproject.org/t/join-us-for-docs-day-tomorrow/107
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev
More info:
https://discourse.pulpproject.org/t/pulp-file-1-9-1-is-generally-available/110
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev
I've taken down Github Discussions. It looks like Github stores the
Discussions though so I can still re-enable them temporarily if anyone
needs info, etc.
David
On Tue, Aug 24, 2021 at 2:44 PM David Davis wrote:
> AFAICT, there's no way to make discussions readonly so any discussi
For more information, check out the post on Discourse:
https://discourse.pulpproject.org/t/pulpcore-3-15-0-is-generally-available/101
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev
___
> From: pulp-dev-boun...@redhat.com on behalf
> of David Davis
> Sent: 23 August 2021 15:30
> To: Melanie Corr
> Cc: pulp-list; Pulp Development List
> Subject: Re: [Pulp-dev] [Pulp-list] Github Discussions
>
> If no one objects, I will be retiring
data to prove the increase in community engagement
>> after the move.
>>
>> Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley > >:
>>
>>> And Matrix integration.
>>> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integrati
I posted a discussion about a 3.14 release note that plugin writers should
be aware of when upgrading to pulpcore 3.15. Please check it out:
https://github.com/pulp/community/discussions/59
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
The container image is fixed now (thanks x9c4 and fao89).
There are a bunch of PRs to merge though to upgrade repos' CI files to
Python 3.8.
David
On Wed, Jul 14, 2021 at 7:02 PM David Davis wrote:
> Hi all,
>
> Today, I upgraded the pulp containers to Python 3.8 and it bro
Hi all,
Today, I upgraded the pulp containers to Python 3.8 and it broke the CI.
The pulp/pulp container seems to work fine but for some reason, the new
pulp-workers in the CI environment are not starting. I have a working
plugin_template PR to update the CI files to use Python 3.8[0] but it's
I haven't heard any objections so I plan to move forward with upgrading our
CI and container images to Python 3.8 on Wednesday July 14 if there are no
objections.
David
On Wed, Jul 7, 2021 at 12:43 PM David Davis wrote:
> Just wanted to call attention to this thread for anyone not check
Just wanted to call attention to this thread for anyone not checking Github
Discussions.
https://github.com/pulp/community/discussions/3
Please submit feedback/questions on the thread.
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
, Jun 16, 2021 at 7:59 PM Neal Gompa wrote:
> On Wed, Jun 16, 2021 at 7:21 PM David Davis wrote:
> >
> > One of the main reasons we wanted to move off mailing lists is that
> signing up is inconvenient for users that may just want to ask a single
> question. But I agree th
in a couple days.
[0] https://www.discourse.org/
[1] https://community.theforeman.org/
[2] https://free.discourse.group/
David
On Wed, Jun 16, 2021 at 5:31 PM James Cassell
wrote:
> On Wed, Jun 16, 2021, at 3:12 PM, Neal Gompa wrote:
> > On Wed, Jun 16, 2021 at 11:59 AM David Davis
in Gmail. It's pretty hard to do
>> filtering of GitHub mail...
>>
>> On Wed, Jun 16, 2021 at 4:29 PM David Davis
>> wrote:
>> >
>> > If you watch the repo, you should be able to get notifications when
>> there's new activity?
>> >
>> >
If you watch the repo, you should be able to get notifications when there's
new activity?
David
On Wed, Jun 16, 2021 at 3:13 PM Neal Gompa wrote:
> On Wed, Jun 16, 2021 at 11:59 AM David Davis
> wrote:
> >
> > Yesterday at open floor, we discussed decommissioning pulp-d
Based on feedback, I've moved discussions to its own repo:
https://github.com/pulp/community/discussions.
David
On Tue, May 25, 2021 at 1:49 PM David Davis wrote:
> We've heard from the community about the amount of friction involved in
> getting help with Pulp and one of the areas I th
I started a discussion on Github about dropping support for Python 3.6 and
Django 2. Please respond with any comments/concerns/feedback.
https://github.com/pulp/pulpcore/discussions/1359
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
We've heard from the community about the amount of friction involved in
getting help with Pulp and one of the areas I think we could improve is
user communications. We currently run two mailing lists: pulp-list and
pulp-dev.
At today's open floor meeting, we talked about using Github's new
Over the past year, we've talked several times about moving off plan.io and
onto Github Issues. We've established that we need a plan for how to do so
though. I'd like to organize a meeting next week to come up with such a
plan. If you are interested in participating, please let me know today or
work>
>> May is Asian Pacific American Heritage Month.
>> <https://source.redhat.com/communitiesatredhat/diversity_and_inclusion/asian_network/asian_pacific_american_heritage_month_2021>
>> We
>> recognize and celebrate the contributions of Asians and Pacific Island
at 2:05 PM Ina Panova wrote:
>
>> I have marked May 19th in the outage calendar as Pulp Docs Day.
>>
>>
>> Regards,
>>
>> Ina Panova
>> Senior Software Engineer| Pulp| Red Hat Inc.
>>
>> "Do not go where the path may lead,
>> go ins
pulp-cli 0.9.0 has been released to PyPI[0]. It is considered beta software
until it reaches its 1.0 release. Future releases will likely break
compatibility.
The 0.9.0 release includes a bugfix caused by the recent release of click 8
as well as a setting for dry_run, better handling of
Ah I see that you will be reordering migrations. Nevermind my idea. I think
you have the right plan.
David
On Tue, May 11, 2021 at 1:02 PM David Davis wrote:
> What if you create a 3.11 release branch and then revert the commits on
> the 3.11 branch? That would save you from having to r
What if you create a 3.11 release branch and then revert the commits on the
3.11 branch? That would save you from having to reapply the two commits.
You could also pin to pulpcore < 3.12 on the 3.11 branch to get the branch
passing while you work on fixing the enqueue problem on master.
David
wrote:
>
>
> On Fri, May 7, 2021 at 11:52 AM David Davis wrote:
>
>> To confirm, the "latest" tag will continue to ship with http? I imagine
>> most users will end up with http then.
>>
> I can modify the PR and make https the default
>
>>
>&
;
>>>>> Best regards,
>>>>> Fabricio Aguiar
>>>>> Software Engineer, Pulp Project
>>>>> Red Hat Brazil - Latam <https://www.redhat.com/>
>>>>> +55 22 999000595
>>>>>
>>>>>
>>>>>
>&
# May 4, 2021
## Topics
* New pulpcore meeting lead?
* New lead rotation
* BaseDistribution drop migration problem
* https://pulp.plan.io/issues/8386#note-5
* Problem: using `run_before` prevents new plugins from being installed
* David to confirm that `run_before` won't work
*
wrote:
> On Sat, Apr 24, 2021 at 09:21:05PM -0400, Daniel Alley wrote:
> >On Fri, Apr 23, 2021 at 10:37 AM David Davis
> wrote:
> >
> >> We started working on a plan to move repos over to Github Issues after
> >> PulpCon last year but I think it kind of fell by t
Sounds good to me. Thank you for organizing this.
David
On Thu, Apr 29, 2021 at 5:47 AM Ina Panova wrote:
> Hi everyone,
>
> Historically we have had Docs Day before a release so we can get some more
> docs PRs in. But this did not work out well for us because of all the
> amount of work and
# April 27, 2021
## Topics
* Migration issue on galaxy
* https://github.com/pulp/pulpcore/pull/1174
* During migration it went out of memory
* Worries about migration breaking in the future when model(s) change
* Need better testing around upgrades
* 3.13 -
This is great. Thank you for working on it.
As a next step, would it make sense to create a branch and then try to
deploy a new temporary tag from that branch? Then maybe we can test a
plugin (eg pulp_npm) against this new image and see what breaks.
David
On Mon, Apr 26, 2021 at 5:01 PM
and if not, find a solution that
will.
[0]
https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Apulp+
David
On Thu, Apr 22, 2021 at 7:42 AM Grant Gainey wrote:
> On Thu, Apr 22, 2021 at 6:48 AM Ina Panova wrote:
>
>>
>> On Wed, Apr 21, 2021 at 7
) or release the announcement without the demo videos (which maybe
defeats the purpose of the demo videos?).
David
On Fri, Apr 23, 2021 at 4:48 AM Melanie Corr wrote:
> Hey David,
>
> Ar Déar 22 Aib 2021 ag 16:14, scríobh David Davis :
>
>>
>> On Tue, Apr 20, 2021 at 10:1
On Tue, Apr 20, 2021 at 10:13 AM Melanie Corr wrote:
> Hi !
>
> Ar Máirt 20 Aib 2021 ag 15:02, scríobh David Davis >:
>
>> # April 20, 2021
>>
>> ## Topics
>> * Demo videos?
>> * Was asked about a demo video for a feature
>> * I
## April 21, 2021
* Moving plugin_template to github issues?
* https://listman.redhat.com/archives/pulp-dev/2021-April/msg00019.html
* pulp-oci-image changes not updating redmine
* Enable github/redmine integration
* Or track issues on github?
* Releasing pulp_installer is
On Fri, Apr 16, 2021 at 8:38 AM David Davis wrote:
> I've always felt that tracking plugin_template issues under the main pulp
> project in plan.io was suboptimal and with other repos such as pulp-cli
> moving to github issues, I feel that it might make sense for the
> plugin_temp
# April 20, 2021
## Topics
* Demo videos?
* Was asked about a demo video for a feature
* I guess we're not doing these anymore?
* Fail to record anything due to capacity and commitments
* Record demos ad hoc?
* Ask feature writer to record demo when stakeholder asks for
Are you running the pulp/pulp:latest image? If so, it should be:
{
"component": "python",
"version": "3.2.0"
},
Check "podman images --digests pulp/pulp:latest" and make sure it matches:
I've always felt that tracking plugin_template issues under the main pulp
project in plan.io was suboptimal and with other repos such as pulp-cli
moving to github issues, I feel that it might make sense for the
plugin_template to move to github issues as well.
There's only 11 open issues right
# April 13, 2021
## Topics
* Orphan endpoint
* As a user I want to see my orphaned content --> generic endpoint
* As a user I want to purge individual orphaned content
* As a user I want to purge orphaned content by type
* Whilst collection v1.2.3 is considered an orphan another
# April 6, 2021
## Topics
* Distribution migration
* problem removing the primary key on the reverse migration
* https://github.com/pulp/pulp_file/pull/495
* Changing a primary key:
https://vivekanandxyz.wordpress.com/2019/02/25/changing-primary-key-in-django-postgresql-setup/
*
There have been reports of Github Actions being abused to run
cryptocurrency mining code by bad actors opening PRs against projects that
use GHA. To prevent our repos from being targeted, I've gone through and
either set repos to only allow select actions or disabled actions
completely (for repos
Great question. We haven't had a compelling reason to upgrade to django 3.2
so there are no current plans or roadmap that I'm aware of.
It looks like the EOL for 2.2 security fixes is April 2022 so we definitely
need to upgrade by then. Our two main stakeholders (Katello and Galaxy) are
both
David Davis wrote:
> It looks like everyone on the team has voted. The week of September 13-17
> seems to be the most popular week. Let's try to aim for some time that
> week. September 20-25 can be a possible backup week if the week of
> September 13 doesn't work out for some reason.
Recently the release workflow was updated to use a manual trigger instead
of being triggered by a new tag[0]. This should allow us to rerun the
release workflow anytime there's a failure.
Once you pick up this change via plugin_template, you'll need to tweak your
release process. If your plugin
in the next month or so in terms of the
actual days/times.
Thanks again everyone.
David
On Wed, Mar 24, 2021 at 11:15 AM David Davis wrote:
> I haven't heard any objections to having PulpCon virtual this year so
> under that assumption, I wanted to gather feedback on when to have PulpCon.
# March 30, 2021
## Previous AIs
* [bmbouter] to close https://github.com/pulp/pulpcore/pull/1122 based on
the recent convo at pulp_ansible meeting
* [ttereshc] to review https://github.com/pulp/pulpcore/pull/1194
* Done, merged
## Topics
* another go/no-go meeting? thursday
* MasterModel
When is the next meeting?
David
On Tue, Mar 23, 2021 at 11:22 AM Ina Panova wrote:
> Here's the tracker for the pulpcore 3.12.0 release
> https://pulp.plan.io/issues/8437
> The tentative GA date is April 6th.
>
> The first go/no-go meeting happened today and so far we are on track.
>
>
my installer development, and support for
> other teams.
>
> So I agree with this approach, but update the plugins too.
>
> -Mike
>
> On Fri, Mar 26, 2021 at 11:16 AM David Davis
> wrote:
>
>> It recently came up that the pulp-smash release PyPI is badly ou
It recently came up that the pulp-smash release PyPI is badly out of date.
It's an extra burden to release it and it doesn't seem to have any benefit.
So instead we're considering using the git repo directly (see [0]) but I
wanted to first check if that's a problem for anyone?
[0]
On Tue, Mar 16, 2021 at 11:08 AM Brian Bouterse wrote:
>
>
> On Mon, Mar 15, 2021 at 11:12 AM David Davis
> wrote:
>
>> The topic of PulpCon came up today as spring is usually the time we begin
>> to plan PulpCon. The main question I think is whether we should hold
>>
# March 16, 2021
## Previous AIs
[mdellweg] summarize "safety in deletion" of remotes feature onto
https://pulp.plan.io/issues/8305 [done]
## Topics
* deleting and rejecting, timeline and scheduling?
* https://pulp.plan.io/issues/7659 run orphan clean up in parallel
* ask for deleting
I've been bitten by this a couple times. I also noticed that ansible
actually defines its own version of urljoin:
https://github.com/ansible/ansible/blob/00bd0b893d5d21de040b53032c466707bacb3b93/lib/ansible/galaxy/api.py#L166-L167
David
On Mon, Mar 15, 2021 at 3:44 PM Grant Gainey wrote:
>
The topic of PulpCon came up today as spring is usually the time we begin
to plan PulpCon. The main question I think is whether we should hold
PulpCon again virtually this year or not.
Optimally, we'd like to meet in person but given the uncertainty of our
current situation, I think we should
The job should be fixed now in plugin_template. Please update your plugin's
CI files.
David
On Mon, Mar 1, 2021 at 10:30 AM David Davis wrote:
> The nightly publish jobs are broken due to a recent change in how
> component names are returned in the status API. I have a potenti
# March 2, 2021
## Previous AIs
* [mdellweg] ping quba42 about pulp_deb CI; Done
## Topics
* docs day for 3.11. Does it makes sense to schedule it this time? I don't
think anyone(?) has made any docs PR for 3.10 docs day due to the
workload[ipanova]
* Skip but mdellweg will check for any
The nightly publish jobs are broken due to a recent change in how component
names are returned in the status API. I have a potential fix that will
require plugins to update their CI configuration from the plugin_template
but I am waiting for a pulpcore CI nightly run to see if it works. Will
reply
pulp-cli 0.6.0 has been released to PyPI[0]. It is considered beta software
until pulp-cli reaches its 1.0 release. Future releases will likely break
compatibility.
This release features support for the upcoming component name change in
pulpcore 3.11. See the changelog for more details[1]. For
One thing I noticed is that the urls still point to
fixtures-test.pulproject.org. I've notified @misc. Hopefully they can get
that resolved soon.
David
On Thu, Feb 25, 2021 at 7:33 AM Brian Bouterse wrote:
> Thank you!
>
> On Thu, Feb 25, 2021, 5:47 AM David Davis wrote:
>
>
The site has been updated and should be working now.
On Tuesday, February 23, 2021, David Davis wrote:
> We're switching over to openshift for fixtures.pulpproject.org on
> Thursday February 25 at 10:00 UTC (5am ET). It may take some time for the
> DNS to update so we expect about an h
We're switching over to openshift for fixtures.pulpproject.org on Thursday
February 25 at 10:00 UTC (5am ET). It may take some time for the DNS to
update so we expect about an hour or so of downtime.
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
pulp-cli 0.5.0 has been released to PyPI[0]. It is considered beta software
until pulp-cli reaches its 1.0 release. Future releases will likely break
compatibility.
This release features pulp 2to3 migration support, multiple config support,
a worker command, and better validation of task states
# February 16, 2021
## Previous action items
* [bmbouter] to revise https://pulp.plan.io/issues/8202 and
https://pulp.plan.io/issues/8167
* Done
* [bmbouter] update working dir changes issue to include docs section about
tempfile https://pulp.plan.io/issues/8231
* Done
* [fao] contribute
# February 9, 2021
## Previous action items
None
## Topics
* https://pulp.plan.io/issues/8202
* Which fields need to be write_only?
* 3.11 release date? volunteer?
* March 2
* ipanova to release
* Discuss rotating the role
* working directory changes
*
pulp-cli 0.3.0 has been released to PyPI[0]. It is considered beta software
until it reaches its 1.0 release. Future releases will likely break
compatibility.
The 0.3.0 release features support for labels, which were added in pulpcore
3.10. See the changelog for all changes[1]. For help
# February 2, 2021
## Previous action items
* [fao89] will port fr the rate limit code to pulpcore - david + brian will
review
* Done: https://github.com/pulp/pulpcore/pull/1091
* [brian and matthias] will meet to talk about security scanners
* Done https://pulp.plan.io/issues/8088
*
In moving fixtures.pulpproject.org to Openshift[0], we had to change the
port nginx listens on in the pulp-fixtures container to 8080 instead of 80.
If you're using pulp-fixtures locally or in your CI, you'll have to either
update your smash-config.json to point to 8080 (see [1]) or map that port
The pulp/pulp-fedora31 container image[0] has been replaced by
pulp/pulp[1]. I plan to remove pulp/pulp-fedora31 after February 5th if
there are no objections.
[0] https://hub.docker.com/r/pulp/pulp-fedora31
[1] https://hub.docker.com/r/pulp/pulp
David
pulp-cli 0.2.0 has been released to PyPI[0]. It is considered beta software
until it reaches its 1.0 release. Future releases will likely break
compatibility.
The 0.2.0 release features pulp_ansible support, a repository modify
command, and the ability to call --help without having to connect to
# January 19, 2021
## Previous action items
* [bmbouter] to ask Satellite if they require this and when
https://pulp.plan.io/issues/7683
* Satellite PM doesn't need. David to check with support.
* [ipanova] open story to add write api for users
* Done.
* [daviddavis] schedule fips check
The first release of the pulp-cli has been released to PyPI[0]. While this
is the first release, the pulp-cli is still considered beta software until
it reaches its 1.0 release. Future releases will likely break compatibility.
The pulp-cli provides a user friendly alternative to the REST API in
There are some great features that have been added to Github Actions--one
of them being manual triggers for workflows (before we weren't sure how we
could trigger the entire release process). So I think we're in a good
position now that we're on Github Actions to automate the rest of the
release
# January 12, 2021
## Previous action items
* [dkliban] to close out pulp_file 1.5.0
* Done
* [ttereshc] start discussion about LTS versions of pulp
* https://www.redhat.com/archives/pulp-dev/2021-January/msg3.html
* Done
## Topics
* Download and verify -
We're approaching feature parity in the CLI with the REST API for pulpcore
and pulp_file. As a result, any new features in pulpcore and pulp_file will
introduce functionality gaps in the CLI.
Optimally, it would be great if developers implemented the CLI
functionality concurrently with the
I agree and I don't have a strong preference between option 1 and 3. If we
go with option 1 though, I'd recommend we prioritize automating the rest of
our release process. Otherwise, we're going to spend a lot of time
releasing.
David
On Wed, Jan 6, 2021 at 8:58 AM Ina Panova wrote:
> Matt,
+1 from me.
David
On Wed, Jan 6, 2021 at 8:28 AM Ina Panova wrote:
> +1 to the change.
>
>
>
> Regards,
>
> Ina Panova
> Senior Software Engineer| Pulp| Red Hat Inc.
>
> "Do not go where the path may lead,
> go instead where there is no path and leave a trail."
>
>
> On Wed, Dec 16,
ry single PR must be refreshed immediately before merging. This
>>> will put off external contributors.
>>>
>>> On Tue, Jan 5, 2021 at 10:42 PM David Davis
>>> wrote:
>>>
>>>> I noticed for the repos that got updated, PRs must now be u
ner
> - pulp_ansible
> - pulp_python
> - pulp_deb
> - pulp-2to3-migration
> - pulp-certguard
>
>
> On Wed, Dec 9, 2020 at 5:35 PM David Davis wrote:
>
>> When we stopped using Travis, I disabled the required status checks in
>> Github for pull requests. To re-enable
+1 to a global plugin release checklist template.
I imagine that pulpcore will have its own set of templates though? I think
there are some steps (eg release the plugin_template and installer) that
plugins don't do.
David
On Tue, Dec 15, 2020 at 11:19 AM Tanya Tereshchenko
wrote:
> We
# January 5, 2021
## Previous action items
* [dkliban] to release pulp_file 1.5.0
* [ttereshc] work on https://pulp.plan.io/issues/7869
* done https://github.com/pulp/plugin_template/pull/325
* [x9c4] write a task to have a test that searches for log messages with
deprecation warnings
*
To follow up, I've added the remaining issues to an epic in pulp.plan.io:
https://pulp.plan.io/issues/7960.
David
On Fri, Dec 11, 2020 at 8:00 AM David Davis wrote:
> I wanted to email these user stories out to the Pulp community to call for
> any feedback. Any comments/questions w
I wanted to email these user stories out to the Pulp community to call for
any feedback. Any comments/questions welcome.
https://hackmd.io/KzcCx9ZZR26kvQqJYp46GQ?view
Thank you.
David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
into
postgresql). So I've updated the ticket with a version of option 1.
https://pulp.plan.io/issues/7127
More feedback is welcome. Also, please feel free to groom it. :)
David
On Wed, Dec 2, 2020 at 1:08 PM David Davis wrote:
> I've put together some design proposals to support object labels in P
When we stopped using Travis, I disabled the required status checks in
Github for pull requests. To re-enable these required status checks, visit
the branch protection settings page for your plugin's repo. Configure a
branch protection rule and there should be a setting to require status
checks.
# December 8, 2020
## Previous action items
* [ttereshc] to file a task to implement plugin removal
* Done https://pulp.plan.io/issues/7822
* [fao89] to figure out the use case for this fix
Pulpcore 3.9.0 [0] and pulp_installer 3.9.0 [1] have been released.
For a full list of changes, please check the changelog for pulpcore [2] and
pulp_installer [3].
# Installation and Upgrade
Users should use the 3.9.0 release of pulp_installer [1] to install or
upgrade their installations. This
Today we had our go/no-go meeting and the decision was made to release 3.9
on December 7th, 2020.
David
On Wed, Dec 2, 2020 at 11:37 AM David Davis wrote:
> For now, we are still aiming to release on December 7th, 2020. But there
> are still some open issues which warrant another
I've put together some design proposals to support object labels in Pulp 3.
This would add key/value labels to a variety of objects in Pulp that users
could use to store information and to filter objects with.
Story: https://pulp.plan.io/issues/7127
Proposals:
For now, we are still aiming to release on December 7th, 2020. But there
are still some open issues which warrant another check in meeting.
The next go/no-go meeting will be December 4, 2020 at 3:30pm UTC/10:30am ET.
David
On Mon, Nov 30, 2020 at 11:01 AM David Davis wrote:
> We met to
# December 1, 2020
### Previous action items
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions,
updating template config, etc)
* https://pulp.plan.io/issues/7817 (needs grooming, please provide
feedback)
*
We met today and reviewed the outstanding issues along with the work left
on our CI/CD infrastructure. For now, we are still aiming to release on
December 7th, 2020.
The next go/no-go meeting will be December 2, 2020 at 4:15pm UTC/11:15am ET.
David
On Mon, Nov 23, 2020 at 10:47 AM David Davis
idn't assign anything new to you while you were away :)
>
> Tanya
>
> On Tue, Nov 24, 2020 at 8:26 PM David Davis wrote:
>
>> Thanks for taking notes and sorry I couldn't be at the meeting. Can you
>> explain more about the action item to give updates on the tagging s
Thanks for taking notes and sorry I couldn't be at the meeting. Can you
explain more about the action item to give updates on the tagging story? I
was planning on following up on the mailing lists with updates since I
don't think the feature will be specific to pulpcore.
As for the automatic
On Tue, Nov 10, 2020 at 11:48 AM Tanya Tereshchenko
wrote:
> Just fixed a typo. It's 3.9.0.
>
> On Tue, Nov 10, 2020 at 4:52 PM David Davis wrote:
>
>> Here's the tracker for the pulpcore 3.8.0 3.9.0 release:
>> https://pulp.plan.io/issues/7789.
>> The tent
/issues/7859
David
On Fri, Nov 13, 2020 at 12:31 PM David Davis wrote:
> A few of us met today to discuss moving the Pulp CI off Travis and onto
> Github Actions. I wanted to send out notes[0] and summarize the next steps.
>
> For Sprint 86, we hope to get pulp_npm fully working on Gi
A few of us met today to discuss moving the Pulp CI off Travis and onto
Github Actions. I wanted to send out notes[0] and summarize the next steps.
For Sprint 86, we hope to get pulp_npm fully working on Github Actions
which will include getting tests, publishing docs and bindings, releasing,
etc
Here's the tracker for the pulpcore 3.8.0 release:
https://pulp.plan.io/issues/7789.
The tentative GA date is November 30th.
The first go/no-go meeting will happen in #pulp-meeting at the time below:
November 23 3:30pm UTC/November 23 10:30am ET
https://everytimezone.com/s/bc9ca71d
David
## November 10, 2020
### Previous action items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* ~~[dkliban] file a task for running tests for multiple plugins in one
fips environment in the installer nightly~~
* [fao89] look at driving forward
1 - 100 of 684 matches
Mail list logo
