create new tag
, view all tags

Minutes of Freetown Release Meeting, 2007-05-21

TOC and Agenda

Logistics, Participants, IRC log

1. Action Item Review

  • All Proposers with accepted proposals: Update ProposedFor field in accepted proposals (not yet implemented) to GeorgetownRelease if they will not be ready for feature freeze date.
  • DONE Kenneth: UseIsoDates: Kenneth takes the action to re-write the proposal for a renewed decision round. Current proposal has no chance to be accepted.
  • DONE Sven: TopicCaseSensitivity: Sven to clarify the spec
  • DONE Sven: AddTWikiAdminUser: Sven to clarify the spec
  • Peter: Create a TWikiBetaTesting topic in Codev, with info for beta testers.
    • Need to do this before next release. Need to recruit beta testers.

2. Review Proposed Features

3. Release Schedule of TWiki Release 4.2

  • Desired outcome: Decide code freeze date

The plan from previous release meeting:

  • Feature freeze (last day to checkin new features): Monday 28 May 2007.
  • Beta release: 17 Jun 2007
  • Earliest release date (can be delayed if too many bugs are open or tests fail): 30 Jun 2007

KennethLavrsen proposes: Because of the current state of Bugs many of us have been delayed in implenting code I propose that we call a freeze on new features but give currently accepted proposals at least another week to get implemented. Proposals that are not accepted at todays meeting should be postponed to Georgetown (5.0) which is probably a year from now. Dates above should then move a week. With the current number of open bugs I believe we need 1-2 more weeks for getting TWiki stable again. You only have to play with TWiki for 10 minutes and you have seen several bugs. I have a list of at least 10 new bugs I have not entered because Bugs times out on me all the time. I do not believe we can release a beta 4.2 until end of June.

CrawfordCurrie: Can we please change the way the releases are listed in the "Proposed For" field in the Codev forms? I want to be able to propose a change for the next patch release, for the next minor release, or the next major release. I don't care what the number is, and I don't care what it's called; I only care that it's the "next release" at that level. This approach also lets us carry items over more easily without the risk of losing them.

  • We forgot to discuss this one. I agree. But I would not look at if it is minor/major. Just two values. One for the next release. And one for the following. It will be an exception to the rule to role new features into patch releases that are so large that they require more than a simple bug item. -- KJL

Action Items

  • All. Implement accepted feature proposals before 28 May 2007 - or defer them to Georgetown (5.0)


Back to: FreetownRelease

Comments / Feedback

Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt FreetownMinutes2007x05x21.txt r1 manage 54.3 K 2007-05-21 - 22:41 KennethLavrsen Log of meeting (time stamps is CEST)
Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r5 - 2007-05-21 - KennethLavrsen
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.