As we rapidly hit the last days of Fedora 26 development, the final notches of planning for what Release Engineering can get done in Fedora 27 is coming together. Our priorities are mostly sorted, and we are marking things to target for Fedora 28.
Release Engineering has its backlog in a Taiga instance that is hosted in the fedora infrastructure cloud. As you can see the backlog is very full. We have a limited number of people Mohan, Adam, Randy, Patrick, and Rob have very full plates with day to day work and getting new features done as possible, Kevin and myself do what we can to assist. If there is something you really want to see working with us to get it scoped and getting it implemented ensures the best chance of success.
My role within releng has changed over the last few months, Fedora is no longer my only responsibility, I am now the team lead for Platform Release Engineering inside of Red Hat, I oversee Fedora and RHEL as a result I am less hands on in the day to day doing things. I ran one compose in Fedora 25 and so far in Fedora 26 I have yet to run a production compose. As a result if you ping me directly asking for input I will redirect you to file an issue in pagure, or to mail the releng mailing list, this is not because I do not want to help, but because I want to remove myself as a single point of failure in getting things done. Of course if you feel you are not getting a responsive or appropriate answer please ping and engage with me so I can help resolving the issue.
Source From: fedoraplanet.org.
Original article title: Dennis Gilmore: What is going on in Fedora Release Engineering.
This full article can be read at: Dennis Gilmore: What is going on in Fedora Release Engineering.