Changeset 9479


Ignore:
Timestamp:
10/03/10 10:38:25 (20 months ago)
Author:
KennethLavrsen
Message:

Item8841: Prepare the final release of 1.1.0

Location:
branches/Release01x01/core/data/System
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • branches/Release01x01/core/data/System/ReleaseHistory.txt

    r9446 r9479  
    66%TOC% 
    77 
    8 ---++ Foswiki Release 1.1.0 Release Candidate 1 - 28 Sep 2010 
    9  
    10 Foswiki 1.1.0 RC 1 was built 28 Sep 2010. Foswiki 1.1.0 Beta 1 was built 13 Sep 2010. It is a release with more than 260 bug fixes relative to 1.0.10 and more than 670 bug fixes relative to 1.0.0. 
     8---++ Foswiki Release 1.1.0 - 03 Oct 2010 
     9 
     10Foswiki 1.1.0 was built 03 Oct 2010. It is a release with more than 260 bug fixes relative to 1.0.10 and more than 670 bug fixes relative to 1.0.0. 
    1111 
    1212This release adds more than 100 enhancements. Foswiki 1.1.0 introduces jQuery Javascript user interface framework, improved topic history display, new QUERY and FORMAT macros, better userinterfaces for groups, much improved WYSIWYG editor, facelift of the default skin, much improved configure tool, and much more. 

  • branches/Release01x01/core/data/System/ReleaseNotes01x01.txt

    r9408 r9479  
    11%META:TOPICPARENT{name="ReleaseHistory"}% 
    22 
    3 ---+!! Foswiki Release 1.1.0 Release Candidate 1 - 28 Sep 2010 
     3---+!! Foswiki Release 1.1.0 - 03 Oct 2010 
    44 
    55%TOC% 
    … …  
    1111Foswiki is a wiki: fundamentally, a website with editable web pages. It looks like a normal web site but it encourages contributions, edits, updates, questions, and answers from its users. It's a powerful way of enabling a community to communicate asynchronously using intranet and public internet websites. Foswiki is simple to learn and use. It aims to provide a transparent way for you to publish and exchange your ideas with others over the web and eliminates the one-webmaster syndrome of outdated intranet content. 
    1212 
    13 Foswiki is a structured wiki with tools that enable users without programming  skills to build powerful yet simple applications to process information and  support workflows. Developers can extend the functionality of Foswiki with plugins. 
    14  
    15 Foswiki is the old TWiki project under a new name. Restrictions on the use  of the TWiki brand resulted in many of its developers continuing the project  under the new Foswiki name. Foswiki is backwards compatible with all content  from older TWiki installations. Foswiki 1.1 ships with a !TWikiCompatibilityPlugin  installed and activated by default, thus enabling most extensions  made for TWiki to work under Foswiki. 
    16  
    17 Since the start of the Foswiki project there have been several releases of TWiki,  However there have been very few functionality changes, and the useful changes  have all been tracked in Foswiki, so topics and wiki applications  supported by TWiki should also work with Foswiki. 
     13Foswiki is a structured wiki with tools that enable users without programming skills to build powerful yet simple applications to process information and support workflows. Developers can extend the functionality of Foswiki with plugins. 
     14 
     15Foswiki is the old TWiki project under a new name. Restrictions on the use of the TWiki brand resulted in many of its developers continuing the project under the new Foswiki name. Foswiki is backwards compatible with all content from older TWiki installations. Foswiki 1.1 ships with a !TWikiCompatibilityPlugin, thus enabling most extensions made for TWiki to work under Foswiki. Since the start of the Foswiki project there have been several releases of TWiki, However there have been very few functionality changes, and the useful changes have all been tracked in Foswiki, so topics and wiki applications supported by TWiki should also work with Foswiki. 
    1816 
    1917Foswiki is released under the GNU General Public License. 
    … …  
    3028   * Foswiki 1.0.9 was built 17 Jan 2010. It is a patch release with more than 320 bug fixes relative to 1.0.0 and several enhancements. This release fixes many bugs in the Wysiwyg editor, bugs related to more advanced wiki applications and bugs in the Plugin API. It contains several bug fixes and enhancements related to security and spam fighting. 
    3129   * Foswiki 1.0.10 was built 08 Sep 2010 as a patch release with more than 410 bug fixes relative to 1.0.0. It is assumed to be the last 1.0.X release. 
    32    * Foswiki 1.1.0 Release Candidate 1 was built 28 Sep 2010. It is a release with more than 260 bug fixes relative to 1.0.10 and more than 670 bug fixes relative to 1.0.0. And the release adds more than 100 enhancements. Foswiki 1.1.0 introduces jQuery Javascript user interface framework, improved topic history display, new QUERY and FORMAT macros, better userinterfaces for groups, much improved WYSIWYG editor, facelift of the default skin, much improved configure tool, and many more enhancements. 
     30   * Foswiki 1.1.0 was built 03 Oct 2010. It is a release with more than 260 bug fixes relative to 1.0.10 and more than 670 bug fixes relative to 1.0.0. And the release adds more than 100 enhancements. Foswiki 1.1.0 introduces jQuery Javascript user interface framework, improved topic history display, new QUERY and FORMAT macros, better userinterfaces for groups, much improved WYSIWYG editor, facelift of the default skin, much improved configure tool, and many more enhancements. 
    3331 
    3432---++ Pre-installed Extensions 
    … …  
    4139   * *Compatibility support* - !TWikiCompatibilityPlugin 
    4240 
    43 ---++ What's new — highlights 
    44 ***UPDATE ME*** 
    45  
    46 See ReleaseNotes01x00 for detailed information about changes in that release. 
    47  
    48 #Release01x00Changes 
     41#Release01x01Changes 
    4942---++ Important Changes since Foswiki 1.0.10 
    5043 
    … …  
    7063 
    7164---+++ Powerful new =QUERY= macro 
    72 A number of new features have been added with the goal of improving support  for wiki applications. These include the powerful new =QUERY= macro, which: 
    73    * supports formatted access to formfields and other meta-data in  topics using the same syntax as is used in =IF= and =SEARCH= statements, 
     65A number of new features have been added with the goal of improving support for wiki applications. These include the powerful new =QUERY= macro, which: 
     66   * supports formatted access to formfields and other meta-data in topics using the same syntax as is used in =IF= and =SEARCH= statements, 
    7467   * gives access to *all* meta-data, including that added by extensions, 
    7568   * supports reporting values using JSON and other standards, simplifying the retrieval of meta-data for REST applications, 
    … …  
    7972 
    8073---+++ Re-architecting of the SEARCH macro 
    81 To improve the speed, consistency and extendability of the most complex  and important Macro, we've started to separate the generation of search results from the outputing of FormattedSearch. The most significant user facing improvements are speed and reliability changes - with many more unit tests written to ensure future compatibility. 
     74To improve the speed, consistency and extendability of the most complex and important Macro, we've started to separate the generation of search results from the outputing of FormattedSearch. The most significant user facing improvements are speed and reliability changes - with many more unit tests written to ensure future compatibility. 
    8275 
    8376---+++ FORMAT macro 
    … …  
    8982For developers additional API's have been added to the Foswiki code to allow these Forms to also be used for non-Foswiki user and group backends. 
    9083 
    91 With some configuration, Foswiki can also add users to groups on registration -  either automatically, or allowing the users to select groups to join. 
     84With some configuration, Foswiki can also add users to groups on registration - either automatically, or allowing the users to select groups to join. 
    9285 
    9386---+++ TinyMCEPlugin updates 
    … …  
    108101---+++ Tailoring of user registration made easier. 
    109102 
    110 The topic System.UserRegistration has been enhanced so it now determines  whether a custom user registration page exists in %USERSWEB%, and includes it if it does; otherwise it includes DefaultUserRegistration. 
    111  
    112 This means that your tailored version in %USERSWEB% web will not be  overwritten by future upgrades. 
    113  
    114 You can create a custom version of the UserRegistration form by first  copying the topic DefaultUserRegistration to !UserRegistration in %USERSWEB% web. This will ensure that your changes will remain intact next time you upgrade. 
    115  
    116 A couple of common fields are hidden from normal view to make the  registration page as simple as possible. You can unhide those fields on the page by removing =EXCLUDED_= from the =INCLUDE= tags). 
     103The topic System.UserRegistration has been enhanced so it now determines whether a custom user registration page exists in %USERSWEB%, and includes it if it does; otherwise it includes DefaultUserRegistration. 
     104 
     105This means that your tailored version in %USERSWEB% web will not be overwritten by future upgrades. 
     106 
     107You can create a custom version of the UserRegistration form by first copying the topic DefaultUserRegistration to !UserRegistration in %USERSWEB% web. This will ensure that your changes will remain intact next time you upgrade. 
     108 
     109A couple of common fields are hidden from normal view to make the registration page as simple as possible. You can unhide those fields on the page by removing =EXCLUDED_= from the =INCLUDE= tags). 
    117110 
    118111---+++ Easy tailoring of reset/change password and change email forms 
    119112 
    120 The topics %SYSTEMWEB%.ResetPassword and %SYSTEMWEB%.ChangePassword now  only show the change forms when Foswiki is managing the passwords (the =configure= setting ={PasswordManager}= set to a manager that handles setting of passwords). 
    121  
    122 If the {PasswordManager} does not support password changing,  the ChangePassword and ResetPassword topics will show a simple message.  This message is defined iby the preference =CHANGEPASSWORDDISABLEDMESSAGE=  in %SYSTEMWEB%.DefaultPreferences. You can redefine this setting by copying  it to %USERSWEB%.SitePreferences and change it to include a link to the password management website of your organisation. 
    123  
    124 ChangeEmailAddress will now guide the user to define the email address  in the user topic when the !PasswordManager does not handle hidden email addresses, so you should not need to tailor this topic any longer. 
     113The topics %SYSTEMWEB%.ResetPassword and %SYSTEMWEB%.ChangePassword now only show the change forms when Foswiki is managing the passwords (the =configure= setting ={PasswordManager}= set to a manager that handles setting of passwords). 
     114 
     115If the {PasswordManager} does not support password changing, the ChangePassword and ResetPassword topics will show a simple message. This message is defined iby the preference =CHANGEPASSWORDDISABLEDMESSAGE= in %SYSTEMWEB%.DefaultPreferences. You can redefine this setting by copying it to %USERSWEB%.SitePreferences and change it to include a link to the password management website of your organisation. 
     116 
     117ChangeEmailAddress will now guide the user to define the email address in the user topic when the !PasswordManager does not handle hidden email addresses, so you should not need to tailor this topic any longer. 
    125118 
    126119---+++ TMPL:DEFs may now access previous (overridden) TMPL:DEF 
    … …  
    132125   * =working/logs/configure.log= 
    133126   * =working/logs/events.log= 
    134     
     127  
    135128It is possible to monitor these logs with a product like =fail2ban= which will set firewall filters due to excessive failures. 
    136129 
    … …  
    143136Because of prior inconsistencies in the files distributed with Foswiki and TWiki core and extensions, migration of older Foswiki or TWiki installs may see excessive errors reported by configure. You are recommended to correct the file system permissions.  
    144137 
    145 ---+++ Newer modern Icon set for DocumentGraphics. 
     138---+++ Newer modern Icon set for Document Graphics. 
    146139To celebrate our new look, project and momentum, Foswiki now has a new ICON set to update the one shipped for the last 10 years. Using the !FamFamFam icon set, augmented with icons from other leading graphic artists. 
    147140 
    … …  
    177170Access checking has been moved from Store up to the Meta and Func routines. This was done to improve perfomance of the Store backend and simplify implementation of different stores e.g. using databases. 
    178171 
    179 Store was never part of the Foswiki or TWiki API.  Extensions which violate this API and reference =Store::= functions directly could potentially have access that was previously blocked by Foswiki and/or may require other changes to be compatible with Foswiki 1.1. 
    180  
    181 Extension authors should first try to use the =Foswiki::Func= API.  This is the preferred API. Pay careful attention to whether or not each =Func::= method verifies access control and use the =Foswiki::Func::checkAccessPermission= to verify access. 
    182  
    183 =Foswiki::Meta= should be used only if =Foswiki::Func= does not have a needed function. Note that =Foswiki::Meta= functions do not implicitly perform any access control checks.  Callers of =Foswiki::Meta== should first use the =Foswiki::Meta::haveAccess=  function to verify access for the planned actions. This was done by design to reduce repetitive access control checks and improve performance. 
     172Store was never part of the Foswiki or TWiki API. Extensions which violate this API and reference =Store::= functions directly could potentially have access that was previously blocked by Foswiki and/or may require other changes to be compatible with Foswiki 1.1. 
     173 
     174Extension authors should first try to use the =Foswiki::Func= API. This is the preferred API. Pay careful attention to whether or not each =Func::= method verifies access control and use the =Foswiki::Func::checkAccessPermission= to verify access. 
     175 
     176=Foswiki::Meta= should be used only if =Foswiki::Func= does not have a needed function. Note that =Foswiki::Meta= functions do not implicitly perform any access control checks. Callers of =Foswiki::Meta== should first use the =Foswiki::Meta::haveAccess= function to verify access for the planned actions. This was done by design to reduce repetitive access control checks and improve performance. 
    184177 
    185178---++++ Tainting 
Note: See TracChangeset for help on using the changeset viewer.