Adding reviewing to our development process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,

As I've been slowly getting into anaconda development I've become increasingly amazed with the number of regressions we have caused by typos and other small predictable errors in day to day development work.

So I've been thinking that we really need to change our processes to include a review phase for all patches except the most trivial ones (the ones fixing all the typos).

This blog post was the trigger for me to stop just thinking about this and actually write a mail about it:
http://anholt.livejournal.com/39921.html

I would like to invite you all to read this post, esp. those who are going to say no against my proposal to start doing more reviews as part of anaconda development.

Regards,

Hans

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux