Minutes of Edinburgh Release Meeting, 06 Feb 2006

Logistics, Participants, IRC log

• Date: Monday, 30 Jan 2005 21:00 GMT
• IRC Channel: #twiki_edinburgh
• FIXME Participants: AntonioTerceiro (terceiro), ArthurClemens (ArturClemens), KennethLavrsen (Lavr), LynnwoodBrown (Lynwood), MichaelDaum (MichaelDaum), PeterThoeny (PeterThoeny), SteffenPoulsen (SteffenPoulsen), SvenDowideit (SvenDowideit), MeredithLesly (bitca)
• Facilitated by LynnwoodBrown and notes taken by SteffenPoulsen
• FIXME EdinburghMinutes2006x02x06.txt: Edinburgh Meeting Minutes 2006-02-06

Agenda

• Quick review of DakarReleaseMeeting2006x01x30
• TWiki 4.0.1 release (TWikiRelease04x00x01)
• Release focus of EdinburghRelease
• Split DEVELOP branch (OneSvnBranchPerRelease)
• Fix Dakar documentation model (DakarDocumentationModelIsBroken)

Quick Review of Dakar Release Meeting 2006-01-30

• Desired outcome: Quick review of DakarReleaseMeeting2006x01x30 to address pending issues
• HandlingCairoDakarPluginDifferences needs some more doc work
  • DONE -- PTh
• COVER documentation awaits CDots arrival back
  • Sven has discovered new issues, will add to bug item
    • DONE

TWiki 4.0.1 release

• Desired outcome: Remaining tasks and release timing of TWikiRelease04x00x01
• Two major fixes, warrents a dot release
• Lavr has issue on BlackListPlugin, Bugs:Item1586
  • Confirmation is new in Dakar, BlackListPlugin needs to be aware
  • Magic number only for registration, not for confirmation
  • Secret field should be added to registration form, does not hurt
    • Action item for Steffen, for release 4.0.1
      • DONE, Item 1586 closed (Credit to Peter for BlackListPlugin update)
• Steffen deprecated [[http://xml.org XML]]-syntax, needs to be inserted again
  • DONE
• Looking over the agenda, I'd like to add one item: offering patched files for fixes.
  • Proposal by Sven, 3 packages for 4.0.1
    • a real patch
    • a set of updated files to copy over an existing install
    • a full packages
• Discussion on automation / urgency priorities
• What goes into 4.0.1 needs to be listed as "known items" to 4.0.0
  • Action item for Steffen, cut & paste from bugs web
    • DONE - Listed as changesets in TWikiRelease04x00x01 instead, thanks Sven! -- SP
• Won't have time to test mod_perl issues further, but an update to docs in TWiki.InstallingTWiki and TWiki.UpgradingTWiki would be good
  • Lavr will doc his setup (mod_perl / apache 2)
    • Pending resolving the open mod_perl issues. TWiki 4.0.1 does not work satisfactory with mod_perl. Users continuously run into issues when saving a topic ( Bugs:Item1576 ) and the login/logout issue ( Bugs:Item 1575 ) is also a problem that needs to be resolved. Making a doc that says how to run with mod_perl is more misleading than anything else. I have tried to get more debug info for a week but I cannot get to the bottom of this. The randomness in the failure makes it even more difficult for me. I have given up mod_perl for now. -- KennethLavrsen - 12 Feb 2006

Release focus of Edinburgh Release

• Desired outcome: Agree on process and timeline to decide on EdinburghRelease focus
• Brainstorm on EdinburghRelease ASAP, try to get some discussion going for next week, or next-next week
• Consider focusing on 4.1 and 4.2 more than 5.0
• OSS projects roadmaps are mainly driven by who want to work on something and not what money can we get from it
• "A guideline for developers" - not too stone ish - more or less just an organized and prioritized enhancement request list
• A great roadmap can help attract developers, short term / long term
• We could propell twiki way more if we tune the marketing message
• "To succeed" means "providing something valuable"
• It is important that a product knows its segment and what is wants to focus on - so that there is a difference between TWiki and the other Wikis. A good difference.
• Suggestion for 4.1 roadmap: mod_perl
• Suggestion for 4.1 roadmap: Incremental speed improvements and better WYSIWYG. And 5.0 redesign topic storage to something indexed that than scale much better then today where Twiki clearly has an "upper limit" defined by speed of searches.
• Two different scopes. 1. Which features when. That is roadmap. 2. HOW. That is deciding on development model, branching, documentation model.
• We each probably have personal roadmaps. Making them explicit and looking for commonalities might facilitate discussion.
• Personal roadmaps are good to know where the interests are, but they distract from focus unless coordinated
• Cairo roadmap can be inspected CairoRelease.

• General agreement on discussing and adding to roadmaps the next couple of meetings, and try to have something settled for Feb 20.

Split DEVELOP branch

• Desired outcome: Review OneSvnBranchPerRelease and address open questions
• Rather technical discussion, for details see IRC log
• Only part consensus reached

Fix Dakar documentation model

• Desired outcome: Review DakarDocumentationModelIsBroken and brainstorm on solution
• Rather technical discussion again, visit IRC log
• Only part consensus reached, proceeding in Codev
• Give the people the tools they need; but editing through TWiki is must have

Miscellaneous

Action Items

• Sven
  • Update COVER item with new findings
    • DONE
• Peter
  • BlackListPlugin update (allow for confirmations)
    • DONE
• Steffen
  • Add secret field to registration form
    • DONE
  • Re-instate [[http://xml.org XML]]-syntax
    • DONE
  • Cut&paste to create known issues from items in bugs web
    • DONE (see above)
• Lavr
  • Documentation updated for mod_perl

IRC Log

• EdinburghMinutes2006x02x06.txt: Edinburgh Meeting Minutes 2006-02-06

Back to: EdinburghRelease

Comments / Feedback