Mailing-List: contact jspwiki-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jspwiki-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of terry@net-frame.com
 designates 65.212.180.79 as permitted sender)
Message-ID: <477D1683.30901@net-frame.com>
Date: Thu, 03 Jan 2008 12:08:19 -0500
From: Terry Steichen <terry@net-frame.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: jspwiki-user@incubator.apache.org
Subject: Change Management Suggestion (was: EmoticonsFilter in 2.6.0)
References: <1072682541.20080103141952@holeczek.de>
 <20080103134622.GA22212@ecyrd.com> <477CFA72.9040606@net-frame.com>
 <20080103161053.GC26535@ecyrd.com>
In-Reply-To: <20080103161053.GC26535@ecyrd.com>
Content-Type: multipart/alternative;
 boundary="------------060505060603050202000800"

--------------060505060603050202000800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Janne,

I don't think the problem is that you weren't "loud" enough.

Because I'm testing a fully operational JSPWiki-based system, I have 
been running the 'stable version' (2.4.xx) as suggested.  The neat new 
stuff in the 2.5.xx releases just took too much time to figure out, and 
caused too much instability as the bugs and feature parameters were 
being worked through.

In the future, when preparing a new release such as 2.6.0, we should 
probably emphasize the need to test the pending new release against the 
most recent *stable* version (ie, 2.4.x in this case), as well as versus 
the *cutting edge* version (2.5.xx). 

In this regard, do you have any idea of how many (if any) 2.6.0 testers 
so far have used code customized to 2.4.xx (templates, filters, plugins, 
etc.) versus 2.5.xx stuff? 

 From a personal standpoint, this transition (to 2.6.0) is making me 
increasingly nervous, because I don't know how to anticipate which of 
the (many) 2.5.xx changes might be incompatible with 2.4.xx.  In 
hindsight, I probably should have jumped in with testing of my own, but 
I had thought the changes affecting APIs and such were being normalized 
both ways between 2.4.x and 2.5.x.  Maybe that wasn't realistic, but 
that was my (obviously naive) belief.  Or, maybe the stable version was 
moved up to a more recent 2.4 release, and I missed it?

Terry

Janne Jalkanen wrote:
>> This seems like a pretty important change (that filters no longer work), 
>> yet this is the first I've heard of it.  I make extensive use of 
>> filters, and that means that I'll have to wait a bit longer before I 
>> really scrub through 2.6.0.  (Hope there aren't any more surprises like 
>> this.)
>>     
>
> This modification was made nine months ago.
>
> 2007-03-18  Janne Jalkanen  <Janne.Jalkanen@ecyrd.com>
>
>         * 2.5.30
>
>         * Fixed BugReferenceToRenamedPageNotCleared
>
>         * Fixed BugTableHeaderNotXHMTLCompliant
>
>         * Fixed BugInitializablePluginNotInitialized
>
>         * API Change: The signature of PageFilter.initialize() now
>         also includes the WikiEngine.  This was necessary, because otherwise
>         the initialize() -method was essentially useless for most use
>         cases.
>
> Sorry for not being louder about it, but yeah, it's been there and
> visible for everyone since last March.
>
> Also, JSPWiki 2.5.x has been in beta since last July (that is 6
> months).  This is exactly the kind of stuff I would like people to
> catch when I say "it's out in beta, please test".  There have been
> LOADS of changes under the hood, and we just can't remember to type up
> everything.  Anyone trying out their old filters on any of the betas
> would have caught this, muttered about it, and we would've remembered
> to put it on the WhatsNewIn2.6 list.
>
> It's there now.
>
> /Janne
>
>   

--------------060505060603050202000800--