https://bugzilla.redhat.com/show_bug.cgi?id=1269649
--- Comment #9 from Antonio Trande <[email protected]> --- >So even if there is no active development, there is a valid upstream and the >>possibility to get my build- and bug fix merged into upstream. > >There is still the option to fork the repo if it is easier to handle. Good point of start. >Release: 0.21beta1%{?dist} If yours is a 0.2.2 pre-release, you should change Release tag like 0.%{X}.%{alphatag}%{?dist} Where %{X} is the release number increment, and %{alphatag} is the string that came from the version. In this case, the period '.' is used as the delimiter between the release number increment, and the non-numeric version string. http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_packages -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/package-review
