Tags:
create new tag
, view all tags

Minutes of Georgetown Release Meeting, 2009-02-16

TOC and Agenda

Logistics, Participants, IRC log

1. Review Urgent Bugs

  • TWikibug:Item5926 - Topics with Chinese in UTF8 destroys page view in Internet Explorer -- defer to after 4.3.0
  • TWikibug:Item4688 - TWiki password, registration and login options need a careful going over (urgent for 4.2.3) -- defer to after 4.3.0
  • TWikibug:Item6140 - Table attributes lost on save -- defer to after 4.3.0
  • TWikibug:Item6138 - Bulletted lists in form fields are not rendered properly -- Sopan working on it
  • TWikibug:Item6091 - statistics broken (trunk only) -- defer to after 4.3.0
  • TWikibug:Item6161 - Test Cases from Release Branch Should pass before next Release
  • TWikibug:Item6086 - TSA DENYTOPICVIEW causes crash (trunk only) -- defer to after 4.3.0
  • TWikibug:Item6041 - TinyMCE bug with Firefox 3 and bulleted lists -- fix by reporter, to be verified
  • TWikibug:Item6039 - Preview does not respect VIEW_TEMPLATE (trunk only) -- defer to after 4.3.0
  • TWikibug:Item5804 - Can kill code by appending odd url params (trunk only) -- defer to after 4.3.0
  • TWikibug:Item5955 - WysiwygPlugin failes to roundtrip tables that are created with align center -- defer to after 4.3.0
  • TWikibug:Item5437 - UTF-8 fixes for TWiki 5.0 (was 4.2 but deferred) -- defer to after 4.3.0

  • TWikibug:Item6185 - Missing newline in Formatted Search if footer used -- not urgent, but fixed yesterday

2. Feature requests for Georgetown Release

3. Release timing of TWiki 4.3 release

  • Desired outcome: Decide on target dates

  • 2009-02-23 - code freeze
  • 2009-03-02 - string freeze
  • 2009-03-02 - rc1

  • Peter to ask Markus if he'd like to help out to coordinate translations - TranslationSupport

4. Review release management process

  • Goal is to make it easier and quicker to accept feature proposals for instant gratification, while keeping risk low of pushing feature through that is not aligned with mission
  • Discussed Peter's idea posted at bottom of TWikiReleaseManagementProcess: May be require x% of active contributors to vote on a feature. Such as: "A vote on a feature can be done at a release meeting if 33% of active core contributors vote, either at the release meeting or online in the feature proposal topic ahead of release meeting. An active core contributor is defined as a person who made at least 3 check-ins within 2 month to the core or core extensions."
  • Feedback: Consider also non-coders, e.g. people contributing on Codev, TWiki, Plugins and Support webs

Back to: GeorgetownRelease

Comments / Feedback

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2009-02-17 - PeterThoeny
 
  • 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-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.