On 09/12/2018 01:57 PM, Doug Hellmann wrote:
Excerpts from Ben Nemec's message of 2018-09-12 13:51:16 -0600:
On 09/04/2018 06:49 PM, Matt Riedemann wrote:
On 9/4/2018 6:39 PM, Ben Nemec wrote:
Would it be helpful to factor some of the common code out into an Oslo
library so projects
On 4/09/18 5:39 PM, Ben Nemec wrote:
Would it be helpful to factor some of the common code out into an Oslo
library so projects basically just have to subclass, implement check
functions, and add them to the _upgrade_checks dict? It's not a huge
amount of code, but a bunch of it seems like it
Excerpts from Ben Nemec's message of 2018-09-12 13:51:16 -0600:
>
> On 09/04/2018 06:49 PM, Matt Riedemann wrote:
> > On 9/4/2018 6:39 PM, Ben Nemec wrote:
> >> Would it be helpful to factor some of the common code out into an Oslo
> >> library so projects basically just have to subclass,
On 09/04/2018 06:49 PM, Matt Riedemann wrote:
On 9/4/2018 6:39 PM, Ben Nemec wrote:
Would it be helpful to factor some of the common code out into an Oslo
library so projects basically just have to subclass, implement check
functions, and add them to the _upgrade_checks dict? It's not a huge
On 9/4/2018 6:39 PM, Ben Nemec wrote:
Would it be helpful to factor some of the common code out into an Oslo
library so projects basically just have to subclass, implement check
functions, and add them to the _upgrade_checks dict? It's not a huge
amount of code, but a bunch of it seems like it
Excerpts from Ben Nemec's message of 2018-09-04 18:39:35 -0500:
> Would it be helpful to factor some of the common code out into an Oslo
> library so projects basically just have to subclass, implement check
> functions, and add them to the _upgrade_checks dict? It's not a huge
> amount of
Would it be helpful to factor some of the common code out into an Oslo
library so projects basically just have to subclass, implement check
functions, and add them to the _upgrade_checks dict? It's not a huge
amount of code, but a bunch of it seems like it would need to be
copy-pasted into
