The Stack Overflow podcast is back! Listen to an interview with our new CEO.
4 Added two tags
| link
3 added 106 characters in body
source | link

This might be only a question of definition, but maybe there's a consensus?

Given the situation, software Foobar Plus is under construction, we're not working on an update, but on the first release of it.

Now, a specific feature(A) was implemented;

  • Feature(A) caused a unwanted behavior in feature(B).
  • It has no influence on feature(A), but is caused by it.
  • Feature(B) isn't implemented yet, the behavior got noticed due interpreting debug logs.

The question now is; is this unexpected behavior called a bug, or just a change in feature(B)'s environment?

Edit: This question isn't about blaming anyone but about finding the proper definition for this case.

This might be only a question of definition, but maybe there's a consensus?

Given the situation, software Foobar Plus is under construction, we're not working on an update, but on the first release of it.

Now, a specific feature(A) was implemented;

  • Feature(A) caused a unwanted behavior in feature(B).
  • It has no influence on feature(A), but is caused by it.
  • Feature(B) isn't implemented yet, the behavior got noticed due interpreting debug logs.

The question now is; is this unexpected behavior called a bug, or just a change in feature(B)'s environment?

This might be only a question of definition, but maybe there's a consensus?

Given the situation, software Foobar Plus is under construction, we're not working on an update, but on the first release of it.

Now, a specific feature(A) was implemented;

  • Feature(A) caused a unwanted behavior in feature(B).
  • It has no influence on feature(A), but is caused by it.
  • Feature(B) isn't implemented yet, the behavior got noticed due interpreting debug logs.

The question now is; is this unexpected behavior called a bug, or just a change in feature(B)'s environment?

Edit: This question isn't about blaming anyone but about finding the proper definition for this case.

2 Copy edits.
source | link

Is unwanted behavior, while work is in progress, declarable as a "bug"?

This might be only a question of definition, but maybe there's a consence;consensus?

Given is the situation, where software Foobar Plus is under construction. We're, we're not working on an update, but on the first release at allof it.

Now, a specific feature(A) was implemented. Feature(A) caused a unwanted behavior in feature(B). It has no influence on feature(A), but is caused by it. Feature(B) isn't implemented yet, behavior got noticed due interpreting debug logs.implemented;

  • Feature(A) caused a unwanted behavior in feature(B).
  • It has no influence on feature(A), but is caused by it.
  • Feature(B) isn't implemented yet, the behavior got noticed due interpreting debug logs.

The question now; Isnow is; is this unexpected behavior called a bug, or just a change in feature(B)s's environment?

Is unwanted behavior, while work is in progress, declarable as "bug"?

This might be only a question of definition, but maybe there's a consence;

Given is the situation, where software Foobar Plus is under construction. We're not working on an update, but on the first release at all.

Now, a specific feature(A) was implemented. Feature(A) caused a unwanted behavior in feature(B). It has no influence on feature(A), but is caused by it. Feature(B) isn't implemented yet, behavior got noticed due interpreting debug logs.

The question now; Is this unexpected behavior called a bug, or just a change in feature(B)s environment?

Is unwanted behavior, while work is in progress, declarable as a "bug"?

This might be only a question of definition, but maybe there's a consensus?

Given the situation, software Foobar Plus is under construction, we're not working on an update, but on the first release of it.

Now, a specific feature(A) was implemented;

  • Feature(A) caused a unwanted behavior in feature(B).
  • It has no influence on feature(A), but is caused by it.
  • Feature(B) isn't implemented yet, the behavior got noticed due interpreting debug logs.

The question now is; is this unexpected behavior called a bug, or just a change in feature(B)'s environment?

    Post Reopened by Thomas Owens
    Post Closed as "unclear what you're asking" by Thomas Owens
1
source | link