I'm sending out the minutes to help @mikedep333 who is off today
*Minutes*
-
Installer having a dedicated project in Redmine?
-
Create a new query for triage that disincludes issues with ‘Pulp 3
installer’ tag.
-
Add a public query that shows all issues with
At today's installer meeting, the installer team agreed to:
* keep the installer items in the pulpcore Redmine and not have a separate
Redmine for it
* Add a Component named 'Installer'. New installer items should be filed
with that component set. [done]
* A new saved query has been created to
Melanie,
I'm sending via pulp-dev for more visibility, but I wanted to see what you
think specifically. Recently a user gave us feedback via an issue on Pulp 3
pain points for usage [0]. A lot of it is code and docs, and we're working
to address those, but the last bullet says:
"On the project
I have a small suggestion.
Besides the documentation plan I would suggest to catch the exception
thrown on server disconnect and give to the users something more friendly
and not have that traceback in the logs.
Regards,
Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.
"Do not go
May 13, 2020
-
CI status check
-
Lots of failures due to new flake8 release
-
plugin_template migrated to travis-ci.com. I (david) forgot to migrate
it before.
-
Should we move the linting facilities of plugin_template into the
“travis” section, or in a
