[Pulp-dev] Re-downloading Corrupted Content (solving bit rot)

[Brian Bouterse]

A feature is being discussed on re-downloading corrupted content. There are
some questions about how to position the API, the locking, and how it
interacts with repo versions that allow 404 errors to still complete a repo
version.

Questions posted here: https://pulp.plan.io/issues/5613#note-3 Please
respond if you have input.

I think this will get implemented soonish, e.g. pulpcore==3.2.0, so having
the full design complete by the end of Jan would be ideal.

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

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Applicability
   -

  Summary of the discussion w/ Katello about ownership of applicability
  feature
  -

  AI: [ggainey] check in with jsherrill RE moving applicability
  discussion to pulp-dev
  -

   Copy
   -

  https://hackmd.io/OIIpE4GUTXKYoQa8lRMgww?view
  -

  AI: meeting with Katello to finalize details

  -

   Review of the remaining (medium to small) RPM features


Pulp 2:

   -

   Z release
   -

  Fixes https://bit.ly/2RcWG56
  -

  Ina volunteered to be a release shepherd


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Sprint 64 minutes

[Robin Chan]

*10-Jan-2020Sprint 64 query: https://pulp.plan.io/issues?query_id=142
Stats on how we did in previous 2
week  Sprint 63 Query : New -
12 Assigned - 7 Post - 9 Modified - 19Closed - NOTABUG - 1Closed - COMPLETE
- 3Closed - CURRENTRELEASE - 22Closed - NOTABUG - 1Closed - WORKSFORME -
2Action Items from last Sprint Planning - N/A - rchan knows all were
resolvedDates:https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans
Sprint Goals/Focus: -
Support of Automation Hub’s work to port to a Pulp plugin (over next ~2
sprints/1 month) - Z-stream updating and y-stream upgrades in ansible-pulp,
including CI. - 3.1. Are we still
planning for end of January?- Yes, targeting release of Jan 30th-
https://pulp.plan.io/issues?query_id=145
- 3.2 - End of Feb- DemosOther
things happening during the sprint (including outages) - January 24-26
(Fri-Sun): DevConf - Conference prep for FOSDEM & ConfigMgmtCurrent
sprint:Anything not moving forward?https://pulp.plan.io/issues?query_id=124
 1. #2220 - Move to modified
(Ina)2. https://pulp.plan.io/issues/5449 
- pulp 2 item, ask katello on priority3. #5642 - not enough capacity4.
#5879 - not enough capacity now, 6.6.1 issueSprint
candidates:https://pulp.plan.io/issues?query_id=26
Pending Items: - Features in
planning and anticipated to be added before the end of the sprint. - none*









*Action Items: - rchan: Clear Sprint Candidate
https://pulp.plan.io/issues?query_id=26
 - 4891- 2946- 4967- 5066- 5122-
5212- 5096- 4664- 4666 - rchan: send out planning minutes - Move new,
assigned, post issues to new sprint- https://pulp.plan.io/issues/5449
 - pulp 2 item, ask katello on priority-
#5879 - not enough capacity now, 6.6.1 issue - need to get this connected
to a bz?*


Robin Chan

She/Her/Hers

Satellite Software Engineering Manager - Pulp

Red Hat 

IRC: rchan

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