[Pulp-dev] Upcoming Docs Day

Hi pulp-devs, there is an upcoming Docs Day! Please check this discussion if you'd like to participate and get more information! https://github.com/pulp/community/discussions/78 Thanks. Regards, Ina Panova Principal Software Engineer| Pulp| Red Hat Inc. "Do not go where the pat

[Pulp-dev] [Meeting Minutes] Sprint 102 Planning Meeting Minutes

Meeting minutes have been posted: https://github.com/pulp/community/discussions/30#discussioncomment-1121573 Description of the Sprint content can be found here: https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans Regards, Ina Panova Principal Software Engineer| Pulp| Red Hat Inc

Re: [Pulp-dev] Docs day revamp

Team, I would like to recapitulate yesterday's Docs day. In a day we managed to knock down 12 issues [0]. Great job! Thanks to everyone who participated whether by submitting or reviewing PRs. [0] https://tinyurl.com/rsv7m4c2 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat

Re: [Pulp-dev] Docs day revamp

The Pulpcore team met today and went a bit through the docs backlog. Here is the query with the list of docs issues we are going to focus tomorrow May 19 https://tinyurl.com/ymctcr32 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may

Re: [Pulp-dev] How to enable HTTPS for our tests in pulpcore and all plugins?

I would get rid of the latest tag because it is non-deterministic and would keep http/https tags only. 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 Fri, May 7,

Re: [Pulp-dev] Docs day revamp

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 instead where there is no path and leave a trail." On Thu, Apr 29, 2021 at 12:54 PM David Davis wrote:

[Pulp-dev] Docs day revamp

we should be over a pulpcore 3.13 release and the temperature should be relatively low. Suggestions are welcome. [0] https://tinyurl.com/r492c8s [1] https://tinyurl.com/ymctcr32 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead

Re: [Pulp-dev] Tracking issues for plugin_template

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, Apr 21, 2021 at 7:55 PM David Davis wrote: > Wanted to bump this to hopefully get some feedback. Also, tod

Re: [Pulp-dev] [Pulp-list] PulpCon 2021

+1 for November date. Another argument to prefer November dates to September is the preparation for the AnsibleFest. I think every year we whether get involved in the booth/talks preparation or some feature delivery to show off. Regards, Ina Panova Senior Software Engineer| Pulp| Red

Re: [Pulp-dev] How docker type repositories are getting synced in pulp3 w.r.t concurrency ?

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 Tue, Mar 30, 2021 at 10:12 AM Sayan Das wrote: > Hello Matthias, > > Thanks for your r

Re: [Pulp-dev] How docker type repositories are getting synced in pulp3 w.r.t concurrency ?

We need to look into fixing this bug https://pulp.plan.io/issues/8295 to match the behaviour you have described Matthias. 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

Re: [Pulp-dev] Removing pulp-smash from PyPI

+1 Thank you! On Mon, 29 Mar 2021, 18:24 David Davis, wrote: > I've heard back from most stakeholders that no one's using pulp-smash > outside of the Pulp team. And I am not seeing any objections to removing it > from PyPI. > > I plan to remove it from PyPI after April 5th unless anyone

[Pulp-dev] pulpcore 3.12.0 release schedule & go/no-go irc meeting

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. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the pat

[Pulp-dev] Content management and disk space clean-up

All these are whether directly or indirectly related to the problem of how to reclaim the disk space. If you have not received an invite and you want to participate please ping me so I add you. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the pat

Re: [Pulp-dev] pulpcore 3.11.0 release schedule & go/no-go irc meeting

Our blocker list has been cleaned up so the release process for 3.11 will start on Monday, March 15. 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 Fri, Mar 5,

Re: [Pulp-dev] pulpcore 3.11.0 release schedule & go/no-go irc meeting

With the amount of the PRs to review and one more issue to nail down it has been decided to push back the release date and have another go/no-go on March 11th 2:30 PM UTC/9.30AM ET Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may

Re: [Pulp-dev] pulpcore 3.11.0 release schedule & go/no-go irc meeting

Forgot to send this yesterday. Based on the meeting which was held yesterday it has been decided that the tentative release date stays the same - March 9th. Next check in meeting will be on Friday, March 3rd 3:00 PM UTC/10AM ET Regards, Ina Panova Senior Software Engineer| Pulp| Red

Re: [Pulp-dev] pulpcore 3.11.0 release schedule & go/no-go irc meeting

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, Feb 17, 2021 at 12:32 PM Ina Panova wrote: > Here's the tracker for the pulpcore 3.11.0 release > https://pulp.pla

Re: [Pulp-dev] Backports and LTS

the backport requests is to really be thorough about which ones to accept by assessing the impact of the stakeholder who has created the request and their possibility to upgrade if any. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead

Re: [Pulp-dev] plugin release checklist templates

+1 to a generic release checklist template. 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 Tue, Jan 5, 2021 at 4:11 PM Matthias Dellweg wrote: > +1 for

Re: [Pulp-dev] RBAC: Secure by default?

+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, 2020 at 8:14 PM Tanya Tereshchenko wrote: > It sounds like a good idea, and

Re: [Pulp-dev] Renaming master to main for pulp_deb

I don't think that other repos or ci are referencing master branch other than pulpcore's. 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 Thu, Dec 10, 2020 a

Re: [Pulp-dev] Re-enable required status checks

Thanks Tanya! 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 Fri, Dec 11, 2020 at 1:26 PM Tanya Tereshchenko wrote: > FYI, I went through the following repo

[Pulp-dev] Artifact upload recovery workflows

Hey folks, we had a meeting today about how to manage missing or corrupted files during the upload process and have captured some ideas on this issue https://pulp.plan.io/issues/7791 Please review and provide feedback directly on the ticket. Thank you! Regards, Ina Panova Senior

[Pulp-dev] Orphan clean up proposal

[1] https://pulp.plan.io/issues/7659 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." ___ Pulp-dev mailing list Pulp-dev@redhat

[Pulp-dev] Pulp Docs day is Today (Nov 30)

Hi, Today is our Pulp Documentation day. Please grab an issue or two and let's work towards having better docs! 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

[Pulp-dev] Container plugin meeting notes

ock mdellweg * reviewed opened PRs and untriaged bugs Pulp 2: Open PRs: * https://github.com/pulp/pulp_container/pulls Un-triaged bugs: * https://pulp.plan.io/projects/pulp_container/issues?query_id=159 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not

[Pulp-dev] Pulp Docs day is delayed

Everyone, We are pushing back the docs day by one week to November 30. Most of the folks are busy right now with the moving from Travis to GHA. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no

[Pulp-dev] Pulp Docs day is Today!

Hi, Today is our Pulp Documentation day. Please grab an issue or two and let's work towards having better docs! 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

[Pulp-dev] Docs Day November 23

Hi, our next Documentation day will be held on November 23rd. Please grab an issue or two and let's work towards having better docs! I will send one more reminder on the Docs Day. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead

[Pulp-dev] Container plugin meeting notes

159 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." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container meeting notes

coverage Pulp 2: Open PRs: * https://github.com/pulp/pulp_container/pulls Un-triaged bugs: * https://pulp.plan.io/projects/pulp_container/issues?query_id=159 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] Abandon PUP process

The repo has been archived https://github.com/pulp/pups . 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 Mon, Oct 26, 2020 at 5:20 PM Ina Panova wrote: >

Re: [Pulp-dev] the "relative path" problem

Tanya, Thank you for summarizing the proposal. I left comments and questions directly on the story. 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 Mon, Oct 26,

[Pulp-dev] Abandon PUP process

on November 2nd, please express all the objections, if any, by then. Thank you! 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." __

[Pulp-dev] Container plugin meeting notes

://pulp.plan.io/issues/7707 * 3 months planning * RBAC * FIPS Pulp 2: Open PRs: * https://github.com/pulp/pulp_container/pulls Un-triaged bugs: * https://pulp.plan.io/projects/pulp_container/issues?query_id=159 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. &qu

Re: [Pulp-dev] Creating a more visible presence on Matrix

This is great, thank you. 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, Oct 14, 2020 at 3:48 PM Melanie Corr wrote: > Hi all, > > I had a chat

[Pulp-dev] Container plugin meeting notes

ery_id=159 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." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] sphinx theme for docs.pulpproject.org

my preference number 1 would be making plugins consistent with pulpcore. 2nd preference would be plup_ansibe theme. 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." O

Re: [Pulp-dev] CLI team meeting notes

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 Fri, Sep 25, 2020 at 2:48 PM Matthias Dellweg wrote: > This is all interesting, but as one of the goa

Re: [Pulp-dev] PR merging

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, Sep 30, 2020 at 2:38 PM David Davis wrote: > I am also concerned about the lack of human involvement and

Re: [Pulp-dev] python-nectar 1.6.2 needed

Thank you, I will put together a small announcement then. 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 Mon, Sep 28, 2020 at 8:12 AM Evgeni Golov wrote:

Re: [Pulp-dev] CLI team meeting notes

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 Thu, Sep 24, 2020 at 7:15 PM Brian Bouterse wrote: > > > On Wed, Sep 23, 2020 at 3:31 PM Robin Chan w

Re: [Pulp-dev] python-nectar 1.6.2 needed

Evgeni, Today Lai confirmed that he successfully synced the problematic repos with the new builds. So please feel free to proceed and push those to stable repos. Thank you. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

Re: [Pulp-dev] Disabling merge by commit

Hi Quirin, 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, Sep 23, 2020 at 10:47 AM Quirin Pamp wrote: > "I'd encourage plugins to consider disabli

[Pulp-dev] Container plugin meeting notes

=159 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." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailma

Re: [Pulp-dev] python-nectar 1.6.2 needed

` are Null, however once it fails I do see both of the keys https://pastebin.com/tE9NzPe6 That's being said the issue is not related to the changes in nectar. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] python-nectar 1.6.2 needed

Hi, Still waiting on the test results. I will keep you posted. Thanks! 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 Mon, Sep 21, 2020 at 8:46 AM Evgeni Go

Re: [Pulp-dev] python-nectar 1.6.2 needed

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 Tue, Sep 15, 2020 at 4:50 PM Ina Panova wrote: > Hey, > we should do some testing first. > Please keep the build for now in stage, o

Re: [Pulp-dev] python-nectar 1.6.2 needed

Hey, we should do some testing first. Please keep the build for now in stage, once it is confirmed that the patches fix the original issue we can push to stable. Thank you! Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

[Pulp-dev] Docs Day September 17

try to dedicate couple of hours to the Docs. Thanks! 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." ___ Pulp-dev mailing

[Pulp-dev] Container plugin meeting notes

/pulls Un-triaged bugs: * https://pulp.plan.io/projects/pulp_container/issues?query_id=159 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 an

[Pulp-dev] container plugin meeting notes

, 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." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] problem: version locking plugins to pulpcore

+1 to the idea. It will definitely improve user experience. 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, Aug 19, 2020 at 12:21 PM Tatiana Tereshchenko wr

Re: [Pulp-dev] github checklist as a part of the release process

+1 to add the checklist. I am ok having it whether in redmine or a new github repo. 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 Thu, Aug 20, 2020 at 4:44 P

[Pulp-dev] Container plugin meeting notes

to run on travis due to kernel limitations on the host - Add to 3 months planning meeting, the goal is to release without tech preview label Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

[Pulp-dev] Container plugin meeting notes

: - Un-triaged bugs https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] When to declare Pulp safe for multi-user?

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 Tue, Aug 11, 2020 at 11:10 PM Brian Bouterse wrote: > Pulpcore 3.6 adds RBAC machinery for plugins to enable

Re: [Pulp-dev] Documentation issues

Thanks everyone for the replies. I marked August 13th as Docs Day 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 Fri, Aug 7, 2020 at 10:28 PM Fabricio Aguiar wr

Re: [Pulp-dev] Skipped repo produces result: error

if it succeeds the state should not be error unless some issue occurred. 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 Fri, Aug 7, 2020 at 10:48 AM Mike Kenyon wrote:

Re: [Pulp-dev] Dealing with our redmine backlog

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, Aug 5, 2020 at 8:54 PM David Davis wrote: > We've been discussing the possibility of closing issues i

[Pulp-dev] Container plugin meeting notes

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." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailma

Re: [Pulp-dev] saftladen pulp's take on asciinema?

This is great, +1 to the automation business. Even though shell scripts are quite self explanatory, could you write some Readme? We could eventually add this to our Wiki https://pulp.plan.io/projects/pulp/wiki/Demo_Presenter_Notes#Recording-a-Video Regards, Ina Panova Senior Software

Re: [Pulp-dev] Allowing Older Z-stream Backports and Releases?

To follow up on this, during the open floor it has been decided to create a Backport tracker to facilitate backport requests, in addition some docs are being written so people have guidelines. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the

[Pulp-dev] Documentation issues

is a good idea I'll go ahead and pick a day in our calendar and mark it as "Docs day". ---- 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." __

Re: [Pulp-dev] Draft Community Demo - Your Opinion Please

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 Mon, Jul 27, 2020 at 1:48 PM Melanie Corr wrote: > > Hey Ina, > > Thanks for reviewing. > > A

[Pulp-dev] Container plugin meeting notes

ub.com/pulp/pulp_docker/pulls - https://github.com/pulp/pulp_container/pulls - Triage: - Un-triaged bugs https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 Regards, Ina Panova

Re: [Pulp-dev] Draft Community Demo - Your Opinion Please

ature set, workflows, installation, etc) or on the contrary what in their opinion has gotten worse or they do not see value in certain areas. ---- 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

Re: [Pulp-dev] Name uniqueness problem in Pulp 3 REST API

update it in a more generalized way so we add in addition to 'name' also 'type' to the uniqueness constraint to all the master/detail models where it makes sense? [0] https://pulp.plan.io/issues/5656. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the

[Pulp-dev] Pulp Container meeting minutes

https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 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

Re: [Pulp-dev] Name uniqueness problem in Pulp 3 REST API

This name uniqueness problem is extended to remotes and distributions, and probably some other objects. 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 Tue, Ju

[Pulp-dev] Container plugin meeting notes

https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 <https://pulp.plan.io/projects/pulp_container/issues?query_id=30> Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. &quo

[Pulp-dev] Pulp Container meeting notes

- https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 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." __

[Pulp-dev] Container plugin meeting notes

aged bugs https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no

Re: [Pulp-dev] Moving fixtures container URL

Thank you for doing this. 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 Tue, Jun 9, 2020 at 1:33 PM David Davis wrote: > This move has been completed.

Re: [Pulp-dev] Feedback needed: How to track progress in a TaskGroup

The story is groomed and added to the sprint. Thanks everyone for the participation and feedback! 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 Fri, May 29, 20

[Pulp-dev] status

er PTO 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." ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulp Container meeting notes

/pulp/pulp_container/pulls - Triage: - Un-triaged bugs https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go

[Pulp-dev] pulp_container 2.0.0 beta 2 is available

/pulp_installer/releases/tag/3.4.0 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." ___ Pulp-dev mailing list Pulp-dev@redhat

[Pulp-dev] RPM plugin meeting notes

is the metadata? - https://github.com/pulp/pulp_rpm/pull/1558 Open PRs: - https://github.com/pulp/pulp_rpm/pulls Triage: - Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc

[Pulp-dev] Feedback needed: How to track progress in a TaskGroup

Hi folks, there is an issue written with some potential options on how we can track progress of the work that tasks have done in a task group. [0] Please review the proposal, comment directly on the issue. Thank you. [0] https://pulp.plan.io/issues/6858 Regards, Ina Panova Senior

[Pulp-dev] Pulp Container meeting notes

/pulls - https://github.com/pulp/pulp_container/pulls - Triage: - Un-triaged bugs https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 Regards, Ina Panova Senior Software Engineer| Pulp

[Pulp-dev] Container plugin meeting notes

/pulp/pulp_container/pulls - Triage: - Un-triaged bugs https://pulp.plan.io/projects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go

Re: [Pulp-dev] No-Retry Behaviour on Network Errors: call for feedback and concerns

I have a small suggestion. Besides the documentation plan I would suggest to catch the exception thrown on server disconnect and give to the users something more friendly and not have that traceback in the logs. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do n

Re: [Pulp-dev] Installer project

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 Fri, May 8, 2020 at 3:55 PM Brian Bouterse wrote: > > > On Tue, May 5, 2020 at 10:48 AM David Davis

Re: [Pulp-dev] [Pulp-list] Pulp 3 CLI MVP

+1 to 'pulp' command +1 to first have plugin name 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 Thu, May 7, 2020 at 2:28 PM Dennis Kliban wrote: > On Thu

[Pulp-dev] Pulp Container meeting notes

ojects/pulp_container/issues?query_id=30 - https://pulp.plan.io/projects/pulp_docker/issues?query_id=30 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 le

Re: [Pulp-dev] Installer project

+1 to the plan. On Tue, 5 May 2020, 19:33 Fabricio Aguiar, wrote: > Yes, it makes sense > > Best regards, > Fabricio Aguiar > Software Engineer, Pulp Project > Red Hat Brazil - Latam > +55 11 999652368 > > > On Tue, May 5, 2020 at 12:24 PM David Davis wrote: > >>

Re: [Pulp-dev] Moving to travis-ci.com

+1 to move pulp3 projects. Thank you for taking care of this. 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 Fri, May 1, 2020 at 9:22 PM Brian Bouterse wrote

Re: [Pulp-dev] fedorapeople.org fixtures

I am also in favour of hosting fixtures. Eventually we'd also need to update our tests and workflows in the docs that point to the fedorapeople.orf fixtures. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] pulp_file 1.0

Based on the extended reply from David referring to semver, I am in favour or releasing pulp_file 1.0. Also, comments inline. 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

Re: [Pulp-dev] serializers in pulp 3 can't use write_only fields

I like option number 2 more, even if there is more work behind the scene it is more explicit and does not leave opened questions like ' why certain fields are null' Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] MODIFIED issues

Comments inline. 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 Mon, Apr 20, 2020 at 2:41 PM David Davis wrote: > During the pulpcore team meeting last w

Re: [Pulp-dev] the "relative path" problem

Daniel, how about setting up a meeting and brainstorm the alternatives, pros/cons there? 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 Fri, Apr 17, 2020

Re: [Pulp-dev] PR Processor

Thank you for this work! 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 Sat, Mar 21, 2020 at 3:49 PM Daniel Alley wrote: > This is great! Awesome w

Re: [Pulp-dev] Package in a different repo does not get added to package list on Module

and message? Thank you. 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, Mar 18, 2020 at 2:04 PM Ina Panova wrote: > This has always been a grey area: > &g

Re: [Pulp-dev] Duplicate nevra but not pkgId (suse repos)

/app/models/package.py#L188 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, Mar 18, 2020 at 2:24 PM Pavel Picka wrote: > True in opensuse repository

Re: [Pulp-dev] Package in a different repo does not get added to package list on Module

This has always been a grey area: what if the user who has created RepoA cannot access content to the repoB and yet we are 'stealing' the content from repoB? Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead

Re: [Pulp-dev] Cherry pick labeling

It would be great if we could automate this part as well. As per responsibility, I think both reviewer and author should share it. Obviously if this is a new contributor, as Tanya mentioned, then reviewer should make sure the label is properly placed if needed. Regards, Ina Panova

Re: [Pulp-dev] Duplicate nevra but not pkgId (suse repos)

that could have pointed to the rpm that did not actually get saved. I believe in Pulp3 we could allow having rpm with same NEVRA if they have different location_href within a repo. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go in

  1   2   3   >