[Pulp-dev] scrum status

2021-01-26 Thread Tanya Tereshchenko
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] after all the
changes and discussions

* Pulp 2to3 Migration
 - added batching to a pulp2 query and gave Justin a patch [3] to test
 - started looking at the CI failures where one task is cancelled

 * Other
 - reviewed Melanie's videos, great job, mcorr++
 - company meeting
 - go/no-go for 3.10
 - open floor
 - opened a doc PR [4] to clarify some language around backport requests

[0] https://pulp.plan.io/issues/8161
[1] https://github.com/pulp/pulpcore/pull/1088
[2] https://github.com/pulp/pulp_container/pull/212
[3] https://github.com/pulp/pulp-2to3-migration/pull/298
[4]
https://github.com/pulp/pulpcore/pull/1089https://github.com/pulp/pulpcore/pull/1089
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


Re: [Pulp-dev] scrum status

2021-01-26 Thread Tanya Tereshchenko
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, opened a
> PR [1]
>  - RBAC meeting with container mini-team
>  - revisited and adjusted the repo versions RBAC PR [2] after all the
> changes and discussions
>
> * Pulp 2to3 Migration
>  - added batching to a pulp2 query and gave Justin a patch [3] to test
>  - started looking at the CI failures where one task is cancelled
>
>  * Other
>  - reviewed Melanie's videos, great job, mcorr++
>  - company meeting
>  - go/no-go for 3.10
>  - open floor
>  - opened a doc PR [4] to clarify some language around backport
> requests
>
> [0] https://pulp.plan.io/issues/8161
> [1] https://github.com/pulp/pulpcore/pull/1088
> [2] https://github.com/pulp/pulp_container/pull/212
> [3] https://github.com/pulp/pulp-2to3-migration/pull/298
> [4]
> https://github.com/pulp/pulpcore/pull/1089https://github.com/pulp/pulpcore/pull/1089
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] Scrum status

2018-11-16 Thread David Davis
- Reviewed https://github.com/pulp/pulp/pull/3757
- 6.5 scrum with Katello
- Responded question about marketing expenses for AnsibleFest
- Meeting with legal about licensing
- Ran triage
- Meeting about single content
- Updated https://github.com/pulp/pulp/pull/3756 based on feedback
- Discovered bug in pulp-smash tests and found reproducer
https://pulp.plan.io/issues/4170
- Opened PR to pin pulpcore-plugin
https://github.com/pulp/pulp_rpm/pull/1227
- Sent out email to update RPM team of beta status
- Paul Cormier AMA on RHEL
- Filled out four question surveys
- Set up vacation response

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


[Pulp-dev] Scrum status

2018-05-22 Thread David Davis
- Encountered another pulp 2 test failure and opened
https://pulp.plan.io/issues/3689
- Talked with some people and opened https://pulp.plan.io/issues/3690
- Scrum of scrums
- Triage
- CLI meeting
- Meeting with Katello about features
- 1x1 with @rchan
- Discussed worker indeterministic filtering on IRC and reviewed fix PR
- Worked on email to pulp-list for CLI feedback

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


[Pulp-dev] Scrum status

2018-04-23 Thread David Davis
Previous:
- Talked about planning out code bindings (python, ruby, etc) on IRC
- Reviewed and tested https://github.com/pulp/pulp/pull/3448
- Talked about handling pulp-smash plans with @bmbouter and @ogmaciel
- Added a bug around broken urls https://pulp.plan.io/issues/3556
- Reviewed https://github.com/pulp/pulp_ansible/pull/13
- Read up on Changeset proposal
- Added @dkliban to pulp_file team
- Looked at beaker FIPS recipe for running m2crypto.
- Started on https://pulp.plan.io/issues/3181

Today:
- Finished codecov setup for pulpcore
- Opened settings issue https://pulp.plan.io/issues/3589
- Read through @ttereshc’s notes on FIPS
from 6.5 planning meeting and responded
- Pulp team meeting
- Reviewed https://github.com/pulp/pulp_file/pull/75
- Pulp ansible check-in meeting
- Opened a small docs PR: https://github.com/pulp/pulp/pull/3463
- Responded to some questions on the thread about our build process
- Worked on demo video for distribution overlap checking in Pulp 3
- Addressed feedback on pulp_ansible upload PR
https://github.com/pulp/pulp_ansible/pull/14
- Opened an fix for get_resource() based on a found bug
https://github.com/pulp/pulp/pull/3468

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


Re: [Pulp-dev] scrum status

2018-03-06 Thread Bihan Zhang
Whoops, wrong list

On Tue, Mar 6, 2018 at 4:51 PM, Bihan Zhang  wrote:

> 3/6/18
> - tracked down an answer to https://forums.suse.com/sho
> wthread.php?11748-What-happens-when-suse-erratum-is-updated&
> p=51367#post51367
> - SUSE does update errata in place, but they increment version
> attribute in the erratum
> - will work on this tomorrow, after @ttereshc checks in with rcm to
> make sure this is ok for rh errata
> - Container source scrum
> - amended #3377 PR [0]
> - continue reading through container source design documents
>
> 3/5/18
> - Team meeting
> - Docker meeting
> - Python meeting
> - #3377
> - read through some details for RCM project- it's not pulp related \o/
> mostly python scripting to make source code in container images available
>
> [0] https://github.com/pulp/pulp_rpm/pull/1088
>
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] scrum status

2018-03-06 Thread Bihan Zhang
3/6/18
- tracked down an answer to https://forums.suse.com/sho
wthread.php?11748-What-happens-when-suse-erratum-is-updated&
p=51367#post51367
- SUSE does update errata in place, but they increment version
attribute in the erratum
- will work on this tomorrow, after @ttereshc checks in with rcm to
make sure this is ok for rh errata
- Container source scrum
- amended #3377 PR [0]
- continue reading through container source design documents

3/5/18
- Team meeting
- Docker meeting
- Python meeting
- #3377
- read through some details for RCM project- it's not pulp related \o/
mostly python scripting to make source code in container images available

[0] https://github.com/pulp/pulp_rpm/pull/1088
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] Scrum status

2018-02-13 Thread David Davis
Previously:
- Pulp team meeting
- Set up Friday meeting with QE to talk through testing Pulp 3
- Discussed pulp-file publishing and dealing with dupe units with @jortel
- Updated PR to prevent duplicate content units based on some feedback from
@jortel [1]
- Reviewed pulp-file roadmap [2]
- Continued on multi-locking issue [3]
- Worked on Walmart 404 issue
- Discussed handling 2.15.2 release on IRC with @bmbouter and @pcreech
- Helped @kersom with some pulp 3 tests and test plans
- Found a bug with sphinx 1.7 [4]

Today:
- Triage
- Discussed how to simplify the pulp_file plugin with @jortel
- Reviewed @bmbouter’s trip report for the plugin coding workshop
- Helped track down kombu version for @dalley
- Prepare for demo
- Updated dupe content unit PR [1]
- 1x1 with @rchan
- Looked through walmart’s mongostat log and requested reporting on a
second instead of min basis

Also, I am AFK from 3:30-4:00pm. I have to go to the tire shop to pick up
my car.

[1] https://github.com/pulp/pulp/pull/3318
[2] https://pulp.plan.io/projects/pulp/wiki/File_Plugin_Roadmap
[3] https://pulp.plan.io/issues/3186
[4] https://pulp.plan.io/issues/3355

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


[Pulp-dev] scrum status

2018-02-01 Thread Brian Bouterse
Monday:
- helping to groom #3324 [0]
- made an epic to track running Pulp2 on Debian [1]
- talking w/ @daviddavis about ansible plugin
- hand testing patch from @dalley [2]. lgtm after some rounds of feedback.
- catching up on other emails
- wrote first half of devconf.cz report
- listened to info from @dalley about credit suisse case

Tuesday:
- talking w/ @ttereshc about credit suisse issue
- organized plugin writer notes from the workshop and closed issue 854 [3]
- finish and send devconf.cz report
- SoS and setup time to talk w/ mkubik about upstream/downstream
- meet w/ @asmacdo to go over the recent context manager design

Wednesday:
- meet w/ CDT to discuss a gpg signing need and a Pulp3 review.
- talk w/ @mkubik to discuss the choice of a RHUI issue tracker and share
some onboarding of upstream processes
- pulp team meeting
- discuss w/ devs about using a Facade/Controller for RepositoryVersion or
not
- reply to jturel about downstream inclusion of a newer gofer to resolve a
500 error

Blockers: none

[0]: https://pulp.plan.io/issues/3324
[1]: https://pulp.plan.io/issues/3325
[2]: https://github.com/pulp/pulp/pull/3283
[3]: https://pulp.plan.io/issues/854
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] scrum status

2018-01-22 Thread Austin Macdonald
Last week:
 - https://pulp.plan.io/issues/3222
 - https://pulp.plan.io/issues/3260
 - High level design https://pulp.plan.io/issues/3309
 - Demo of ^
 - Context manager planning with jortel
 - PR Review

Today:
 - Take (for dkliban) https://pulp.plan.io/issues/3221
 - Take (for dkliban) https://pulp.plan.io/issues/3296
 - Review Ansible proposal and comment
 - If time, continue with https://pulp.plan.io/issues/3294
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] Scrum status

2017-06-12 Thread David Davis
Previously:
- Continue working on hammer csv PR [1]
  - Change flags to allow for both --no-publish and --publish
  - Add validation for options
  - Fixed output problem @akofink found
  - Merged PR
- Followed up on which release to target hammer-cli-csv bug fixes/features
in Bugzilla
- Retrospective and triage

Today:
- Helping @orabin with Clydesdale bug involving refreshing manifests
- Followed up on PUP-3 discussion on mailing list
- Started a new discussion around what “obvious consensus” means in PUP-1
on mailing list
- Trying to setup a pulp 3.0 dev environment but am hitting an error during
vagrant up [2]
- Team meeting
- Field eng scrum

[1] https://github.com/Katello/hammer-cli-csv/pull/159
[2] https://gist.github.com/daviddavis/dd857b2fe11807145b83b5c318fac08b

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