From Fedora Project Wiki

Revision as of 09:54, 14 February 2014 by Red (talk | contribs) (Brainstorming: clarified by Dennis Gilmore: we already do have nightly builds for months)


Remove this section as ideas are put into a more structured form (or discarded).

  • Retire appliance-creator
    • Anaconda-based installs are the way forward
      • Needs new ImageFactory release
      • Patch Koji for ImageFactory support
      • Then, needs new Koji release
      • Then, push new Koji release to Fedora production
  • Extend AutoQA to allow for automated testing of cloud images (if not already possible)
  • Automate rel-eng
    • produce scratch builds on change (note: we already have nightly images of rawhide and branched compose for months)
    • upload final release and re-release images to ec2 and ftp
  • Updated Web Site for Obtaining Cloud Images
    • Easier access to provided images for various use cases
    • Provide build toolchain
    • encourage community to use toolchain to build new products
    • Allow folks to share and review the work done by their peers
  • Implement new procedures for (a)periodical re-releases
  • Ensure usability of software stacks for cloud usage
    • Always have several different versions (major or minor releases, i.e. non-bugfix releases) ready for installation
    • Make sure older versions are supported and available as long as possible, particularly with new Fedora releases
      • i.e. apps running on F21 cloud images should still be able to run on F22 cloud images (and F23? How long should they work?)
  • More modularly-packaged kernel (modules that are not necessary in virtualized environments need become optionally installable)
  • More modularly-packaged (or written?) SELinux policies
  • Make it possible to install without l10n/i18n support (no extra languages, etc.) but keep the possibility to install them
  • Make it possible to install packages without documentation (to save space) but keep the possibility to install them