Being the sole maintainer for about a year, there is no formal review
process.
There is a jenkins server, which I use to test all pull requests before
merging them in. This currently also tests any commits made to the master
and release24 branches.
Looking forward to seeing patches come in :)
On Mon, Nov 18, 2013 at 10:29 AM, Alan Evangelista <
alanoe(a)linux.vnet.ibm.com> wrote:
Hi.
My name is Alan Evangelista, I am considering to create a fork of Cobbler
to customize it.
If I do so, my team would periodically send patches upstream when they
make sense to the open source community.
I'd like to ask some questions about the project development process:
- You do code review in Github? I see the commits in Github, but I dont
see code reviews. What is the code review process?
- I see pyunit tests in tests/ dir in Cobbler Git repository. Is there any
sort of continuous testing/integration tool/process or the
developers/maintainers manually run the tests before pushing/merging?
Regards,
Alan Evangelista
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel