On 19 June, 2015, at 23:26, Cliff Perry <cpe...@redhat.com> wrote:
we agreed today that this makes sense for Spacewalk. […]
Great!
We would like you to reach out to the main spacewalk users list, ensure that
they are aware of what will change/break and get input, try to ensure we know
the alternatives, if required.
Sure, no problem.
I suspect that work should be done either in a public branch or via a long
running pull request.
Spacewalk developers: which one do you prefer? I propose a PR, as it is easier
to leave comments and discuss. I would label it as [WIP] in the title until we
think it’s safe for a final review before merging.
Ideally we'd try to have builds testable before it hits nightly.
That would help us a lot as well. Unfortunately, I have basically no idea on
how to implement it - I hope you guys can help.
When it does hit nightly, we have users on nightly, react in a timely manner to
issues raised and ensure users are aware before it hits nightly. Same for when
next Spacewalk is released with this code changes. Being responsive to posts on
the changes to the users list. […]
Sure, we will do our best to fix all reported regressions.
Thanks,
--
Silvio Moioli
SUSE LINUX Products GmbH
Maxfeldstraße 5, 90409 Nürnberg Germany
--
Silvio Moioli
SUSE LLC
Maxfeldstraße 5, 90409 Nürnberg Germany
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
