Bug 817356
Summary: | vala-0.17.0 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | vala | Assignee: | Michel Lind <michel> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | michel, zeenix |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-04 09:27:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Upstream Release Monitoring
2012-04-29 11:02:56 UTC
You probably already know but just to be sure, 0.17.x is the new unstable release cycle so it should only go into rawhide. Certainly. And I should note that there is a compatibility 0.14 package that's been awaiting review -- https://bugzilla.redhat.com/show_bug.cgi?id=787193 I was thinking we could have a 'compat-vala' package that always tracks whatever the previous API is, relative to whatever the default API release is for a given Fedora / EPEL target. 0.17.0-1.fc18 built for Rawhide |