Development is pretty much done (see DakarRelease) and we need to focus on bugfixing and documentation.

The idea is to lock down changes so that only entries in Bugs web can be used as references for checkins (i.e. you can't link back to Codev topics). The rationale is that way, the reports don't pollute codev, and full traceability of changes is maintained.

Anyone object? Reasons?

-- CrawfordCurrie - 12 Jul 2005

personally, i'm all for it - in fact in the long term i'd go further and change the Bugs web into a Tasks web to track all commits - thus leaving Codev more useful for disscussions. (and makes if significantly easier to track what goes into which release.

-- SvenDowideit - 12 Jul 2005

I agree. Cairo is significantly unuseful compared to Dakar, but I would not want to advise use of Dakar in a production environment until its loose ends are tied.

-- MartinCleaver - 12 Jul 2005

Agreed. At least, lets make a list of what we still will be working on so that stragglers (such as I) can finish their work in progress...

-- ThomasWeigert - 12 Jul 2005

i propose that we release a preview release by 17 Jul 2005

-- WillNorris - 13 Jul 2005

OK... DevelopBranch now requires all changes to come from Items in the Bugs web

-- SvenDowideit - 16 Jul 2005

Sven, I think we first need to make a list of what we should still ocmplete, rather than just pick a random stop work date, as I said earlier....

-- ThomasWeigert - 16 Jul 2005

We already have that list; that is what DakarRelease and the Bugs web is for. If something is missing from the Bugs web, please add it so we can track it (Bugs is a misnomer; it is general tracking for DakarRelease and contains enhancements as well)

I have polled for release criteria as well, but not had much response on that.

-- CrawfordCurrie - 17 Jul 2005