|
From: <sv...@va...> - 2013-12-01 14:51:30
|
Author: philippe
Date: Sun Dec 1 14:51:21 2013
New Revision: 13742
Log:
Move bug fix announcement to the FIXED BUGS section
Modified:
trunk/NEWS
Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Sun Dec 1 14:51:21 2013
@@ -4,7 +4,6 @@
* ================== PLATFORM CHANGES =================
-328205 Implement additional Xen hypercalls
* ==================== TOOL CHANGES ====================
@@ -30,6 +29,7 @@
327238 Callgrind Assertion 'passed <= last_bb->cjmp_count' failed
327837 dwz compressed alternate .debug_info and .debug_str not read correctly
327916 DW_TAG_typedef may have no name
+328205 Implement additional Xen hypercalls
Release 3.9.0 (31 October 2013)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
From: Bart V. A. <bva...@ac...> - 2013-12-01 15:00:03
|
Hello Philippe, Can you explain why you made this change ? In other words, do you consider adding Xen hypercalls as a new feature or rather as a bug fix ? For me it doesn't matter whether or not a bug number has been assigned. What e.g. if a platform change would be requested as a wishlist item in the KDE bugzilla tracker ? Would the fact that a bug number has been assigned to a platform change be sufficient for you to conclude that it must be mentioned under "FIXED BUGS" and not under "PLATFORM CHANGES" ? Thanks, Bart. On 12/01/13 15:51, sv...@va... wrote: > Author: philippe > Date: Sun Dec 1 14:51:21 2013 > New Revision: 13742 > > Log: > Move bug fix announcement to the FIXED BUGS section > > > Modified: > trunk/NEWS > > Modified: trunk/NEWS > ============================================================================== > --- trunk/NEWS (original) > +++ trunk/NEWS Sun Dec 1 14:51:21 2013 > @@ -4,7 +4,6 @@ > > * ================== PLATFORM CHANGES ================= > > -328205 Implement additional Xen hypercalls > > * ==================== TOOL CHANGES ==================== > > @@ -30,6 +29,7 @@ > 327238 Callgrind Assertion 'passed <= last_bb->cjmp_count' failed > 327837 dwz compressed alternate .debug_info and .debug_str not read correctly > 327916 DW_TAG_typedef may have no name > +328205 Implement additional Xen hypercalls > > Release 3.9.0 (31 October 2013) > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Philippe W. <phi...@sk...> - 2013-12-01 19:18:46
|
On Sun, 2013-12-01 at 15:59 +0100, Bart Van Assche wrote: > Hello Philippe, > > Can you explain why you made this change ? In other words, do you > consider adding Xen hypercalls as a new feature or rather as a bug fix ? > For me it doesn't matter whether or not a bug number has been assigned. > What e.g. if a platform change would be requested as a wishlist item in > the KDE bugzilla tracker ? Would the fact that a bug number has been > assigned to a platform change be sufficient for you to conclude that it > must be mentioned under "FIXED BUGS" and not under "PLATFORM CHANGES" ? Hello Bart, The idea is that the FIXED BUGS contains all bugs that were reported in bugzilla and that are fixed/implemented. If some of these bugs are in fact not bugs but rather wishes for new features that are now implemented, these are also mentioned in the FIXED BUGS. On top of that, new features or relevant technical changes are also documented in specific sections such as PLATFORM CHANGES, TOOLS CHANGES, OTHER CHANGES. The above is similar to what was done for the NEWS in previous releases. For the specific example of Xen specific syscalls, in the past, these were only referenced in the fixed bugs section. But if relevant (e.g. if the support is now complete or allows to run significantly more programs), IMO, they could also be mentioned in PLATFORM CHANGES, so as to better inform the users. Philippe > > Thanks, > > Bart. > > On 12/01/13 15:51, sv...@va... wrote: > > Author: philippe > > Date: Sun Dec 1 14:51:21 2013 > > New Revision: 13742 > > > > Log: > > Move bug fix announcement to the FIXED BUGS section > > > > > > Modified: > > trunk/NEWS > > > > Modified: trunk/NEWS > > ============================================================================== > > --- trunk/NEWS (original) > > +++ trunk/NEWS Sun Dec 1 14:51:21 2013 > > @@ -4,7 +4,6 @@ > > > > * ================== PLATFORM CHANGES ================= > > > > -328205 Implement additional Xen hypercalls > > > > * ==================== TOOL CHANGES ==================== > > > > @@ -30,6 +29,7 @@ > > 327238 Callgrind Assertion 'passed <= last_bb->cjmp_count' failed > > 327837 dwz compressed alternate .debug_info and .debug_str not read correctly > > 327916 DW_TAG_typedef may have no name > > +328205 Implement additional Xen hypercalls > > > > Release 3.9.0 (31 October 2013) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > ------------------------------------------------------------------------------ > > Rapidly troubleshoot problems before they affect your business. Most IT > > organizations don't have a clear picture of how application performance > > affects their revenue. With AppDynamics, you get 100% visibility into your > > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > > http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk > > _______________________________________________ > > Valgrind-developers mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > > |