Re: [Pulp-dev] Documentation issues

[Grant Gainey]

GMTA, was thinking about exactly this over the weekend. Even we don't/can't
declare a "Doc Day" (which I think is a fine idea, but I know how schedules
are right now...), being intentional about "I will assign one doc-issue to
myself and get a PR submitted by COB Friday" would knock a bunch of issues
out that have been waiting around for quite some time.

Thanks for writing this up, Ina!

G

On Mon, Aug 3, 2020 at 7:30 AM Ina Panova  wrote:

> Folks,
> I noticed that currently on the sprint we have roughly ~10 issues with
> Documentation tag. Some of them have been carried over multiple sprints and
> probably realistically still will be carried over.
>
> What do you think about dedicating a day and knock them down?
> It will roughly be an issue per person. I am not suggesting to dedicate
> whole 8 hours but let's say setting a goal for every team member for that
> day:"Today I am going to prioritize docs issues and knock down at least one
> documentation issue and submit a PR"
>
> Please provide feedback, and if the team feels like this 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."
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>


-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] pulp-2-to-3-migration pins the wrong pulpcore version?

[Evgeni Golov]

Thanks Таня!

The deps look correct now, I'll package it and we'll see if anything explodes :)

On Mon, Aug 3, 2020 at 2:07 PM Tatiana Tereshchenko  wrote:
>
> 0.2.0b7 is out with the fixed pulpcore version. Please try it out.
>
> Tanya
>
> On Mon, Aug 3, 2020 at 12:11 PM Tatiana Tereshchenko  
> wrote:
>>
>> It's not intentional, let me fix it.
>>
>> Tanya
>>
>> On Mon, Aug 3, 2020 at 11:46 AM Evgeni Golov  wrote:
>>>
>>> Ohai,
>>>
>>> in 
>>> https://github.com/pulp/pulp-2to3-migration/commit/43c2f10b9590a9886f2492614c48e527956873c1
>>> 2to3 got a hard pin on pulpcore 3.4, which means it can't be used with
>>> 3.4.1 which is the latest version in the 3.4 branch and what we have
>>> currently in Katello packaging.
>>>
>>> Is this pin intentional? Or should it be >=3.4,<3.5 (or ~= 3.4)?
>>>
>>> If it's intentional, we'll have to downgrade pulpcore for Katello :(
>>>
>>> Evgeni
>>>
>>> --
>>> Beste Grüße/Kind regards,
>>>
>>> Evgeni Golov
>>> Senior Software Engineer
>>> 
>>> Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn,
>>> Handelsregister: Amtsgericht München, HRB 153243,
>>> Geschäftsführer: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas 
>>> Savage
>>>
>>>
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev



-- 
Beste Grüße/Kind regards,

Evgeni Golov
Senior Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn,
Handelsregister: Amtsgericht München, HRB 153243,
Geschäftsführer: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage


___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] pulp-2-to-3-migration pins the wrong pulpcore version?

[Tatiana Tereshchenko]

0.2.0b7 is out with the fixed pulpcore version. Please try it out.

Tanya

On Mon, Aug 3, 2020 at 12:11 PM Tatiana Tereshchenko 
wrote:

> It's not intentional, let me fix it.
>
> Tanya
>
> On Mon, Aug 3, 2020 at 11:46 AM Evgeni Golov  wrote:
>
>> Ohai,
>>
>> in
>> https://github.com/pulp/pulp-2to3-migration/commit/43c2f10b9590a9886f2492614c48e527956873c1
>> 2to3
>> 
>> got a hard pin on pulpcore 3.4, which means it can't be used with
>> 3.4.1 which is the latest version in the 3.4 branch and what we have
>> currently in Katello packaging.
>>
>> Is this pin intentional? Or should it be >=3.4,<3.5 (or ~= 3.4)?
>>
>> If it's intentional, we'll have to downgrade pulpcore for Katello :(
>>
>> Evgeni
>>
>> --
>> Beste Grüße/Kind regards,
>>
>> Evgeni Golov
>> Senior Software Engineer
>> 
>> Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn,
>> Handelsregister: Amtsgericht München, HRB 153243,
>> Geschäftsführer: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas
>> Savage
>>
>>
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Documentation issues

[David Davis]

+1 from me as well. I'd suggest a day after 3.6 (August 11th) though as I
probably won't have time until after then.

David


On Mon, Aug 3, 2020 at 7:40 AM Matthias Dellweg  wrote:

> I like the idea.
>
> On Mon, Aug 3, 2020 at 1:30 PM Ina Panova  wrote:
> >
> > Folks,
> > I noticed that currently on the sprint we have roughly ~10 issues with
> Documentation tag. Some of them have been carried over multiple sprints and
> probably realistically still will be carried over.
> >
> > What do you think about dedicating a day and knock them down?
> > It will roughly be an issue per person. I am not suggesting to dedicate
> whole 8 hours but let's say setting a goal for every team member for that
> day:"Today I am going to prioritize docs issues and knock down at least one
> documentation issue and submit a PR"
> >
> > Please provide feedback, and if the team feels like this 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."
> > ___
> > Pulp-dev mailing list
> > Pulp-dev@redhat.com
> > https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Documentation issues

[Matthias Dellweg]

I like the idea.

On Mon, Aug 3, 2020 at 1:30 PM Ina Panova  wrote:
>
> Folks,
> I noticed that currently on the sprint we have roughly ~10 issues with 
> Documentation tag. Some of them have been carried over multiple sprints and 
> probably realistically still will be carried over.
>
> What do you think about dedicating a day and knock them down?
> It will roughly be an issue per person. I am not suggesting to dedicate whole 
> 8 hours but let's say setting a goal for every team member for that 
> day:"Today I am going to prioritize docs issues and knock down at least one 
> documentation issue and submit a PR"
>
> Please provide feedback, and if the team feels like this 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."
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev


___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Documentation issues

[Ina Panova]

Folks,
I noticed that currently on the sprint we have roughly ~10 issues with
Documentation tag. Some of them have been carried over multiple sprints and
probably realistically still will be carried over.

What do you think about dedicating a day and knock them down?
It will roughly be an issue per person. I am not suggesting to dedicate
whole 8 hours but let's say setting a goal for every team member for that
day:"Today I am going to prioritize docs issues and knock down at least one
documentation issue and submit a PR"

Please provide feedback, and if the team feels like this 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."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] pulp-2-to-3-migration pins the wrong pulpcore version?

[Tatiana Tereshchenko]

It's not intentional, let me fix it.

Tanya

On Mon, Aug 3, 2020 at 11:46 AM Evgeni Golov  wrote:

> Ohai,
>
> in
> https://github.com/pulp/pulp-2to3-migration/commit/43c2f10b9590a9886f2492614c48e527956873c1
> 2to3
> 
> got a hard pin on pulpcore 3.4, which means it can't be used with
> 3.4.1 which is the latest version in the 3.4 branch and what we have
> currently in Katello packaging.
>
> Is this pin intentional? Or should it be >=3.4,<3.5 (or ~= 3.4)?
>
> If it's intentional, we'll have to downgrade pulpcore for Katello :(
>
> Evgeni
>
> --
> Beste Grüße/Kind regards,
>
> Evgeni Golov
> Senior Software Engineer
> 
> Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn,
> Handelsregister: Amtsgericht München, HRB 153243,
> Geschäftsführer: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas
> Savage
>
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] pulp-2-to-3-migration pins the wrong pulpcore version?

[Evgeni Golov]

Ohai,

in 
https://github.com/pulp/pulp-2to3-migration/commit/43c2f10b9590a9886f2492614c48e527956873c1
2to3 got a hard pin on pulpcore 3.4, which means it can't be used with
3.4.1 which is the latest version in the 3.4 branch and what we have
currently in Katello packaging.

Is this pin intentional? Or should it be >=3.4,<3.5 (or ~= 3.4)?

If it's intentional, we'll have to downgrade pulpcore for Katello :(

Evgeni

-- 
Beste Grüße/Kind regards,

Evgeni Golov
Senior Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn,
Handelsregister: Amtsgericht München, HRB 153243,
Geschäftsführer: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage


___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev