Re: [cross-project-issues-dev] Final bugzilla status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cross-project-issues-dev] Final bugzilla status

From: Krzysztof Daniel <kdaniel@xxxxxxxxxx>
Date: Mon, 28 May 2012 08:42:15 +0200
Delivered-to: cross-project-issues-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cross-project-issues-dev>
List-help: <mailto:cross-project-issues-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=unsubscribe>
Organization: Red Hat

There was a practice of moving bugs to a CLOSED state after Eclipse was
shipped once upon a time :-).

So, the resolved state was used when the bug was fixed.
Verified - when the bug was verified in the milestone end game.
Closed - when the bug was verified after the release.

The rationale was that a closed bugs should never be touched again,
while other statuses could be reopened, and patches for them withdrawn.

-- 
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
Red Hat

References:
- [cross-project-issues-dev] Final bugzilla status
  - From: Wim Jongman
- Re: [cross-project-issues-dev] Final bugzilla status
  - From: Stephan Herrmann

Prev by Date: Re: [cross-project-issues-dev] Juno RC1 staging repository is complete
Next by Date: Re: [cross-project-issues-dev] Final bugzilla status
Previous by thread: Re: [cross-project-issues-dev] Final bugzilla status
Next by thread: Re: [cross-project-issues-dev] Final bugzilla status
Index(es):
- Date
- Thread

Breadcrumbs