Developer's meeting notes
|
|
By janra , Section Project [] Posted on Fri Feb 13, 2004 at 12:00:00 PM PST
|
|
There was a developer's meeting today (Friday, February 13th, 7PM EST) as announced on scoop-dev last week.
Items discussed were:
- 1.0 release requirements
- plans for after 1.0
- versioning
- bugzilla component owners
- new components
- docs
- development practices
- release dates
|
1.0 release requirements
- Bugs in list must be fixed
- Documentation finished
- README README.upgrade and INSTALL updated
- Clean up default scoop layout
- (CT) do a default install on a clean system with RC, note problems especially with CPAN
Plans for after 1.0
- Get rid of forumzilla support
- Switch tags on CVS so CURRENT is the default tree
- Branch out STABLE from release
- Fully deprecate MySQL 3.22 support
- Lots of new features & code cleanup in -CURRENT; may break compatibility with 1.x
Versioning
- Two branches, STABLE and CURRENT:
- STABLE will have bugfixes and some features backported from CURRENT and will be the source of 1.1, 1.2, etc releases
- CURRENT will be bleeding edge and never guaranteed stable, and will be the source of the future 2.0 release
Bugzilla component owners
- hulver: archive, search, uploads, comments
- captain tenille: sections, stories, topics, users, utility code
- panner: cron, subscriptions, scoop.k5, rdf, admin tools, polls, install, advertisements, DB interface, SBE
- rusty: payment processing
- coryking: post throttle
- janra: documentation
- MostlyHarmless: SBM
New Components to add to Bugzilla
- Compat (CT)
- Plugins (coryking)
- CVS (CT)
- HTML output (janra)
Documentation
- developer docs
- index
- needs feedback from users
- README, README.upgrade, and INSTALL
Development practices
general:
- to make a code patch: cvs diff -c >my.patch
- never check in your own code - send to another person with commit access to test it and let them check it in
- need "how to write a db patch" docs - write sql statement in patch file then paste to mysql interface; if it works, leave it in patch because it's tested. If not, debug & repeat
for commit:
- update scoop.sql when committing - not when submitting sql patch for testing
- update README in patch directory when committing a new sql patch
- number patches just before committing - cvs update immediately before to avoid numbering conflicts
- panner to document his commit procedure
Release dates
- Final Release Candidate by March 1, 2004
- Release a few days afterward, pending last minute bugfixes
- RC1 in a day or so
If you have any comments about the above items, feel free to post them here. |
|
Story Views
|
90 Scoop users have viewed this story.
|
|