Bumping the thread, moved it to the GitHub discussions
https://github.com/pulp/community/discussions/20.
On Tue, May 18, 2021 at 5:55 PM Tanya Tereshchenko
wrote:
> Hi,
>
> I'd like to bring to your attention a suggestion [0] (based on a BZ [1])
> to categorize Pulp logs differen
Hi,
I'd like to bring to your attention a suggestion [0] (based on a BZ [1]) to
categorize Pulp logs differently and have an ability to write them to a
different place.
Different users might want to do it differently, so I read it as an ask to
make logging more configurable.
It might also be a
Hi Grant,
Thanks for putting this together.
It sounds about right, as a general idea of what needs to happen.
I would leave it to a person who performs all the git fu to figure out
exact commits and details and to the reviewer of all those changes, when PR
1984 is ready to be merged and releases
Hey Grant,
Let's start with thoughts without modularity :)
I think the main reasons for the existing behavior are semantical and also
aim to preserve collections as they are.
The situation you describe (when I change only pkglist and nothing else at
all) usually means one of the following:
1. A
On Wed, Mar 31, 2021 at 2:39 PM Melanie Corr wrote:
>
>
> Ar Céad 31 Márta 2021 ag 13:36, scríobh Grant Gainey :
>
>> On Wed, Mar 31, 2021 at 8:00 AM David Davis
>> wrote:
>>
>>> After talking to some people this morning, it sounds like November 8-12
>>> would also work. I think people would
# March 23, 2021
## Previous AIs
* [ipanova] to set up meeting about content management (removal, rejecting,
etc) [done]
* [bmbouter] to merge https://github.com/pulp/pulp/pull/4020/ and reply to
thread [done]
## Topics
* Do we need a pulp_file release for pulpcore 3.11?
* we have 1.6.0
The 3.10.0 seems to be on track to be released on Feb 4th.
I'll update this thread in case of any issues or changes in the schedule.
On Tue, Jan 26, 2021 at 6:35 PM Tanya Tereshchenko
wrote:
> More pulpcore items keep showing up related to the pulp_container RBAC
> work. Since it
Reminder: I'm working 1/2 day (US mornings) tomorrow and on Thursday
Tuesday:
* Core + Pulp 3 Container RBAC
- filed a task [0] to add repo check to global permissions, opened a
PR [1]
- RBAC meeting with container mini-team
- revisited and adjusted the repo versions RBAC PR [2]
wrong list, ignore me
On Tue, Jan 26, 2021 at 8:28 PM Tanya Tereshchenko
wrote:
> Reminder: I'm working 1/2 day (US mornings) tomorrow and on Thursday
>
> Tuesday:
> * Core + Pulp 3 Container RBAC
> - filed a task [0] to add repo check to global permissions, o
for plugins at this
moment.
The tentative GA date is Feb 4th.
The next go/no-go meeting will happen in #pulp-meeting at the time below:
February 2, 3:00 PM UTC/ February 2, 10:00 AM ET
https://everytimezone.com/s/f0f3b5c7
On Fri, Jan 22, 2021 at 4:32 PM Tanya Tereshchenko
wrote:
> With some items st
check-in meeting will be in #pulp-meeting at the time below:
https://everytimezone.com/s/da051970
On Tue, Jan 19, 2021 at 4:16 PM Tanya Tereshchenko
wrote:
> So far 3.10.0 is on track to be released on Jan 26th.
>
> The next check-in meeting will be in #pulp-meeting this Friday at the sa
Pulpcore 3.10 is currently planned to be released on Jan 26th.
We always encourage plugin maintainers to release a compatibility release
with an upcoming pulpcore release to avoid rushing with a plugin release
right after the pulpocre is out.
Don't forget to address the pulpcore 3.10 requirement
Here's the tracker for the pulpcore 3.10.0 release:
https://pulp.plan.io/issues/8087
The tentative GA date is January 26th.
The first go/no-go meeting will happen in #pulp-meeting at the time below:
January 19, 3:00 PM UTC/January 19, 10:00 AM ET
https://everytimezone.com/s/f7b5af77
Bump.
Just a reminder for plugin maintainers to enable that if you haven't done
it yet.
Tanya
On Fri, Dec 11, 2020 at 11:05 PM Dennis Kliban wrote:
> The plugin-template can now be used to enable a cron job that tests the
> latest release of a plugin on PyPI against the master branch of
I went through the list of repos from this thread and pulp 3 related
branches and unset the up-to-date check where it was set.
Thanks for noticing and pointing out the problem.
Tanya
On Wed, Jan 6, 2021 at 12:58 PM Tanya Tereshchenko
wrote:
> Interesting, I didn't notice that.
> In any c
gt; I noticed for the repos that got updated, PRs must now be up to date
>> before merging. I think we previously had this disabled but I am guessing
>> it got enabled since it's the default when required status checks are
>> enabled?
>>
>> David
>>
>>
>>
With more and further away backport requests coming in, there is more need
for a clear policy/docs to set expectations for users and to define
requirements for those performing a backport.
The question which hasn't been answered yet (in documented way) is:
*Should backports be backported to
It sounds like a good idea, and additional +1 that it doesn't break
things.
On Tue, Dec 15, 2020 at 5:57 PM Matthias Dellweg
wrote:
> In today's pulpcore meeting, we discussed that any endpoint that is not
> aware of RBAC yet will be open to every authenticated user.
>
> The suggestion that
We started using redmine checklists in pulpcore and in some plugins.
Here [0] is an example of a plugin checklist in use.
Currently any plugin which has a checklist template has their own checklist
template.
It's quite inconvenient to update those if there any changes introduced to
the release
Previous action items
- [dkliban] to schedule backlog grooming meeting
- done
- [dkliban] to email plugins about and close out
https://pulp.plan.io/issues/7895
- email sent, the issue will be closed today
- [bmbouter] release pulp_file 1.5.0
- dkliban will do it
Hi Quirin,
I'm replying based on my experience. Maybe folks can add more or correct me
if I'm off somewhere.
On Mon, Dec 14, 2020 at 6:27 PM Quirin Pamp wrote:
> Hi everyone,
>
> I wanted to ask if there is some agreed upon workflow/convention, on when
> to apply the latest changes from the
FYI, I went through the following repos and enabled required checks (lint,
test(pulp), test(docs), and test(s3)) where they were missing, for the
master and for the release branches if such rules existed:
- pulpcore
- pulp_file
- pulp_rpm
- pulp_container
- pulp_ansible
- pulp_python
-
Thanks!
How do I trigger the docs job?
Is it a part of the release workflow only or is there a way for me to
publish docs before a release?
Tanya
On Thu, Dec 10, 2020 at 8:45 PM Dennis Kliban wrote:
> Each plugin repository in the Pulp organization on GitHub has been
> configured with a
Thanks for the write-up and the guesstimation!
It would be really helpful for me personally to see stakeholder use cases
or to understand if we are trying to cover similar use cases as we had in
Pulp 2.
I believe it's very important for this specific plugin to get the modelling
right right from
to pulpcore.
>
> As for the automatic merge PR (https://github.com/pulp/pulp-ci/pull/737),
> I wasn't planning on carrying forward an AI for it. I don't have any time
> to address in the near future but I'm happy to hand it off to someone else
> if they're interested.
>
> David
>
>
&
Previous action items
- [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
- Hold off until after Github Actions move
- [fao89] look at driving forward release automation.
- Automate post-release steps (branching, bumping to dev
Hi Erik,
Thank you so much for sharing! A great example of using Python bindings for
client tooling.
I'm adding pulp-list to share it with more users, and not only developers.
Thank you,
Tanya
On Sat, Nov 14, 2020 at 6:43 PM Erik K. Whitesides
wrote:
> Hi - not sure if anyone is interested,
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 tentative GA date is November 30th.
>
> The first go/no-go meeting will happen in #pulp-meeting at the time
Here is the user authentication stories for Pulp 3 which are in MVP [0].
Please, groom them:
* Basic Auth https://pulp.plan.io/issues/2358
* JWT https://pulp.plan.io/issues/2359
If you are still in the auth mood, more Pulp 3 auth stories are
available for grooming but they are out of
29 matches
Mail list logo
