DEVELOP branch has been floating around for quite a while now, and is even in use on a few public websites and probably a few private ones too. So I started to wonder, what are the preconditions that have to be met before the CoreTeam will consider DEVELOP ready for release as DakarRelease? Obviously

1. Bugs:AllOutStandingItems has to be cleared
2. The list at the top of DakarRelease has to be cleared

But what additional preconditions exist? Here are some possibilities:

• It has to have run TWiki.org for a week without problems?
• It has to have a "killer feature"?
• It has to have a suite of new logos?
• All plugins have to be tested against it?
• All documentation has to be translated into Tibetan and blessed by the Dalai Lama?

Core team, and specifically PeterThoeny, help, please, otherwise we are left guessing what the priorities are, and we will never get it out the door.

-- CrawfordCurrie - 22 Jun 2005

this isn't a wishlist, it's a must have list.

Discussions on MD5 sums moved to ShipMd5Sums.

Criteria for an alpha release

• I assume none - we should do so every month -- SvenDowideit - 22 Jun 2005
• At least full unit tests, automatic testcases, and sanity testcase, all pass. -- CrawfordCurrie - 16 Jul 2005

Criteria for a beta release

• passes all tests? -- SvenDowideit - 22 Jun 2005
• Basic docs in place. No Urgent bugs. -- CrawfordCurrie - 16 Jul 2005

,v files in the release, so we can test UpgradeTWiki

-- CrawfordCurrie - 21 Jul 2005

Criteria for a TWiki release

• TWikiAdvocacy text -- SamHasler - 08 Jul 2005
• define procedure (and naming convention) for follow-up releases containing bug fixes and/or security patches

-- WillNorris - 21 Jul 2005