engine GUI (webadmin/userportal) is currently communicating with the engine-core (backend) via the legacy backend api; the GUI consumes this api via a GWT RPC servlet. We would like to: (1) stop GUI communication with the legacy backend api and start working with the "official" engine api (exposed via the rest api). (2) stop working with GWT RPC as our transport layer and simply work with direct requests to the engine's rest api (via an engine javascript SDK). more details here: http://www.ovirt.org/Features/Design/Using_REST_API_In_Web_UI
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant.
(In reply to Sandro Bonazzola from comment #1) > This is an automated message. > This Bugzilla report has been opened on a version which is not maintained > anymore. > Please check if this bug is still relevant in oVirt 3.5.4. > If it's not relevant anymore, please close it (you may use EOL or CURRENT > RELEASE resolution) > If it's an RFE please update the version to 4.0 if still relevant. not sure why I've received this message, as this RFE is already targeted for 4.0.0 since April 2015. @Sandro - worth checking the script. Thanks.
(In reply to Einav Cohen from comment #2) > (In reply to Sandro Bonazzola from comment #1) > > This is an automated message. > > This Bugzilla report has been opened on a version which is not maintained > > anymore. > > Please check if this bug is still relevant in oVirt 3.5.4. > > If it's not relevant anymore, please close it (you may use EOL or CURRENT > > RELEASE resolution) > > If it's an RFE please update the version to 4.0 if still relevant. > > not sure why I've received this message, as this RFE is already targeted for > 4.0.0 since April 2015. @Sandro - worth checking the script. Thanks. This bug Target Version is 4.0 but it has been opened on 3.4 version and version field still points to 3.4 which is not supported anymore. Please consider moving that to 4.0 too.
(In reply to Sandro Bonazzola from comment #3) > > This bug Target Version is 4.0 but it has been opened on 3.4 version and > version field still points to 3.4 which is not supported anymore. > Please consider moving that to 4.0 too. a version that is not supported anymore is a version to which BZs cannot be *targeted* to. The fact that the BZ was reported in a version that is not supported anymore doesn't mean that it should not be fixed, so I don't think that such BZs are good candidates for closing; good candidates for closing are e.g. BZs that did not have any activity on them for a long time. If a user has found an issue in a certain version, then that's the Version that should be filled in the BZ - I don't think that it should be changed at any point in time. Moreover, let's say that a reporter tests the issue in the current version and then changes the BZ's Version accordingly as you suggest; once this BZ will be assigned to someone, the BZ assignee may think that this issue is much more recent than it really is, which may confuse him when coming to determine the root cause of the issue. I think that BZs should stay in the Version they were reported in. What reporters can do is see if the issue still reproduces in the current version, and then close the BZ if it doesn't, or put a comment like "still reproducible on 3.6" if it is - but not change the Version, or close on EOL.
(In reply to Einav Cohen from comment #4) I'm not going to enforce this in anyway, I'll just point you to https://bugzilla.redhat.com/page.cgi?id=fields.html#version "If bug report is a feature request, set it to the version you would like to see problem fixed in." I can't find a reference to the policy used by Fedora, but you can take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1021310#c2 and see that bug with version 20 has been closed eol, without having set a target version. The close message says: "Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version." so, changing version is common practice.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
closing for now. will re-open if necessary.