You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Craig L Russell <Cr...@Sun.COM> on 2008/12/20 17:48:00 UTC
Movin' along
We haven't had the discussion for a little while, so I thought I'd see
what the big picture is.
Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
and user interaction, so let's now focus on getting "the big one" done.
I can't find the plan for changing package names and making an
official Apache release. I know we discussed it but can't seem to
locate it.
Craig
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Florian Holeczek <fl...@holeczek.de>.
> Any updates since 12-November?
Well, Andrew has already been committing lots of Stripes stuff to the
trunk but isn't done yet. Janne is doing the JCR work on an extra
branch.
Florian
Re: Movin' along
Posted by Craig L Russell <Cr...@Sun.COM>.
Any updates since 12-November?
Craig
On Dec 20, 2008, at 9:23 AM, Florian Holeczek wrote:
> Hi Craig,
>
> AFAIK all discussion on this topic was done under
> https://issues.apache.org/jira/browse/JSPWIKI-38
>
> Regards
> Florian
>
> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>> We haven't had the discussion for a little while, so I thought I'd
>> see
>> what the big picture is.
>
>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
>> and user interaction, so let's now focus on getting "the big one"
>> done.
>
>> I can't find the plan for changing package names and making an
>> official Apache release. I know we discussed it but can't seem to
>> locate it.
>
>> Craig
>
>> Craig L Russell
>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
They probably consulted an oracle somewhere.
Frankly, I have no idea :-)
/Janne
On Dec 20, 2008, at 20:05 , Florian Holeczek wrote:
> Hi Janne,
>
> BTW, the german computer magazine iX wrote that the project will
> incubate to a "real" Apache project still in 2008. Any idea where this
> information could come from?
>
> Regards
> Florian
>
> Ursprüngliche Nachricht vom 20.12.2008 um 18:56:
>
>> We'll need more than that - I think we need to release at least once
>> from incubator in order to graduate.
>
>> And that means a stable 3.0...
>
>> (I'd like to do the JCR integration work before the rename - or at
>> least merge it with the trunk before that is done. I've been trying
>> to do it slowly by starting to use the org.apache.jspwiki.api
>> package... I'm going to move WikiPage there pretty soon - probably
>> today/tomorrow. Also, I would like folks to *really* review the API
>> package - so far I haven't had too many comments.)
>
>> /Janne
>
>> On Dec 20, 2008, at 19:42 , Andrew Jaquith wrote:
>
>>> I would support doing the big package renames soon. Most of my work
>>> now is in the JSP tier, and won't be affected too much. (The
>>> Stripes integration code is already in trunk.)
>>>
>>> On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de>
>>> wrote:
>>>
>>>> Hi Craig,
>>>>
>>>> AFAIK all discussion on this topic was done under
>>>> https://issues.apache.org/jira/browse/JSPWIKI-38
>>>>
>>>> Regards
>>>> Florian
>>>>
>>>> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>>>>> We haven't had the discussion for a little while, so I thought
>>>>> I'd see
>>>>> what the big picture is.
>>>>
>>>>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good
>>>>> community
>>>>> and user interaction, so let's now focus on getting "the big one"
>>>>> done.
>>>>
>>>>> I can't find the plan for changing package names and making an
>>>>> official Apache release. I know we discussed it but can't seem to
>>>>> locate it.
>>>>
>>>>> Craig
>>>>
>>>>> Craig L Russell
>>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>>> P.S. A good JDO? O, Gasp!
>>>>
>
Re: Movin' along
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi Janne,
BTW, the german computer magazine iX wrote that the project will
incubate to a "real" Apache project still in 2008. Any idea where this
information could come from?
Regards
Florian
Ursprüngliche Nachricht vom 20.12.2008 um 18:56:
> We'll need more than that - I think we need to release at least once
> from incubator in order to graduate.
> And that means a stable 3.0...
> (I'd like to do the JCR integration work before the rename - or at
> least merge it with the trunk before that is done. I've been trying
> to do it slowly by starting to use the org.apache.jspwiki.api
> package... I'm going to move WikiPage there pretty soon - probably
> today/tomorrow. Also, I would like folks to *really* review the API
> package - so far I haven't had too many comments.)
> /Janne
> On Dec 20, 2008, at 19:42 , Andrew Jaquith wrote:
>> I would support doing the big package renames soon. Most of my work
>> now is in the JSP tier, and won't be affected too much. (The
>> Stripes integration code is already in trunk.)
>>
>> On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de>
>> wrote:
>>
>>> Hi Craig,
>>>
>>> AFAIK all discussion on this topic was done under
>>> https://issues.apache.org/jira/browse/JSPWIKI-38
>>>
>>> Regards
>>> Florian
>>>
>>> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>>>> We haven't had the discussion for a little while, so I thought
>>>> I'd see
>>>> what the big picture is.
>>>
>>>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
>>>> and user interaction, so let's now focus on getting "the big one"
>>>> done.
>>>
>>>> I can't find the plan for changing package names and making an
>>>> official Apache release. I know we discussed it but can't seem to
>>>> locate it.
>>>
>>>> Craig
>>>
>>>> Craig L Russell
>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>> P.S. A good JDO? O, Gasp!
>>>
Re: Movin' along
Posted by Dirk Frederickx <di...@gmail.com>.
Janne, e.a.
I'm working on a replacement of the posteditor.
This should be ok for inclusion in v3.0-incubating-something.
dirk
On Sun, Dec 21, 2008 at 1:08 PM, Janne Jalkanen
<Ja...@ecyrd.com> wrote:
>
>>
>> You betcha! An Apache release can even be broken code (although generally
>> we discourage that). As long as the community wants to release, we release.
>> We get lots of help from the mentors and the rest of the incubator PMC to be
>> sure that what we release is properly identified as Apache licensed or has a
>> compatible license and out we go.
>
> Very good - I was under the impression that Apache releases need to be
> stable. If that is the case, then we can probably release a lot earlier.
> It'll just have to be a "3.0.0-incubating-alpha-1" or something.
>
> Then we really only have a couple of gating issues - one of them being the
> posteditor.js thing (JSPWIKI-382), where the license is possibly not
> Apache-compatible.
>
> /Janne
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
>
> You betcha! An Apache release can even be broken code (although
> generally we discourage that). As long as the community wants to
> release, we release. We get lots of help from the mentors and the
> rest of the incubator PMC to be sure that what we release is
> properly identified as Apache licensed or has a compatible license
> and out we go.
Very good - I was under the impression that Apache releases need to
be stable. If that is the case, then we can probably release a lot
earlier. It'll just have to be a "3.0.0-incubating-alpha-1" or
something.
Then we really only have a couple of gating issues - one of them
being the posteditor.js thing (JSPWIKI-382), where the license is
possibly not Apache-compatible.
/Janne
Re: Movin' along
Posted by Craig L Russell <Cr...@Sun.COM>.
On Dec 20, 2008, at 2:27 PM, Janne Jalkanen wrote:
>> Are you saying you want to wait until all the 40 plus-things-we-
>> haven't-found-yet have been fixed before renaming, or before
>> release? I hope it's the latter.
>
> Release. The only reason we don't want to rename now is that
> merging back the JCR branch would be a pain.
>
>> At some point, 3.0 will need to have a first release, which is
>> really what the incubator is best at. Call it -alpha, call it -
>> earlyaccess, call it anything, but release it as an Apache release.
>
> Hm? We can do that?
You betcha! An Apache release can even be broken code (although
generally we discourage that). As long as the community wants to
release, we release. We get lots of help from the mentors and the rest
of the incubator PMC to be sure that what we release is properly
identified as Apache licensed or has a compatible license and out we go.
Craig
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Janne,
some estimates regarding "how much time is left for hacking JSPWiki when
you have your first kid" - initially none and later on you might hack
between 22:00 to 24:00 ... ;-)
Cheers,
Siegfried Goeschl
Father of two remarkable girls
Late Night Apache Hacker
Janne Jalkanen wrote:
>> I've found @since tags to be valuable as a way to see what's changed.
>> Especially useful for migrating plugins from earlier releases. I
>> don't see anything wrong with adding @since 3.0.0 to new APIs and
>> tagging the others with e.g. 2.8.0 for features that were in 2.8,
>> even though they were in a class instead of an interface.
>
> Actually, my problem is with @author-tags... I think they are useless
> and potentially dangerous at this point. Here's a nice presentation
> from the Subversion team (it's a good presentation, and this
> particular topic starts at about 17m30s. Very recommended watching.)
>
> http://video.google.com/videoplay?docid=-4216011961522818645
>
>> There's really nothing else to do before releasing. The release
>> process from the incubator is mainly an exercise in reviewing the
>> release package to make sure that all code is legally releasable
>> under the Apache license (code developed or donated to the project
>> itself) or compatible licenses (code developed elsewhere and released
>> as part of the package for convenience, e.g. the lib directory jar
>> files).
>
> OK.
>
> Unfortunately, I've run out of time. I currently got the following
> things on my plate:
>
> * JCR integration
> * bug triage (on the issue tracker)
> * Apache graduation
> * 3.0 refactoring
> * general participation on the mailing lists; responding to user
> questions, etc.
>
> I also have a book project which is now overdue, and on which I will
> have to concentrate from now on until it is in better shape. Our
> first child is also due in about four weeks, and there's a lot of
> practical stuff to be done still. And unfortunately, these two have
> to take precendence over JSPWiki hacking.
>
> I was hoping to get the JCR integration done before the Christmas
> holidays, but unfortunately I hit some major snags, which will need
> some rethinking. Like the fact that in order to get a WikiPage, you
> need a WikiContext; and in order to get a WikiContext, you need a
> WikiPage... Versioning is also a pain.
>
> At any rate, with respect to graduation, this is not good news unless
> someone else can take the load off me. Since getting a kid is a new
> situation for me, I can't even give an estimate on how much time I
> possibly have for hacking. But at any rate, don't expect a whole lot
> of responses from me in the next few months. I am going to
> concentrate on the JCR integration, and just ignore a lot of the other
> stuff.
>
> Unfortunately, free time is a limited resource, so others will need to
> step up now.
>
> /Janne
>
>
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
> I've found @since tags to be valuable as a way to see what's
> changed. Especially useful for migrating plugins from earlier
> releases. I don't see anything wrong with adding @since 3.0.0 to
> new APIs and tagging the others with e.g. 2.8.0 for features that
> were in 2.8, even though they were in a class instead of an interface.
Actually, my problem is with @author-tags... I think they are
useless and potentially dangerous at this point. Here's a nice
presentation from the Subversion team (it's a good presentation, and
this particular topic starts at about 17m30s. Very recommended
watching.)
http://video.google.com/videoplay?docid=-4216011961522818645
> There's really nothing else to do before releasing. The release
> process from the incubator is mainly an exercise in reviewing the
> release package to make sure that all code is legally releasable
> under the Apache license (code developed or donated to the project
> itself) or compatible licenses (code developed elsewhere and
> released as part of the package for convenience, e.g. the lib
> directory jar files).
OK.
Unfortunately, I've run out of time. I currently got the following
things on my plate:
* JCR integration
* bug triage (on the issue tracker)
* Apache graduation
* 3.0 refactoring
* general participation on the mailing lists; responding to user
questions, etc.
I also have a book project which is now overdue, and on which I will
have to concentrate from now on until it is in better shape. Our
first child is also due in about four weeks, and there's a lot of
practical stuff to be done still. And unfortunately, these two have
to take precendence over JSPWiki hacking.
I was hoping to get the JCR integration done before the Christmas
holidays, but unfortunately I hit some major snags, which will need
some rethinking. Like the fact that in order to get a WikiPage, you
need a WikiContext; and in order to get a WikiContext, you need a
WikiPage... Versioning is also a pain.
At any rate, with respect to graduation, this is not good news unless
someone else can take the load off me. Since getting a kid is a new
situation for me, I can't even give an estimate on how much time I
possibly have for hacking. But at any rate, don't expect a whole lot
of responses from me in the next few months. I am going to
concentrate on the JCR integration, and just ignore a lot of the
other stuff.
Unfortunately, free time is a limited resource, so others will need
to step up now.
/Janne
Re: Movin' along
Posted by Craig L Russell <Cr...@Sun.COM>.
On Dec 21, 2008, at 8:23 AM, Janne Jalkanen wrote:
>> - I committed a few typo corrections, not important
>> - there should be package documentation, which tells the reader
>> at least
>> what you just said: *org.apache.jspwiki.api.* is the one you can
>> rely on.
>
> Yup, good point.
+1 Regardless of how we name the api that can be relied on (see
discussion at https://issues.apache.org/jira/browse/JSPWIKI-38 ) the
package doc should indicate which APIs are intended to be stable.
>
>> - do we need all the @since tags ?
>
> I'm still wondering whether they should refer to API versions.
I've found @since tags to be valuable as a way to see what's changed.
Especially useful for migrating plugins from earlier releases. I don't
see anything wrong with adding @since 3.0.0 to new APIs and tagging
the others with e.g. 2.8.0 for features that were in 2.8, even though
they were in a class instead of an interface.
But I'm not a user voice, so take this as a mild suggestion for
discussion not a recommendation.
>
> BTW, I created a new issue: https://issues.apache.org/jira/browse/JSPWIKI-461
> for tracking what should be done before an incubating release. I
> think there are still several administrative issues (like whatever
> status raports, etc). Then we probably need an issue for graduation
> as well. I trust our mentors can review and tell us what stuff is
> missing?
There's really nothing else to do before releasing. The release
process from the incubator is mainly an exercise in reviewing the
release package to make sure that all code is legally releasable under
the Apache license (code developed or donated to the project itself)
or compatible licenses (code developed elsewhere and released as part
of the package for convenience, e.g. the lib directory jar files).
The process that I observed Janne perform while verifying the
provenance of the code that was imported simply needs to be documented
in the status file incubator/trunk/site-author/projects/jspwiki.xml.
IIRC, the items identified as Copyright and Distribution Rights need
to be dated as of the date the work was completed.
Craig
>
>
> /Janne
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
> - I committed a few typo corrections, not important
> - there should be package documentation, which tells the reader
> at least
> what you just said: *org.apache.jspwiki.api.* is the one you can
> rely on.
Yup, good point.
> Everything else *we will consider breakable without notice*.*
> - WikiPage.getAcl() and .setAcl() refer to an ACL object which
> is outside
> the API package, that should not happen ?
True. I think we should move the Acl and AclEntry classes into
org.apache.jspwiki.api.acl, yes?
> - WikiPage.getWiki() should indeed be renamed to
> WikiPage.getWikiName()
I think I would prefer getSpace().
> - do we need all the @since tags ?
I'm still wondering whether they should refer to API versions.
> - if ModuleData is only about plugins we could probably rename
> it to
> PluginMetaData or something else.
Mmm... I think we need something for filters as well. So it might
make sense to split out some of the annotations out of the ModuleData
which are plugin-specific.
BTW, I created a new issue: https://issues.apache.org/jira/browse/
JSPWIKI-461 for tracking what should be done before an incubating
release. I think there are still several administrative issues (like
whatever status raports, etc). Then we probably need an issue for
graduation as well. I trust our mentors can review and tell us what
stuff is missing?
/Janne
Re: Movin' along
Posted by Harry Metske <ha...@gmail.com>.
I had a look at the API package, just a few quick notes for what it's worth
:
- I committed a few typo corrections, not important
- there should be package documentation, which tells the reader at least
what you just said: *org.apache.jspwiki.api.* is the one you can rely on.
Everything else *we will consider breakable without notice*.*
- WikiPage.getAcl() and .setAcl() refer to an ACL object which is outside
the API package, that should not happen ?
- WikiPage.getWiki() should indeed be renamed to WikiPage.getWikiName()
- do we need all the @since tags ?
- if ModuleData is only about plugins we could probably rename it to
PluginMetaData or something else.
regards,
Harry
2008/12/20 Janne Jalkanen <Ja...@ecyrd.com>
> If it's going to be some time, perhaps it shouldn't gate the rename. I
>> assume that the JCR branch can be renamed as well if it isn't ready to
>> integrate.
>>
>
> I was planning a merge once I get it working, so that people don't have to
> deal with (too) broken code.
>
> But it's still not usable.
>
>>
>> Are you saying you want to wait until all the 40
>> plus-things-we-haven't-found-yet have been fixed before renaming, or before
>> release? I hope it's the latter.
>>
>
> Release. The only reason we don't want to rename now is that merging back
> the JCR branch would be a pain.
>
> At some point, 3.0 will need to have a first release, which is really what
>> the incubator is best at. Call it -alpha, call it -earlyaccess, call it
>> anything, but release it as an Apache release.
>>
>
> Hm? We can do that?
>
> We know that all applications that have plugins will need to change, and
>> it's important to get the code out there so folks have an idea of what they
>> are up against with the rename.
>>
>
> The rename is not the big problem; the API is the big problem. Which is
> why I am worried that nobody else has commented on it...
>
> Just in case people haven't yet realized this - for plugin and filter
> writes, org.apache.jspwiki.api.* is the one you can rely on. Everything
> else *we will consider breakable without notice*.
>
> (And for template writers, org.apache.jspwiki.tags.*, but there's no reason
> to change them, really. So they're already pretty stable.)
>
> /Janne
>
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
> If it's going to be some time, perhaps it shouldn't gate the
> rename. I assume that the JCR branch can be renamed as well if it
> isn't ready to integrate.
I was planning a merge once I get it working, so that people don't
have to deal with (too) broken code.
But it's still not usable.
>
> Are you saying you want to wait until all the 40 plus-things-we-
> haven't-found-yet have been fixed before renaming, or before
> release? I hope it's the latter.
Release. The only reason we don't want to rename now is that merging
back the JCR branch would be a pain.
> At some point, 3.0 will need to have a first release, which is
> really what the incubator is best at. Call it -alpha, call it -
> earlyaccess, call it anything, but release it as an Apache release.
Hm? We can do that?
> We know that all applications that have plugins will need to
> change, and it's important to get the code out there so folks have
> an idea of what they are up against with the rename.
The rename is not the big problem; the API is the big problem. Which
is why I am worried that nobody else has commented on it...
Just in case people haven't yet realized this - for plugin and filter
writes, org.apache.jspwiki.api.* is the one you can rely on.
Everything else *we will consider breakable without notice*.
(And for template writers, org.apache.jspwiki.tags.*, but there's no
reason to change them, really. So they're already pretty stable.)
/Janne
Re: Movin' along
Posted by Craig L Russell <Cr...@Sun.COM>.
On Dec 20, 2008, at 12:59 PM, Janne Jalkanen wrote:
>
> I can't give any estimate. For JCR, it all depends on my wife's
> health and where it goes, which we simply don't know at this stage
> (long story).
If it's going to be some time, perhaps it shouldn't gate the rename. I
assume that the JCR branch can be renamed as well if it isn't ready to
integrate.
>
>
> There are currently over 40 unclosed items for 3.0, and I would
> expect those to be fixed as well.
Are you saying you want to wait until all the 40 plus-things-we-
haven't-found-yet have been fixed before renaming, or before release?
I hope it's the latter.
> (JIRA has a pretty comprehensive list of all issues to be fixed
> prior to 3.0). And, of course, go through the entire alpha-beta
> testing round, which takes a few months.
Of course, but I'm talking specifically about the rename project.
>
>
> Otherwise we will need to release 3.0, and tell people "this is
> otherwise nice but you shouldn't use it because it is broken." :-/
At some point, 3.0 will need to have a first release, which is really
what the incubator is best at. Call it -alpha, call it -earlyaccess,
call it anything, but release it as an Apache release.
We know that all applications that have plugins will need to change,
and it's important to get the code out there so folks have an idea of
what they are up against with the rename.
Craig
>
>
> /Janne
>
> On 20 Dec 2008, at 22:11, Craig L Russell wrote:
>
>> So we're all agreed that the big rename is just pending the JCR
>> integration and a thorough review of the API?
>>
>> When are these expected to be done?
>>
>> Craig
>>
>> On Dec 20, 2008, at 9:56 AM, Janne Jalkanen wrote:
>>
>>>
>>> We'll need more than that - I think we need to release at least
>>> once from incubator in order to graduate.
>>>
>>> And that means a stable 3.0...
>>>
>>> (I'd like to do the JCR integration work before the rename - or at
>>> least merge it with the trunk before that is done. I've been
>>> trying to do it slowly by starting to use the
>>> org.apache.jspwiki.api package... I'm going to move WikiPage there
>>> pretty soon - probably today/tomorrow. Also, I would like folks
>>> to *really* review the API package - so far I haven't had too many
>>> comments.)
>>>
>>> /Janne
>>>
>>> On Dec 20, 2008, at 19:42 , Andrew Jaquith wrote:
>>>
>>>> I would support doing the big package renames soon. Most of my
>>>> work now is in the JSP tier, and won't be affected too much. (The
>>>> Stripes integration code is already in trunk.)
>>>>
>>>> On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de>
>>>> wrote:
>>>>
>>>>> Hi Craig,
>>>>>
>>>>> AFAIK all discussion on this topic was done under
>>>>> https://issues.apache.org/jira/browse/JSPWIKI-38
>>>>>
>>>>> Regards
>>>>> Florian
>>>>>
>>>>> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>>>>>> We haven't had the discussion for a little while, so I thought
>>>>>> I'd see
>>>>>> what the big picture is.
>>>>>
>>>>>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good
>>>>>> community
>>>>>> and user interaction, so let's now focus on getting "the big
>>>>>> one" done.
>>>>>
>>>>>> I can't find the plan for changing package names and making an
>>>>>> official Apache release. I know we discussed it but can't seem to
>>>>>> locate it.
>>>>>
>>>>>> Craig
>>>>>
>>>>>> Craig L Russell
>>>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>>>> P.S. A good JDO? O, Gasp!
>>>>>
>>>
>>
>> Craig L Russell
>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
I can't give any estimate. For JCR, it all depends on my wife's
health and where it goes, which we simply don't know at this stage
(long story).
There are currently over 40 unclosed items for 3.0, and I would
expect those to be fixed as well. (JIRA has a pretty comprehensive
list of all issues to be fixed prior to 3.0). And, of course, go
through the entire alpha-beta testing round, which takes a few months.
Otherwise we will need to release 3.0, and tell people "this is
otherwise nice but you shouldn't use it because it is broken." :-/
/Janne
On 20 Dec 2008, at 22:11, Craig L Russell wrote:
> So we're all agreed that the big rename is just pending the JCR
> integration and a thorough review of the API?
>
> When are these expected to be done?
>
> Craig
>
> On Dec 20, 2008, at 9:56 AM, Janne Jalkanen wrote:
>
>>
>> We'll need more than that - I think we need to release at least
>> once from incubator in order to graduate.
>>
>> And that means a stable 3.0...
>>
>> (I'd like to do the JCR integration work before the rename - or at
>> least merge it with the trunk before that is done. I've been
>> trying to do it slowly by starting to use the
>> org.apache.jspwiki.api package... I'm going to move WikiPage there
>> pretty soon - probably today/tomorrow. Also, I would like folks
>> to *really* review the API package - so far I haven't had too many
>> comments.)
>>
>> /Janne
>>
>> On Dec 20, 2008, at 19:42 , Andrew Jaquith wrote:
>>
>>> I would support doing the big package renames soon. Most of my
>>> work now is in the JSP tier, and won't be affected too much. (The
>>> Stripes integration code is already in trunk.)
>>>
>>> On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de>
>>> wrote:
>>>
>>>> Hi Craig,
>>>>
>>>> AFAIK all discussion on this topic was done under
>>>> https://issues.apache.org/jira/browse/JSPWIKI-38
>>>>
>>>> Regards
>>>> Florian
>>>>
>>>> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>>>>> We haven't had the discussion for a little while, so I thought
>>>>> I'd see
>>>>> what the big picture is.
>>>>
>>>>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good
>>>>> community
>>>>> and user interaction, so let's now focus on getting "the big
>>>>> one" done.
>>>>
>>>>> I can't find the plan for changing package names and making an
>>>>> official Apache release. I know we discussed it but can't seem to
>>>>> locate it.
>>>>
>>>>> Craig
>>>>
>>>>> Craig L Russell
>>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>>> P.S. A good JDO? O, Gasp!
>>>>
>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Craig L Russell <Cr...@Sun.COM>.
So we're all agreed that the big rename is just pending the JCR
integration and a thorough review of the API?
When are these expected to be done?
Craig
On Dec 20, 2008, at 9:56 AM, Janne Jalkanen wrote:
>
> We'll need more than that - I think we need to release at least once
> from incubator in order to graduate.
>
> And that means a stable 3.0...
>
> (I'd like to do the JCR integration work before the rename - or at
> least merge it with the trunk before that is done. I've been trying
> to do it slowly by starting to use the org.apache.jspwiki.api
> package... I'm going to move WikiPage there pretty soon - probably
> today/tomorrow. Also, I would like folks to *really* review the API
> package - so far I haven't had too many comments.)
>
> /Janne
>
> On Dec 20, 2008, at 19:42 , Andrew Jaquith wrote:
>
>> I would support doing the big package renames soon. Most of my work
>> now is in the JSP tier, and won't be affected too much. (The
>> Stripes integration code is already in trunk.)
>>
>> On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de>
>> wrote:
>>
>>> Hi Craig,
>>>
>>> AFAIK all discussion on this topic was done under
>>> https://issues.apache.org/jira/browse/JSPWIKI-38
>>>
>>> Regards
>>> Florian
>>>
>>> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>>>> We haven't had the discussion for a little while, so I thought
>>>> I'd see
>>>> what the big picture is.
>>>
>>>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
>>>> and user interaction, so let's now focus on getting "the big one"
>>>> done.
>>>
>>>> I can't find the plan for changing package names and making an
>>>> official Apache release. I know we discussed it but can't seem to
>>>> locate it.
>>>
>>>> Craig
>>>
>>>> Craig L Russell
>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>> P.S. A good JDO? O, Gasp!
>>>
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Movin' along
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
We'll need more than that - I think we need to release at least once
from incubator in order to graduate.
And that means a stable 3.0...
(I'd like to do the JCR integration work before the rename - or at
least merge it with the trunk before that is done. I've been trying
to do it slowly by starting to use the org.apache.jspwiki.api
package... I'm going to move WikiPage there pretty soon - probably
today/tomorrow. Also, I would like folks to *really* review the API
package - so far I haven't had too many comments.)
/Janne
On Dec 20, 2008, at 19:42 , Andrew Jaquith wrote:
> I would support doing the big package renames soon. Most of my work
> now is in the JSP tier, and won't be affected too much. (The
> Stripes integration code is already in trunk.)
>
> On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de>
> wrote:
>
>> Hi Craig,
>>
>> AFAIK all discussion on this topic was done under
>> https://issues.apache.org/jira/browse/JSPWIKI-38
>>
>> Regards
>> Florian
>>
>> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>>> We haven't had the discussion for a little while, so I thought
>>> I'd see
>>> what the big picture is.
>>
>>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
>>> and user interaction, so let's now focus on getting "the big one"
>>> done.
>>
>>> I can't find the plan for changing package names and making an
>>> official Apache release. I know we discussed it but can't seem to
>>> locate it.
>>
>>> Craig
>>
>>> Craig L Russell
>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>
Re: Movin' along
Posted by Andrew Jaquith <an...@gmail.com>.
I would support doing the big package renames soon. Most of my work
now is in the JSP tier, and won't be affected too much. (The Stripes
integration code is already in trunk.)
On Dec 20, 2008, at 12:23, Florian Holeczek <fl...@holeczek.de> wrote:
> Hi Craig,
>
> AFAIK all discussion on this topic was done under
> https://issues.apache.org/jira/browse/JSPWIKI-38
>
> Regards
> Florian
>
> Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
>> We haven't had the discussion for a little while, so I thought I'd
>> see
>> what the big picture is.
>
>> Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
>> and user interaction, so let's now focus on getting "the big one"
>> done.
>
>> I can't find the plan for changing package names and making an
>> official Apache release. I know we discussed it but can't seem to
>> locate it.
>
>> Craig
>
>> Craig L Russell
>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>
Re: Movin' along
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi Craig,
AFAIK all discussion on this topic was done under
https://issues.apache.org/jira/browse/JSPWIKI-38
Regards
Florian
Ursprüngliche Nachricht vom 20.12.2008 um 17:48:
> We haven't had the discussion for a little while, so I thought I'd see
> what the big picture is.
> Jspwiki 2.8.1 is out, lots of activity in the trunk, good community
> and user interaction, so let's now focus on getting "the big one" done.
> I can't find the plan for changing package names and making an
> official Apache release. I know we discussed it but can't seem to
> locate it.
> Craig
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!