Re: PDC replacement proposal

2023-09-14 Thread Adam Williamson
On Thu, 2023-09-14 at 07:41 +0200, Tomas Hrcka wrote: > Ok, now we are on the same page. > > On Wed, Sep 13, 2023 at 8:04 PM Adam Williamson > wrote: > > > On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote: > > > I thought this was exactly the JSON blob we will implement, If you look > > at

Re: PDC replacement proposal

2023-09-13 Thread Tomas Hrcka
Ok, now we are on the same page. On Wed, Sep 13, 2023 at 8:04 PM Adam Williamson wrote: > On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote: > > I thought this was exactly the JSON blob we will implement, If you look > at > > the model of PDC > > >

Re: PDC replacement proposal

2023-09-13 Thread Adam Williamson
On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote: > I thought this was exactly the JSON blob we will implement, If you look at > the model of PDC > https://product-definition-center.github.io/product-definition-center/_images/overview.svg > > Those endpoints are covered by relations Release,

Re: PDC replacement proposal

2023-09-13 Thread Tomas Hrcka
I thought this was exactly the JSON blob we will implement, If you look at the model of PDC https://product-definition-center.github.io/product-definition-center/_images/overview.svg Those endpoints are covered by relations Release, Compose, RPM through some others. The PDC approach is more or

Re: PDC replacement proposal

2023-09-11 Thread Adam Williamson
On Mon, 2023-09-11 at 09:40 -0700, Kevin Fenzi wrote: > These are the things that fedfind/qa users? Do we have examples of this > data? Okay, here is (again) a list of the stuff fedfind uses. You can see sample data for each compose in the web UI itself, PDC actually has a rather good interactive

Re: PDC replacement proposal

2023-09-11 Thread Kevin Fenzi
On Mon, Sep 11, 2023 at 03:08:50PM +0200, Tomas Hrcka wrote: > Sorry for the confusion with work that is already done, > We can drop the critpath thanks Adam! > > > As it goes for EoL and package retirement we for the past few releases we > are saving EOL date in bodhi. > So getting EOL for

Re: PDC replacement proposal

2023-09-11 Thread Mattia Verga via devel
Il 11/09/23 15:08, Tomas Hrcka ha scritto: > Sorry for the confusion with work that is already done, > We can drop the critpath thanks Adam! > > As it goes for EoL and package retirement we for the past few releases we are > saving EOL date in bodhi. > So getting EOL for specific release is not

Re: PDC replacement proposal

2023-09-11 Thread Tomas Hrcka
Sorry for the confusion with work that is already done, We can drop the critpath thanks Adam! As it goes for EoL and package retirement we for the past few releases we are saving EOL date in bodhi. So getting EOL for specific release is not a problem once the release is out. For storing the

Re: PDC replacement proposal

2023-09-06 Thread Pierre-Yves Chibon
On Tue, Sep 05, 2023 at 11:35:19AM -0700, Kevin Fenzi wrote: > On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote: > > Hello all, it took us a few years but we are finally getting rid of the PDC > > project. Thanks to the ARC research we identified use cases in our tooling > > and

Re: PDC replacement proposal

2023-09-06 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote: > Hello all, it took us a few years but we are finally getting rid of the PDC > project. Thanks to the ARC research we identified use cases in our tooling > and proposed solution. > > The essential functionalities currently provided by

Re: PDC replacement proposal

2023-09-05 Thread Kevin Fenzi
On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote: > Hello all, it took us a few years but we are finally getting rid of the PDC > project. Thanks to the ARC research we identified use cases in our tooling > and proposed solution. > > The essential functionalities currently provided by

Re: PDC replacement proposal

2023-09-04 Thread Dominik 'Rathann' Mierzejewski
On Tuesday, 05 September 2023 at 01:05, Adam Williamson wrote: > On Mon, 2023-09-04 at 22:26 +0200, Dominik 'Rathann' Mierzejewski > wrote: > > On Monday, 04 September 2023 at 17:37, Adam Williamson wrote: > > [...] > > > BTW, the email seems kind of weird. There are lots of places where it > > >

Re: PDC replacement proposal

2023-09-04 Thread Adam Williamson
On Mon, 2023-09-04 at 22:26 +0200, Dominik 'Rathann' Mierzejewski wrote: > On Monday, 04 September 2023 at 17:37, Adam Williamson wrote: > [...] > > BTW, the email seems kind of weird. There are lots of places where it > > seems like it's referring to external information - "as demonstrated > >

Re: PDC replacement proposal

2023-09-04 Thread Dominik 'Rathann' Mierzejewski
On Monday, 04 September 2023 at 17:37, Adam Williamson wrote: [...] > BTW, the email seems kind of weird. There are lots of places where it > seems like it's referring to external information - "as demonstrated > here", "Previously, we followed this process to update it, but now we > have

Re: PDC replacement proposal

2023-09-04 Thread Adam Williamson
On Mon, 2023-09-04 at 16:51 +0200, Tomas Hrcka wrote: > > Current uses of PDC: > >1. > >Critical Path Package Tracking: Bodhi leverages PDC to track packages on >the critical path. > > /rest_api/v1/component-branches/: Specifically, Bodhi will handle the > critical-path flag. > >

PDC replacement proposal

2023-09-04 Thread Tomas Hrcka
Hello all, it took us a few years but we are finally getting rid of the PDC project. Thanks to the ARC research we identified use cases in our tooling and proposed solution. The essential functionalities currently provided by PDC will be re-implemented in other applications within our release