This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2017-12-11 23:01:27

The IssueTrackingWikiProtocol is used for pages which are intended for tracking open and resolved issues. In order for this to work, we've created a few simple rules for modifying these pages.

The Rules

  1. We keep two kinds of pages - OpenIssues and ResolvedIssues. Items are originally created on the OpenIssues page, and then moved to the ResolvedIssues page, once they've been resolved according to the originator of the issue.

  2. All issues are numbered with a permanent number. The Wiki won't do this for us conveniently, so the following format is used 2). Parentheses are used to keep the wiki from autonumbering the paragraph. Every issue number should be accounted for between the OpenIssues page and the ResolvedIssues page.

  3. The line with the issue number on it should contain only a short description of the issue, preferably one that fits on one line.
  4. Subsequent lines are indented using a single space. Sometimes the issues are written in the voices of different participants. When the participant changes, the text should start in a new paragraph.
  5. Spelling corrections and simple wording clarifications are fine. Feel free to make them inline.
  6. Disagreements, comments, questions, and more verbose clarifications should be in separate paragraphs in most cases.
  7. Both pages are kept in reverse cronological order. That is, the newest / most recently resolved issues are placed first on the respective pages.

Sample OpenIssues Page

1) LarsMarowskyBree thinks we need some more documentation on Wiki etiquette

  • AlanRobertson isn't quite sure he understands what is wanted here.

2) AlanRobertson thinks we need to have someplace in the Wiki to track open and closed issues for the LocalResourceManager.

Sample ResolvedIssues Page

1) LarsMarowskyBree thinks we need some more documentation on Wiki etiquette

2) AlanRobertson thinks we need to have someplace in the Wiki to track open and closed issues for the LocalResourceManager.


Uhm, the examples above are not sorted in reverse order ... was this intentional?

And, may I suggest to use the Include macro instead, like in [[Include(BaseNameOpenIssues/IssueName)]]

This ways you have one subpage per issue, which stays the same and can even be bookmarked. The macro invocation then can easily be moved from the OpenIssues to the ResolvedIssues page.

See Also

WikiEtiquette