Fedora Remix maintained by the Rochester Institute of Technology (RIT) Linux Users Group, targeted at users new to Linux and RIT students, faculty, and staff
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

29 lines
1.5 KiB

7 years ago
  1. This document provides information about where we are right now and where I'd
  2. like to go. Eventually there will be information about how to make tarball
  3. releases and update the generic-release packages.
  4. Currently I have just imported the (extracted) tarball from fedora 20. We
  5. currently don't have a build for rawhide with a version of 21. This is
  6. the top priority.
  7. fedora-release has some features that would be nice to get into
  8. generic-release, in particular the arch mapping that associates the
  9. correct keys for different architecures.
  10. The package version needs to match the fedora release (unless we switch
  11. over to just relying on the system-release(release) provides, but that
  12. seems to be premature now), but I'd like to allow multiple tarballs
  13. for a single release (to add features or keys) with different versions.
  14. My thought on this was to use a major.minor version, where major is the
  15. fedora release version and would be used for the package version. Minor
  16. would just end up in the package release.
  17. I don't want to build new tarballs to cover spec file changes that are
  18. just configuration or changelog updates. I prefer to not keep changelog
  19. updates in this repo, as changes to the spec file will be documented
  20. in git. When changes are incorporated into packages, important notes
  21. from the git log, can be added to the changelog.
  22. While there is currently just a master branch, the plan is to add a new
  23. branch each time Fedora is branched. I don't think we'll go back and
  24. add branches before f21.