This page is intended to gather feedback from the Fedora community on things that worked well and things that could have been better during the Fedora 21 release cycle. The feedback will be used as a basis for identifying areas for improvement for Fedora 22 and could weigh into the Fedora 22 Schedule. Any thoughts, big or small, are valuable. If someone already provided feedback similar to what you'd like to add, don't worry ... add your thoughts regardless.
Several different Fedora teams have their own retrospective process. See:
- Kevin Fenzi - I liked that we made a retrospective wiki page.
Adding feedback is fairly straight forward. If you already have a Fedora account ...
- Login to the wiki
- Select [Edit] for the appropriate section below.
- Add your feedback using the format:
* ~~~ - I like ____ about the new ____ process
- When done, Submit your changes
Things that went well
- Sudhir Khanger - Every single release whether alpha, beta, RC, etc.they all worked flawlessly and were very stable. Kudos to developers, maintainers and the hard work done by the QA team.
- M. Edward (Ed) Borasky - I was impressed by how quickly the bugs I found in building my remix were fixed.
Could have been better
- M. Edward (Ed) Borasky - The documentation for Fedora Cloud, especially Project Atomic was "typical of a young project". I think it could be better.
- Sudhir Khanger - I get the reasons why OpenJDK 7 had to be dropped from Fedora 21 but dropping something because it goes EOL before the EOL of the release is not the best way to accomplish the goals.
- M. Edward (Ed) Borasky - If this is 'wishes for F22', my fondest wish is for some kind of architectural / software mechanism for seamlessly integrating the various language packaging systems on a Fedora core. Just about every Python developer I know has a mix of "native" Linux packages and packages living in a virtualenv installed with 'pip'. In my case, I'm installing R from Fedora (or Ubuntu or openSUSE) but installing the packages from CRAN or even from source repositories via 'devtools'. And don't get me started on Node.js / npm. ;-) This is error-prone and hard to reproduce / maintain / document.