Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
View all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
Accelerator
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Type
/
to search
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading.
Please reload this page
.
dapperlinux
/
dapper-release
Public
Notifications
You must be signed in to change notification settings
Fork
0
Star
0
Code
Issues
0
Pull requests
0
Actions
Projects
Security and quality
0
Insights
Additional navigation options
Code
Issues
Pull requests
Actions
Projects
Security and quality
Insights
Files
Expand file tree
master
Breadcrumbs
dapper-release
/
README.developers
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
29 lines (24 loc) · 1.49 KB
master
Breadcrumbs
dapper-release
/
README.developers
Copy path
Top
File metadata and controls
Code
Blame
29 lines (24 loc) · 1.49 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
This document provides information about where we are right now and where I'd
like to go. Eventually there will be information about how to make tarball
releases and update the generic-release packages.
Currently I have just imported the (extracted) tarball from fedora 20. We
currently don't have a build for rawhide with a version of 21. This is
the top priority.
fedora-release has some features that would be nice to get into
generic-release, in particular the arch mapping that associates the
correct keys for different architecures.
The package version needs to match the fedora release (unless we switch
over to just relying on the system-release(release) provides, but that
seems to be premature now), but I'd like to allow multiple tarballs
for a single release (to add features or keys) with different versions.
My thought on this was to use a major.minor version, where major is the
fedora release version and would be used for the package version. Minor
would just end up in the package release.
I don't want to build new tarballs to cover spec file changes that are
just configuration or changelog updates. I prefer to not keep changelog
updates in this repo, as changes to the spec file will be documented
in git. When changes are incorporated into packages, important notes
from the git log, can be added to the changelog.
While there is currently just a master branch, the plan is to add a new
branch each time Fedora is branched. I don't think we'll go back and
add branches before f21.
You can’t perform that action at this time.