On Wednesday, September 21, 2016 2:57:03 PM CEST Miroslav Suchý wrote:
> Dne 21.9.2016 v 12:52 Pavel Raiskup napsal(a):
> > Thanks, I'll subscribe there. Let's hope I'll be able to find good
> > heuristic to pick important changes for review -- but unfortunately, I can
> > not review everything. Is there possibility to highlight important
> > changes?
> Define "important changes" :)
:) Consider that others consume Copr sources ...
> What is important for me is not important for you and vice versa.
... and have Copr working, want to have it as stable as possible, and are
planning regular updates with new releases. So to answer your question:
Whatever could complicate updating is worth having a look (by other consumers)
whether it is (a) necessary, (b) shouldn't be made optional; or (c) at worth
study hard how to re-configure properly.
Typical "hint" can be:
- "you have to hack something on XX (backend e.g)" because you changed something
on "YY (e.g. dist git)", and whetever else component.
- API changes, copr client should detect that server supports older API
- You need to change deployment scripts, others will need this too
- you put requirement on software that is not in base Fedora repo, be that yum
repo or other software repo ... (like dockerhub)
Yup, it is on my TODO list to make the upstream packages usable for me too
(because otherwise it is real pain), but so far (except for client side) I need
to re-build the packages with downstream patches. If there was something
docker-related, I would have to rebuild the images probably too...
copr-devel mailing list -- firstname.lastname@example.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org