1.8 plans

The general idea about 1.8 is to stabilise / test / release it rather quick after SOC 2008 to get the stuff out that we have ready. Then we create a moin 1.9/2.0 repo and work on the harder to integrate stuff.

Release schedule (no guarantees!)

• translators can catch up any time (see master18 wiki) - the releases will just have the stuff that is ready at release time.

• until 2008-09-15 first beta release

• until 2008-10-06 freeze, first release candidate(s), create moin/1.9 repo

• until 2008-11-01 release 1.8.0

TODO

• GUI editor upgrade (GUI editor in 1.6/1.7 has many problems)

• work on "modernized" theme

• config refactoring (work in progress, see below too)

• change the HomepageTemplate to

  ##master-page:HomepageTemplate
  #format wiki
  #language en
  == @``ME@ ==
  
  Email: <<MailTo()>>
  ## You can even more obfuscate your email address by adding more uppercase letters followed by a leading and trailing blank.
  ...
   * extend HelpOnVariables `|| <<MailTo()>> || Just the user's email address, obfuscation can be extendeded || e.g. test DOT user AT example dot com ||`
  ----
  CategoryHomepage

  That does not really work good on master wiki, because every translation of HomepageTemplate is not recognized by the default page_template_regex and thus, @...@ stuff gets expanded.

Done

• add action to send an object from the cache (applications: primarily all image-generating extensions, but can be also used for other stuff):

  • use non-guessable cache key as action url param, so we don't have to check ACLs

  • store metadata for header and raw file data separately, so we can use metadata for 304 status checks and sendfile for raw data

  • implement file-like interface for cache objects (for sendfile)

• multiple plugin dirs

• widget.browser.format form action method needs to become configurable not hardcoded GET only.

• something like this should be added to 1.7/1.8 otherwise only the browser widget has control over a form definition browser.patch

settings to remove?

Add some words about removal reason and, if applicable, how to replace the functionality.

• url_prefix (replaced by url_prefix_static since 1.6)

• subscribable_events/_subscribable_events (wasn't even used)

• traceback_log_dir (use logging.exception())

• editor_quickhelp (moved into parsers, new custom parsers should ship their own quickhelp)

• backup related settings (when new storage gets merged, incompatible with storage abstraction)

Additionally, a number of userprefs settings should be cleaned up:

• user_autocreate (moved to auth objects)

Later (not 1.8)

• refactor a lot of code to get rid of **kw arguments and provide defaults instead, i.e.

  def foo(request, **kw):
     bar = kw.get(bar, False)
     ...

  is changed to

  def foo(request, bar=False):
     ...
  n

  • to make the code easier to understand and give errors when using wrong arguments that would otherwise be ignored.

  • it is not a good idea to do this while a lot of different development branches are active as it will create lots of conflicts

• separate anything that should persist (e.g. session storage) out of caching framework
• remove antispam_master_url (should be a parameter to the security policy)
• remove user_transient_fields (does this have to be configurable? transient data ought to be in the session)
• cleanup user_checkbox_defaults/user_checkbox_disable/user_checkbox_fields/user_checkbox_remove (check if they're still really applicable)
• cleanup user_form_defaults/user_form_disable/user_form_fields/user_form_remove (check where used etc.)
• check output of actions called by macro Action
• make the msg on user creation of not valid password much more visible by adding the error icon