Georgetown Release - Released 2009-03-30

Georgetown, Guyana: Governmental administration.

Introduction

Georgetown Release is the code name for the TWiki Release 4.3, TWikiRelease04x03. This release supersedes the FreetownRelease (TWikiRelease04x02). The CodeName of the release after Georgetown is HelsinkiRelease.

Releases

Release topic	Date	Stable?	Download	Rev	Type	Code Name
TWikiRelease04x03x02	2009-09-02		zip, tgz, upgrade.zip, upgrade.tgz, md5	4.3.2 (r18148)	Production	GeorgetownRelease
TWikiRelease04x03x02rc2	2009-08-31		zip , tgz	4.3.2-rc2 (r18125)	RC	GeorgetownRelease
TWikiRelease04x03x02rc1	2009-08-27		zip , tgz	4.3.2-rc1 (r18121)	RC	GeorgetownRelease
TWikiRelease04x03x01	2009-04-29		zip, tgz, upgrade.zip, upgrade.tgz, md5	4.3.1 (r18054)	Production	GeorgetownRelease
TWikiRelease04x03x00	2009-03-30		zip, tgz, upgrade.tgz, upgrade.zip	4.3.0 (r17948)	Production	GeorgetownRelease
TWikiRelease04x03x00rc1	2009-03-07		zip , tgz	4.3.0-rc1 (r17878)	RC	GeorgetownRelease

Release Focus

The TWikiMission specifies the overall purpose of the project.

The release focus is per our roadmap:

• Usability:
  • Seamless, quick, extensible WYSIWYG
  • Point and click permissions
  • Flow of manipulating content: File upload, more screen,...
  • Polish content of the TWiki distribution to be more accessible to different types of personas
• Performance & scalability:
  • Fast structured queries
  • Fast text search
  • Storage back-end that scales to gazillions of pages with compatibility and audit trail
  • Address high traffic bottlenecks by e.g. implementing caching
  • Topic Object Model
• Application platform:
  • Easy ways to build & exchange applications & components
• Mashups:
  • Easy ways to mash up different data sources & applications (XML/SOAP/JSON/OpenSocial toolkit)
• UI:
  • Stable template baseline for skins

See latest TWikiRoadMap

Release Management

• Please follow our TWikiReleaseManagementProcess
• Release manager for Georgetown is SopanShewale

Georgetown Release Meetings

Meetings are held in #twiki_release IRC channel.

Features / Change Proposals

See all TWikiFeatureProposals

-- Contributors: PeterThoeny, CrawfordCurrie, SvenDowideit - 07 May 2007

Discussion

I added Usability to the Release Focus . I'm convinced that TWikis lacking ease of use (in some parts) needs to be improved a lot. It's the next major release, so we need to make a bis step forward in this area.

-- CarloSchulz - 23 Jan 2008

Database storage would be the feature that TWiki needs. I'm no big coder but will seek to contribute whatever I can. I wish for a narrow feature list, mostly focusing on database support.

-- LarsEik - 23 Jan 2008

Ability to easily install/deploy Twiki in a (virtual) hosted solution which does not have command line (shell) access, nor ready access to other utilities (such as gunzip etc), and where cgi-bin can not be dedicated to simply having Twiki in it (since a variety of other packages also run off the same virtualised hosted area).

-- TonySutherland - 30 Jan 2008

Tony, TWikiStandAlone is probably something you want to help along then. I managed to get it running on my laptop. Really great and easy. I think that is nr.2 feature after database storage.

-- LarsEik - 17 Feb 2008

I am supporting Carlo for adding Usability as a main goal for TWiki.

-- MartinSeibert - 18 Feb 2008

Nobody is interested in ProposedUTF8SupportForI18N ?

-- JurajVariny - 14 Apr 2008

Its not that no-one is interested in seeing it done. Rather that no-one has commited to doing the work. Are you interested in doing it (we really do need more hands in this area in particular)?

-- SvenDowideit - 14 Apr 2008

Given the recent development in the TWikiCommunity, this page needs an update real badly.

-- JoachimBlum - 11 Nov 2008

Yes, names will change, the roadmap largely remains the same. You can make a difference by getting engaged!

-- PeterThoeny - 11 Nov 2008

Yes, I'm quite interested in ProposedUTF8SupportForI18N! I tested Freetown release and the SVN repository. Chinese WikiWord is supported through [[ ]] tag. But CreateNewTopic page doesn't support it. And THE MAIN PROBLEM is Chinese searching doesn't work at all. In English sentences, spaces and marks are used to split words. But in Chinese, you need a more sophisticated splitting logic.

Some of my colleagues are working on Chinese word splitting. And I'm quite interested in TWiki project. And want to promote it to my company. Though I'm new to TWiki, but I've found a lot of bugs and tried to fix some of them. I think I may offer some help in UTF8 proposal, even allocating some company resources.

-- FengZhaolin - 12 Feb 2009

Thank you Feng for the offer to get involved! That is very good news, I18N needs some tender loving care. Please ReadmeFirst to get started. I will also send you some pointers by e-mail.

-- PeterThoeny - 12 Feb 2009

I've checked for Korean WikiWord like that Feng did. But in case of mine, which version is GeorgeTown(r17907), I was able to search Korean characters which were used as a topic. That's great!

However, the wikiWordRegex of TWiki.pm is not sufficient to express Korean, Chinese, and even Japanese. In addition, it seems that there are few considerations for theses languages, which have no concepts of capital or small letters.

When do you have a plan to support newer version of WikiWord? Is that started already?

-- JustinKim - 27 Mar 2009

Thank you for the feedback. We are currently looking for people who can drive the internationalization effort of TWiki. It would be great if you join efforts with Feng.

The goal for Korean, Chinese and Japanese is to rely solely on square bracket links, and to support multi-byte characters for page names.

-- PeterThoeny - 27 Mar 2009