I had a few other small things, notably mostly serializing the
workflow classes except for those methods that would actually require
us to make real changes to things (read: last week's long conversation
about serializing workflows). Thought it would be a good forwards-
compatible thing to do.
(I've actually documented this in UPGRADING already; just haven't
checked in the bits...)
On Jul 1, 2008, at 1:49 AM, Janne Jalkanen wrote:
Um... What do you want to check in that particular file? I think
adding new stuff in the build.xml is fine...
/Janne
On 1 Jul 2008, at 00:40, Andrew Jaquith wrote:
Did the API diff earlier today. If I knew what to change in
Release.java now that we are alpha, I'd check in the Ant task that
does the API diffing right now... :)
Janne, what do I change in order to check in post-alpha stuff?
On Jun 30, 2008, at 5:25 PM, Janne Jalkanen wrote:
On Jul 1, 2008, at 00:13 , Murray Altheim wrote:
Janne Jalkanen wrote:
It's done. JSPWiki 2.8.0-alpha-1 is now available at http://www.jspwiki.org/wiki/JSPWikiDownload
, and also under the jspwiki_2_8_0_alpha_1.
Code-wise, is this (at this point) an exact match for an existing
package, e.g., 2.6.3? IOW, if one were to substitute 2.8.0-alpha-1
things wouldn't break except for package name changes?
If so this would be a good time for me to begin converting all my
plugins.
Not even that - we're still under com.ecyrd.jspwiki. Let's break
everything in one go in 3.0...
I *think* 2.6 and 2.8 should be fully API compatible.
/Janne
