Hi,
I suggest this schedule for 2.3.0:
May 28: ask for new translations
June 4: RC1
June 18? : final
Meanwhile we try to empty the patch tracker :)
----- Original Message ----- From: "Marc Delisle" Delislma@CollegeSherbrooke.qc.ca
Hi,
I suggest this schedule for 2.3.0:
May 28: ask for new translations
June 4: RC1
June 18? : final
I'll have exams in a few weeks so I won't have much time. They'll end on June 10th, so I'd prefer this schedule: release candidate 1: June 18th final release (or maybe RC2, if RC1 is too buggy): July 2nd.
Another thing: There was an idea about adding a third frame to navigate between the new tbl_properties / db_details pages, maybe combined with feature #546112. Is anyone working on this? If not, I'd like to do it.
Alexander
Rabus wrote:
----- Original Message ----- From: "Marc Delisle" Delislma@CollegeSherbrooke.qc.ca
Hi,
I suggest this schedule for 2.3.0:
May 28: ask for new translations
June 4: RC1
June 18? : final
I'll have exams in a few weeks so I won't have much time. They'll end on June 10th, so I'd prefer this schedule: release candidate 1: June 18th final release (or maybe RC2, if RC1 is too buggy): July 2nd.
No problem!
Another thing: There was an idea about adding a third frame to navigate between the new tbl_properties / db_details pages, maybe combined with feature #546112. Is anyone working on this? If not, I'd like to do it.
I am not working on this, you can do it!
On Tue, 14 May 2002, Marc Delisle wrote:
I'll have exams in a few weeks so I won't have much time. They'll end on June 10th, so I'd prefer this schedule: release candidate 1: June 18th final release (or maybe RC2, if RC1 is too buggy): July 2nd.
No problem!
I've got an intense programming job for a few weeks now, so this schedule works well for me as well. I'm coding C++ with SGI Performerer on a lovely SGI Onyx 3200 8-).
Another thing: There was an idea about adding a third frame to navigate between the new tbl_properties / db_details pages, maybe combined with feature #546112. Is anyone working on this? If not, I'd like to do it.
Sounds like a good plan to me.
Progress report for my stuff: IP Allow/Deny rules (Feature #484158) - coded and tested, writing documentation now - will commit by the end of Sunday
DB-Config (Feature #485311) - coding still in progress, currently focusing on security
DB-Config web pages (Feature #486080) - not started yet
Column Documentation (Feature #494651) - not started yet - see mailing list messages about having a phpMyAdmin database
images format http://burnallgifs.org/ (Feature #458895) - Tweaking PNG images for size/quality
create user and database for an ISP (Feature #479640) - I lost my code in a FUBAR accident with my local CVS copy - Haven't restarted.
Would everybody else that is working on some specific bug/features/patches please take the assignment of them on the Feature/Patch/Bug trackers? That way we can see what has not been started, and consider those things for 2.3.0.