You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Ate Douma <at...@douma.nu> on 2005/03/21 22:31:01 UTC
J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
David Sean Taylor wrote:
> Hema Menon wrote:
>
>> Hi,
>>
>> I have been trying to get our Struts application under JS1.6 with
>> Fusion. Here's the env
>> Latest JS 1.6 build from CVS
>> Struts-portal bridge 0.2 version.
>>
>> I find that the application runs as a standalone using Portal bridges
>> 0.2, which means that the portalbridges work as expected outside of
>> Jetspeed. However inside Jetspeed, the lookup dispatch action fails.
>> THE INTERESTING FACT IS THAT IF I DEPLOY THIS APPLICATION ON JETSPEED
>> 2, IT WORKS AS EXPECTED. This makes me believe that the Jetspeed 1.6
>> with Fusion is causing the problem.
>>
>> I believe there are changes in Struts bridge 0.2 version, which
>> require it to run with JS-M2 files. However any time, I build Jetspeed
>> 1.6 with fusion, I find that the jetspeed.war contains M1 files. I
>> have removed the M1 jars from TOMCAT shared/lib directory. However
>> since JS1.6 is being build against M1 jars, I cannot remove what's in
>> the jetspeed war.
>>
>> Here's my situation, Please help
>> - All our portlets are JS1.5 compliant and we are quite happy with it
>> - We cannot move to JS2 immediately since it means changing to JSR168
>> portlets
>> - We need support for Struts portlet
>> - JS1.6 WITH FUSION, was the perfect solution for us since it would
>> suit all our needs.
>> - However, if the struts portlet does not work as expected in JS1.6
>> with Fusion, I don't know what option does we have :(
>>
>> The changes is Struts-portlet bridge is very very important and neat,
>> since it requires minor changes to our Struts application. But JS1.6
>> with Fusion is equally important to us for deploying it. Somehow I
>> find that JS1.6 With Fusion on JS2M1 jars does not seem to be running
>> right. I am not sure what option do I have :(
>>
>> Can you please let us know what your plans are regarding to JS1.6 on
>> Fusion. Thanks for reading a long email, forgive me, I am desperate :(
>>
>
> Im sorry about your situation.
> I recommend running Fusion against the M1 release.
> Recently, the dependencies in Fusion were upgraded to match Jetspeed-2's
> Spring dependencies. This may be causing some problems. Try checking out
> Fusion from the same time as the M1 release.
>
> Im in a situation here myself and not finding any time for Jetspeed.
> 'Up to my ears in it' as they say :(
> Really hope to free up next week some, and by the first week in April I
> will get Fusion fixed up and released. Im sorry but thats the best I can
> do right now. If someone else wants to step up and release Fusion before
> then, please do so!
>
I want to propose the following:
- I like to call a vote on merging the J2 deployment_refactoring branch with
CVS HEAD before the end of *this week*
- if/once the deployment_refactoring branch is merged, I'll step up and work
on getting Fusion running again with the current J2 CVS HEAD. I'll try
to do so within a few days, (the sooner we decide if/when to merge the
branch the more time I will have for it)
Precondition for success though is that there are not other blocking issues
with Fusion to get it working again. I don't know. Community, David?
Getting help from some of you currently working with Fusion might help too:
Hema, Jeff?
- Hopefully, beginning next week we have both J2 and Fusion in sync again
- If all works out well, I'll propose to do a J2-M2 release as well as a
Fusion 1.6 release next weekend (!) as I can dedicate most of my time that
weekend doing the release.
I haven't done a release before though, so getting at least some help from
someone from the team with previous experience will be important I think.
- Furthermore, I'd like to propose to do releases more often (say once every
month, maybe two) at least until we reach J2-final.
The next release (M3) could contain the portlet selector (customizer)
from David if he won't be able to commit it in time for M2.
Furthermore, we should try to get most of the outstanding bugs fixed by then.
I'm willing to work on that a lot.
- Furthermore, I am going to spend more time in April on writing documentation
as the community really is in dire need of it. I'd say the M3 release should
contain enough documentation to allow new users to start working with J2
on their own.
Hopefully, other team members and/or active community users can step up too
in providing more documentation...
I know this list is quite ambitious, but well, I am ;-)
Anyone like to comment?
Regards, Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
David Sean Taylor wrote:
> Ate Douma wrote:
>
>>>
>> I want to propose the following:
>> - I like to call a vote on merging the J2 deployment_refactoring
>> branch with
>> CVS HEAD before the end of *this week*
>
>
> I don't see the need to impose a deadline on yourself.
> Personally I have enough deadlines as is.
> Why don't we just say "call a vote on merging the deployment_refactoring
> branch" and then you get it done when it gets done.
I'm not calling on anyone else for doing the merge or helping me out with it.
I think I can handle it myself without much problems as I monitored the changes
to CVS HEAD since I started the branch and there isn't anything really conflicting
committed yet. So I expect the merge to be swift and easy to do.
As for imposing a deadline on myself, I can handle that just fine myself too, thank you ;-)
>
> My vote is +1
Thanks!
>
>> - if/once the deployment_refactoring branch is merged, I'll step up
>> and work
>> on getting Fusion running again with the current J2 CVS HEAD. I'll try
>> to do so within a few days, (the sooner we decide if/when to merge the
>> branch the more time I will have for it)
>> Precondition for success though is that there are not other blocking
>> issues
>> with Fusion to get it working again. I don't know. Community, David?
>
>
> Ive seen a few bug reports recently that make me wonder if I ever got
> everything working properly after the navigational state conversion. My
> work with Fusion pretty much ended in September 2004. I can say I was
> confident at that point. Right now Im not, and I haven't been testing
> against the J2 head. We can always fallback to a 1.6 release with M1.
>
> The only real issue is that your new branch will break Fusion in the CVS
> head.
Ok, I'll see to that once I merged the branch and handle other/new issues
when they present themselves.
I intend to create a temporarily branch in Fusion too to work on so it will
be easier for others to help out testing it as well as protecting the
current Fusion HEAD until the synchronization is done.
>
>> Getting help from some of you currently working with Fusion might
>> help too:
>> Hema, Jeff?
>> - Hopefully, beginning next week we have both J2 and Fusion in sync again
>> - If all works out well, I'll propose to do a J2-M2 release as well as a
>> Fusion 1.6 release next weekend (!) as I can dedicate most of my
>> time that
>> weekend doing the release.
>> I haven't done a release before though, so getting at least some
>> help from
>> someone from the team with previous experience will be important I
>> think.
>
>
> Next weekend? Do you mean the weekend of April 2-3?
> April 2-3 is perfect for me, as my family is out of town that weekend
> and Im free to work on the release with you.
Great! Yes I meant April 2-3.
So, if all works out as expected we have a date ;-)
>
>> - Furthermore, I'd like to propose to do releases more often (say once
>> every
>> month, maybe two) at least until we reach J2-final.
>
> +1
>
>> The next release (M3) could contain the portlet selector (customizer)
>> from David if he won't be able to commit it in time for M2.
>
>
> Im shooting for M2, we'll see...
>
>> Furthermore, we should try to get most of the outstanding bugs fixed
>> by then.
>> I'm willing to work on that a lot.
>> - Furthermore, I am going to spend more time in April on writing
>> documentation
>> as the community really is in dire need of it. I'd say the M3
>> release should
>> contain enough documentation to allow new users to start working
>> with J2
>> on their own.
>> Hopefully, other team members and/or active community users can step
>> up too
>> in providing more documentation...
>>
> I think we should all help out with the documentation.
> Its too much work for one person and its also best to get input from
> more than one person. If any non-committers want to help out you are
> very welcome to send documentation patches
I don't intend to write the whole lot myself :-)
But I will make it top priority in my todo list for J2.
>
>> I know this list is quite ambitious, but well, I am ;-)
>> Anyone like to comment?
>>
> Ambitious Ate! Right on!
> You're inspiring me too
:-)
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
Scott T Weaver wrote:
>
>>-----Original Message-----
>>From: David Sean Taylor [mailto:david@bluesunrise.com]
>>Sent: Monday, March 21, 2005 10:55 PM
>>To: Jetspeed Developers List
>>Subject: Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-
>>Bridge & Fusion - David/Ate/others- Pls comment)
>>
>>Ate Douma wrote:
>>
>
> ...
>
>
>>>- If all works out well, I'll propose to do a J2-M2 release as well as a
>>> Fusion 1.6 release next weekend (!) as I can dedicate most of my time
>>>that
>>> weekend doing the release.
>>> I haven't done a release before though, so getting at least some help
>>>from
>>> someone from the team with previous experience will be important I
>>
>>think.
>>
>>Next weekend? Do you mean the weekend of April 2-3?
>>April 2-3 is perfect for me, as my family is out of town that weekend
>>and Im free to work on the release with you.
>
>
> Ill offer my services as well seeing I have been pretty much MIA in regards
> to the project as of late and feel pretty bad about that.
Great! With both David's and your help, nothing can go wrong anymore, is it? ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Scott T Weaver <sc...@binary-designs.net>.
Thanks!
-scott
> -----Original Message-----
> From: Raphaël Luta [mailto:raphael@apache.org]
> Sent: Tuesday, March 22, 2005 10:16 AM
> To: Jetspeed Developers List
> Subject: Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-
> Bridge & Fusion - David/Ate/others- Pls comment)
>
> Of course, give me a few days to put everything in shape though.
>
> Scott T Weaver wrote:
> > Great! Would it be possible for me to get copy of the Jetspeed 2
> Forrest
> > source to "play" with ;)
> >
> > -scott
> >
> >
> >>-----Original Message-----
> >>From: Raphaël Luta [mailto:raphael@apache.org]
> >>Sent: Tuesday, March 22, 2005 9:57 AM
> >>To: Jetspeed Developers List
> >>Subject: Re: J2/Fusion synchronisation and release plan (Was: Re:
> Struts-
> >>Bridge & Fusion - David/Ate/others- Pls comment)
> >>
> >>Scott T Weaver wrote:
> >>
> >>>I think we should look at consolidating as much info as possible in
> >>
> >>spot.
> >>
> >>>Right now people have to search all over the place (wiki, website,
> >>
> >>READMEs,
> >>
> >>>etc) to piece together any useful info. Even worse some of our docs
> are
> >>>severely outdated and cause more harm than good :(
> >>>
> >>>I like the format of the Spring and Hibernate documentation pages.
> >>
> >>Their
> >>
> >>>outline view is *MUCH* easier to navigate then the side menu
> Maven/Xdocs
> >>>spits out. I vote we use them as a template for doing our docs.
> >>>
> >>
> >>For yhat it's worth, I've nearly completed a build of the entire
> >>design-docs folder in Jetspeed 2 as a website with Forrest (which
> >>handles mny different formats including OpenOffice).
> >>
> >>It's currently not online but I can try and publish it before this
> >>week-end. This could be a basis for a comprehensive documentation
> >>without having the hassle of rewriting existing docs in xdoc format.
> >>
>
> --
> Raphaël Luta - raphael@apache.org
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Raphaël Luta <ra...@apache.org>.
Of course, give me a few days to put everything in shape though.
Scott T Weaver wrote:
> Great! Would it be possible for me to get copy of the Jetspeed 2 Forrest
> source to "play" with ;)
>
> -scott
>
>
>>-----Original Message-----
>>From: Raphaël Luta [mailto:raphael@apache.org]
>>Sent: Tuesday, March 22, 2005 9:57 AM
>>To: Jetspeed Developers List
>>Subject: Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-
>>Bridge & Fusion - David/Ate/others- Pls comment)
>>
>>Scott T Weaver wrote:
>>
>>>I think we should look at consolidating as much info as possible in
>>
>>spot.
>>
>>>Right now people have to search all over the place (wiki, website,
>>
>>READMEs,
>>
>>>etc) to piece together any useful info. Even worse some of our docs are
>>>severely outdated and cause more harm than good :(
>>>
>>>I like the format of the Spring and Hibernate documentation pages.
>>
>>Their
>>
>>>outline view is *MUCH* easier to navigate then the side menu Maven/Xdocs
>>>spits out. I vote we use them as a template for doing our docs.
>>>
>>
>>For yhat it's worth, I've nearly completed a build of the entire
>>design-docs folder in Jetspeed 2 as a website with Forrest (which
>>handles mny different formats including OpenOffice).
>>
>>It's currently not online but I can try and publish it before this
>>week-end. This could be a basis for a comprehensive documentation
>>without having the hassle of rewriting existing docs in xdoc format.
>>
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Scott T Weaver <sc...@binary-designs.net>.
Great! Would it be possible for me to get copy of the Jetspeed 2 Forrest
source to "play" with ;)
-scott
> -----Original Message-----
> From: Raphaël Luta [mailto:raphael@apache.org]
> Sent: Tuesday, March 22, 2005 9:57 AM
> To: Jetspeed Developers List
> Subject: Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-
> Bridge & Fusion - David/Ate/others- Pls comment)
>
> Scott T Weaver wrote:
> >
> > I think we should look at consolidating as much info as possible in
> spot.
> > Right now people have to search all over the place (wiki, website,
> READMEs,
> > etc) to piece together any useful info. Even worse some of our docs are
> > severely outdated and cause more harm than good :(
> >
> > I like the format of the Spring and Hibernate documentation pages.
> Their
> > outline view is *MUCH* easier to navigate then the side menu Maven/Xdocs
> > spits out. I vote we use them as a template for doing our docs.
> >
>
> For yhat it's worth, I've nearly completed a build of the entire
> design-docs folder in Jetspeed 2 as a website with Forrest (which
> handles mny different formats including OpenOffice).
>
> It's currently not online but I can try and publish it before this
> week-end. This could be a basis for a comprehensive documentation
> without having the hassle of rewriting existing docs in xdoc format.
>
> --
> Raphaël Luta - raphael@apache.org
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Raphaël Luta <ra...@apache.org>.
Scott T Weaver wrote:
>
> I think we should look at consolidating as much info as possible in spot.
> Right now people have to search all over the place (wiki, website, READMEs,
> etc) to piece together any useful info. Even worse some of our docs are
> severely outdated and cause more harm than good :(
>
> I like the format of the Spring and Hibernate documentation pages. Their
> outline view is *MUCH* easier to navigate then the side menu Maven/Xdocs
> spits out. I vote we use them as a template for doing our docs.
>
For yhat it's worth, I've nearly completed a build of the entire
design-docs folder in Jetspeed 2 as a website with Forrest (which
handles mny different formats including OpenOffice).
It's currently not online but I can try and publish it before this
week-end. This could be a basis for a comprehensive documentation
without having the hassle of rewriting existing docs in xdoc format.
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Scott T Weaver <sc...@binary-designs.net>.
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, March 21, 2005 10:55 PM
> To: Jetspeed Developers List
> Subject: Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-
> Bridge & Fusion - David/Ate/others- Pls comment)
>
> Ate Douma wrote:
> >>
...
> > - If all works out well, I'll propose to do a J2-M2 release as well as a
> > Fusion 1.6 release next weekend (!) as I can dedicate most of my time
> > that
> > weekend doing the release.
> > I haven't done a release before though, so getting at least some help
> > from
> > someone from the team with previous experience will be important I
> think.
>
> Next weekend? Do you mean the weekend of April 2-3?
> April 2-3 is perfect for me, as my family is out of town that weekend
> and Im free to work on the release with you.
Ill offer my services as well seeing I have been pretty much MIA in regards
to the project as of late and feel pretty bad about that.
...
> > - Furthermore, I am going to spend more time in April on writing
> > documentation
> > as the community really is in dire need of it. I'd say the M3 release
> > should
> > contain enough documentation to allow new users to start working with
> J2
> > on their own.
> > Hopefully, other team members and/or active community users can step
> > up too
> > in providing more documentation...
> >
> I think we should all help out with the documentation.
> Its too much work for one person and its also best to get input from
> more than one person. If any non-committers want to help out you are
> very welcome to send documentation patches
I think we should look at consolidating as much info as possible in spot.
Right now people have to search all over the place (wiki, website, READMEs,
etc) to piece together any useful info. Even worse some of our docs are
severely outdated and cause more harm than good :(
I like the format of the Spring and Hibernate documentation pages. Their
outline view is *MUCH* easier to navigate then the side menu Maven/Xdocs
spits out. I vote we use them as a template for doing our docs.
-Scott
>
> > I know this list is quite ambitious, but well, I am ;-)
> > Anyone like to comment?
> >
> Ambitious Ate! Right on!
> You're inspiring me too
>
>
> --
> David Sean Taylor
> Bluesunrise Software
> david@bluesunrise.com
> [office] +01 707 773-4646
> [mobile] +01 707 529 9194
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by David Sean Taylor <da...@bluesunrise.com>.
Ate Douma wrote:
>>
> I want to propose the following:
> - I like to call a vote on merging the J2 deployment_refactoring branch
> with
> CVS HEAD before the end of *this week*
I don't see the need to impose a deadline on yourself.
Personally I have enough deadlines as is.
Why don't we just say "call a vote on merging the deployment_refactoring
branch" and then you get it done when it gets done.
My vote is +1
> - if/once the deployment_refactoring branch is merged, I'll step up and
> work
> on getting Fusion running again with the current J2 CVS HEAD. I'll try
> to do so within a few days, (the sooner we decide if/when to merge the
> branch the more time I will have for it)
> Precondition for success though is that there are not other blocking
> issues
> with Fusion to get it working again. I don't know. Community, David?
Ive seen a few bug reports recently that make me wonder if I ever got
everything working properly after the navigational state conversion. My
work with Fusion pretty much ended in September 2004. I can say I was
confident at that point. Right now Im not, and I haven't been testing
against the J2 head. We can always fallback to a 1.6 release with M1.
The only real issue is that your new branch will break Fusion in the CVS
head.
> Getting help from some of you currently working with Fusion might help
> too:
> Hema, Jeff?
> - Hopefully, beginning next week we have both J2 and Fusion in sync again
> - If all works out well, I'll propose to do a J2-M2 release as well as a
> Fusion 1.6 release next weekend (!) as I can dedicate most of my time
> that
> weekend doing the release.
> I haven't done a release before though, so getting at least some help
> from
> someone from the team with previous experience will be important I think.
Next weekend? Do you mean the weekend of April 2-3?
April 2-3 is perfect for me, as my family is out of town that weekend
and Im free to work on the release with you.
> - Furthermore, I'd like to propose to do releases more often (say once
> every
> month, maybe two) at least until we reach J2-final.
+1
> The next release (M3) could contain the portlet selector (customizer)
> from David if he won't be able to commit it in time for M2.
Im shooting for M2, we'll see...
> Furthermore, we should try to get most of the outstanding bugs fixed
> by then.
> I'm willing to work on that a lot.
> - Furthermore, I am going to spend more time in April on writing
> documentation
> as the community really is in dire need of it. I'd say the M3 release
> should
> contain enough documentation to allow new users to start working with J2
> on their own.
> Hopefully, other team members and/or active community users can step
> up too
> in providing more documentation...
>
I think we should all help out with the documentation.
Its too much work for one person and its also best to get input from
more than one person. If any non-committers want to help out you are
very welcome to send documentation patches
> I know this list is quite ambitious, but well, I am ;-)
> Anyone like to comment?
>
Ambitious Ate! Right on!
You're inspiring me too
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
Ate Douma wrote:
> I want to propose the following:
> - I like to call a vote on merging the J2 deployment_refactoring branch
> with
> CVS HEAD before the end of *this week*
As I have positive responses (and non negative) from at least 3 team members
and several from the community too, I'll try to do the merge this evening already
and will start with the Fusion synchronization branch tomorrow evening :-)
Regards, Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Jeff Sheets <je...@gmail.com>.
I definitely fall into the "pathologically bad documenters" category :-)
I also agree that user experiences are good to report and read, and
I'll try to add to the wiki along with my blog. On the flip side,
corporate IT decision makers often don't like to hear that the
documentation is only user experiences, and not actual docs from the
developers.
So I can see where both are very vital to the project....
On Tue, 22 Mar 2005 14:56:31 +0100, Raphaël Luta <ra...@apache.org> wrote:
> Jeff Sheets wrote:
> > Ate,
> >
> > Lastly, documentation is a high concern in my organization, as well as
> > others. Some are scared to use a product that is lightly documented,
> > so adding more/better/accurate docs would be a tremendous benefit for
> > Jetspeed. As the code becomes more stable, I have to agree that this
> > would be a well rewarded effort.
> >
>
> Don't forget most good developers are pathologically bad documenters :)
>
> Also, in my experience, the most useful documentation usually comes from
> new user/developer experiences discovering the product and describing
> their experience and pitfalls encountered.
>
> If you really want a top notch documentation, please try and use the
> wiki to report on your install/config experiences, issues encountered
> and things you want to do with J2 but can't find how to do.
> This kind of feedback helps us put the emphasis where it's needed,
> explaining better the difficult points and not losing too much energy on
> documenting obscure things of limited value or miss some major
> functional areas.
>
> Basically, every user can help make the documentation as helpful as
> possible by giving feedback on their experience.
> Just create a new page in the Jetspeed2 wiki :
>
> http://wiki.apache.org/portals/Jetspeed2
>
> and let us know about it !
>
> --
> Raphaël Luta - raphael@apache.org
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Raphaël Luta <ra...@apache.org>.
Hema Menon wrote:
> I guess my words didn't come out right either. I have seen many
> queries in the user list is regarding the build issuses or related to
> installation be it multiple platform or diff db's. Every user who
> tries to use this product has to go thru this routine. Based on that,
> what I meant to say, is that user experiences is very relevant in that
> case, more for development of a FAQ, similar to what Wiki has right
> now.
>
So it looks we all agree there. I'm looking forward working on the
user feedbacks :)
>>Hema Menon wrote:
>>
>>>I tend to agree to the "good developers/bad documentors" theory.
>>>However its not always easy to work with lack of/no documentation to a
>>>product. Yes, user experience is the best form of documentation. Will
>>>try to use Wiki to give more feedback, that could help others too.
>>>
>>
>>My point was not to imply that user should document the product with
>>their experiences, simply that user feedback is a great tool for
>>developers to build a *useful* documentation without spending too
>>much energy documenting every features in one go...
>>It enables us to identify where explanations are needed and what can
>>be made more intuitive.
>>
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Hema Menon <me...@gmail.com>.
I guess my words didn't come out right either. I have seen many
queries in the user list is regarding the build issuses or related to
installation be it multiple platform or diff db's. Every user who
tries to use this product has to go thru this routine. Based on that,
what I meant to say, is that user experiences is very relevant in that
case, more for development of a FAQ, similar to what Wiki has right
now.
Hema
On Tue, 22 Mar 2005 15:50:47 +0100, Raphaël Luta <ra...@apache.org> wrote:
> Hema Menon wrote:
> > I tend to agree to the "good developers/bad documentors" theory.
> > However its not always easy to work with lack of/no documentation to a
> > product. Yes, user experience is the best form of documentation. Will
> > try to use Wiki to give more feedback, that could help others too.
> >
>
> My point was not to imply that user should document the product with
> their experiences, simply that user feedback is a great tool for
> developers to build a *useful* documentation without spending too
> much energy documenting every features in one go...
> It enables us to identify where explanations are needed and what can
> be made more intuitive.
>
> --
> Raphaël Luta - raphael@apache.org
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hema Menon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Serge Huber <sh...@jahia.com>.
I'd go further and say that in a perfect world, user documentation
shouldn't be needed at all because the software would be so intuitive
that users would be able to understand it immediately.
Nobody really likes writing documentation... and nobody really likes
reading it to get the job done :)
Please note I said in a perfect world and I'm only talking about user
documentation :)
On a more serious (and realistic) note, I agree with Rafaël completely.
cheers,
Serge...
Raphaël Luta wrote:
> Hema Menon wrote:
>
>> I tend to agree to the "good developers/bad documentors" theory.
>> However its not always easy to work with lack of/no documentation to a
>> product. Yes, user experience is the best form of documentation. Will
>> try to use Wiki to give more feedback, that could help others too.
>>
> My point was not to imply that user should document the product with
> their experiences, simply that user feedback is a great tool for
> developers to build a *useful* documentation without spending too
> much energy documenting every features in one go...
> It enables us to identify where explanations are needed and what can
> be made more intuitive.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Raphaël Luta <ra...@apache.org>.
Hema Menon wrote:
> I tend to agree to the "good developers/bad documentors" theory.
> However its not always easy to work with lack of/no documentation to a
> product. Yes, user experience is the best form of documentation. Will
> try to use Wiki to give more feedback, that could help others too.
>
My point was not to imply that user should document the product with
their experiences, simply that user feedback is a great tool for
developers to build a *useful* documentation without spending too
much energy documenting every features in one go...
It enables us to identify where explanations are needed and what can
be made more intuitive.
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Hema Menon <me...@gmail.com>.
I tend to agree to the "good developers/bad documentors" theory.
However its not always easy to work with lack of/no documentation to a
product. Yes, user experience is the best form of documentation. Will
try to use Wiki to give more feedback, that could help others too.
Hema
On Tue, 22 Mar 2005 14:56:31 +0100, Raphaël Luta <ra...@apache.org> wrote:
> Don't forget most good developers are pathologically bad documenters :)
>
> Also, in my experience, the most useful documentation usually comes from
> new user/developer experiences discovering the product and describing
> their experience and pitfalls encountered.
>
> If you really want a top notch documentation, please try and use the
> wiki to report on your install/config experiences, issues encountered
> and things you want to do with J2 but can't find how to do.
> This kind of feedback helps us put the emphasis where it's needed,
> explaining better the difficult points and not losing too much energy on
> documenting obscure things of limited value or miss some major
> functional areas.
>
> Basically, every user can help make the documentation as helpful as
> possible by giving feedback on their experience.
> Just create a new page in the Jetspeed2 wiki :
>
> http://wiki.apache.org/portals/Jetspeed2
>
> and let us know about it !
>
> --
> Raphaël Luta - raphael@apache.org
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hema Menon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Raphaël Luta <ra...@apache.org>.
Jeff Sheets wrote:
> Ate,
>
> Lastly, documentation is a high concern in my organization, as well as
> others. Some are scared to use a product that is lightly documented,
> so adding more/better/accurate docs would be a tremendous benefit for
> Jetspeed. As the code becomes more stable, I have to agree that this
> would be a well rewarded effort.
>
Don't forget most good developers are pathologically bad documenters :)
Also, in my experience, the most useful documentation usually comes from
new user/developer experiences discovering the product and describing
their experience and pitfalls encountered.
If you really want a top notch documentation, please try and use the
wiki to report on your install/config experiences, issues encountered
and things you want to do with J2 but can't find how to do.
This kind of feedback helps us put the emphasis where it's needed,
explaining better the difficult points and not losing too much energy on
documenting obscure things of limited value or miss some major
functional areas.
Basically, every user can help make the documentation as helpful as
possible by giving feedback on their experience.
Just create a new page in the Jetspeed2 wiki :
http://wiki.apache.org/portals/Jetspeed2
and let us know about it !
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Jeff Sheets <je...@gmail.com>.
Ate,
I am excited about the items that you have listed here, especially
about a release date for 1.6 in a short time frame!! I would be happy
to help out with testing or bug fixing, just let me know.
And Hema, I agree with you that a customizer is badly needed for J2.
Coming from J1, we also felt lost without a customizer and cannot use
J2 until it is ready.
Lastly, documentation is a high concern in my organization, as well as
others. Some are scared to use a product that is lightly documented,
so adding more/better/accurate docs would be a tremendous benefit for
Jetspeed. As the code becomes more stable, I have to agree that this
would be a well rewarded effort.
Thanks for the forum for my thoughts,
-- Jeff
On Mon, 21 Mar 2005 19:09:04 -0900, Hema Menon <me...@gmail.com> wrote:
> Ate,
>
> Its almost the end of the day( a long tiring day, I must add) for my
> part of the world, but hey, all of a sudden I feel all awake and
> energetic to start another? :) Well, thanks for the response. My
> comments are inline.
>
> > I want to propose the following:
> > - I like to call a vote on merging the J2 deployment_refactoring branch with CVS HEAD before the end of *this week* - if/once the deployment_refactoring branch is merged, I'll step up and work on getting Fusion running again with the current J2 CVS HEAD. I'll try to do so within a few days, (the sooner we decide if/when to merge the branch the more time I will have for it) Precondition for success though is that there are not other blocking issues with Fusion to get it working again. I don't know. Community, David?
>
> <HM>
> I am not sure what's the show stopper for merging the deployment
> refactoring branch. As far as I understand from the mails going
> around, the changes in the refactoring branch has been breaking some
> Fusion stuff. If you think, the first step in getting to resolve that
> is to get it the branch merged, maybe it should. Well, I am not aware
> of all the implications, David might be able to say which way to go.
> </HM>
>
> > Getting help from some of you currently working with Fusion might help too: Hema, Jeff?
>
> <HM>
> Sure. We could offer whatever help that we can provide. A better
> product is the need for the community as a whole:)
> </HM>
>
> > - Hopefully, beginning next week we have both J2 and Fusion in sync again - If all works out well, I'll propose to do a J2-M2 release as well as a Fusion 1.6 release next weekend (!) as I can dedicate most of my time that weekend doing the release.
>
> <HM>
> Well, that would be awesome! I guess it could be a Fusion with M2 release :)
> </HM>
>
>
> > I haven't done a release before though, so getting at least some help from someone from the team with previous experience will be important I think. Furthermore, I'd like to propose to do releases more often (say once every month, maybe two) at least until we reach J2-final.
>
> <HM>
> I believe incremental releases are a great way to go, but its your
> call, since you are the developers(the hardworking group) </HM>
>
>
> > The next release (M3) could contain the portlet selector (customizer) from David if he won't be able to commit it in time for M2.
>
> <HM>
> Customizer, is as I mentioned before, a great tool and a must. I kind
> of felt lost without the customizer, trying to deploy a portlet in
> JS2. Its great, that David has it almost ready for JS2.
> </HM>
>
> > Furthermore, we should try to get most of the outstanding bugs fixed by then. I'm willing to work on that a lot.
> > - Furthermore, I am going to spend more time in April on writing documentation as the community really is in dire need of it. I'd say the M3 release should contain enough documentation to allow new users to start working with J2
> > on their own. Hopefully, other team members and/or active community users can step up too in providing more documentation...
>
> <HM>
> Well, you said it! Good documentation is a must. I haven't tried out
> much with JS2, since we are still with JS1.6, but is sure willing to
> lend a hand to get it going.
> </HM>
>
>
> > I know this list is quite ambitious, but well, I am ;-)
>
> <HM>
> Great! We need the energy. Its always been here, which is why we have
> a stable product running on JS 1.5 .
> </HM>
>
> > Anyone like to comment?
> Jeff, over to you:)
>
> Thanks!
> Hema
>
>
> >
> > Regards, Ate
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
>
> --
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Hema Menon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Hema Menon <me...@gmail.com>.
Ate,
Sure. That's fine with me.
Hema
On Tue, 22 Mar 2005 10:08:05 +0100, Ate Douma <at...@douma.nu> wrote:
>
>
> Hema Menon wrote:
> > Ate,
> >
> > <HM>
> > I am not sure what's the show stopper for merging the deployment
> > refactoring branch. As far as I understand from the mails going
> > around, the changes in the refactoring branch has been breaking some
> > Fusion stuff. If you think, the first step in getting to resolve that
> > is to get it the branch merged, maybe it should. Well, I am not aware
> > of all the implications, David might be able to say which way to go.
> > </HM>
> Synchronizing the merged deployment refactoring branch with Fusion is what I'll
> take onto myself. But once that's done, I could use help from you and others
> for testing the result and detect possible (other) problems to resolve before
> we should release Fusion.
>
> >
> >> Getting help from some of you currently working with Fusion might help too: Hema, Jeff?
> >
> >
> > <HM>
> > Sure. We could offer whatever help that we can provide. A better
> > product is the need for the community as a whole:)
> > </HM>
> Great. Keep monitoring the list for progress and I might just mail you directly
> if I have a new Fusion ready for testing. Is that alright with you?
>
> > <HM>
> > Well, that would be awesome! I guess it could be a Fusion with M2 release :)
> > </HM>
> Thats what I'm aiming for...
>
> Ate
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hema Menon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
Hema Menon wrote:
> Ate,
>
> <HM>
> I am not sure what's the show stopper for merging the deployment
> refactoring branch. As far as I understand from the mails going
> around, the changes in the refactoring branch has been breaking some
> Fusion stuff. If you think, the first step in getting to resolve that
> is to get it the branch merged, maybe it should. Well, I am not aware
> of all the implications, David might be able to say which way to go.
> </HM>
Synchronizing the merged deployment refactoring branch with Fusion is what I'll
take onto myself. But once that's done, I could use help from you and others
for testing the result and detect possible (other) problems to resolve before
we should release Fusion.
>
>> Getting help from some of you currently working with Fusion might help too: Hema, Jeff?
>
>
> <HM>
> Sure. We could offer whatever help that we can provide. A better
> product is the need for the community as a whole:)
> </HM>
Great. Keep monitoring the list for progress and I might just mail you directly
if I have a new Fusion ready for testing. Is that alright with you?
> <HM>
> Well, that would be awesome! I guess it could be a Fusion with M2 release :)
> </HM>
Thats what I'm aiming for...
Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Hema Menon <me...@gmail.com>.
Ate,
Its almost the end of the day( a long tiring day, I must add) for my
part of the world, but hey, all of a sudden I feel all awake and
energetic to start another? :) Well, thanks for the response. My
comments are inline.
> I want to propose the following:
> - I like to call a vote on merging the J2 deployment_refactoring branch with CVS HEAD before the end of *this week* - if/once the deployment_refactoring branch is merged, I'll step up and work on getting Fusion running again with the current J2 CVS HEAD. I'll try to do so within a few days, (the sooner we decide if/when to merge the branch the more time I will have for it) Precondition for success though is that there are not other blocking issues with Fusion to get it working again. I don't know. Community, David?
<HM>
I am not sure what's the show stopper for merging the deployment
refactoring branch. As far as I understand from the mails going
around, the changes in the refactoring branch has been breaking some
Fusion stuff. If you think, the first step in getting to resolve that
is to get it the branch merged, maybe it should. Well, I am not aware
of all the implications, David might be able to say which way to go.
</HM>
> Getting help from some of you currently working with Fusion might help too: Hema, Jeff?
<HM>
Sure. We could offer whatever help that we can provide. A better
product is the need for the community as a whole:)
</HM>
> - Hopefully, beginning next week we have both J2 and Fusion in sync again - If all works out well, I'll propose to do a J2-M2 release as well as a Fusion 1.6 release next weekend (!) as I can dedicate most of my time that weekend doing the release.
<HM>
Well, that would be awesome! I guess it could be a Fusion with M2 release :)
</HM>
> I haven't done a release before though, so getting at least some help from someone from the team with previous experience will be important I think. Furthermore, I'd like to propose to do releases more often (say once every month, maybe two) at least until we reach J2-final.
<HM>
I believe incremental releases are a great way to go, but its your
call, since you are the developers(the hardworking group) </HM>
> The next release (M3) could contain the portlet selector (customizer) from David if he won't be able to commit it in time for M2.
<HM>
Customizer, is as I mentioned before, a great tool and a must. I kind
of felt lost without the customizer, trying to deploy a portlet in
JS2. Its great, that David has it almost ready for JS2.
</HM>
> Furthermore, we should try to get most of the outstanding bugs fixed by then. I'm willing to work on that a lot.
> - Furthermore, I am going to spend more time in April on writing documentation as the community really is in dire need of it. I'd say the M3 release should contain enough documentation to allow new users to start working with J2
> on their own. Hopefully, other team members and/or active community users can step up too in providing more documentation...
<HM>
Well, you said it! Good documentation is a must. I haven't tried out
much with JS2, since we are still with JS1.6, but is sure willing to
lend a hand to get it going.
</HM>
> I know this list is quite ambitious, but well, I am ;-)
<HM>
Great! We need the energy. Its always been here, which is why we have
a stable product running on JS 1.5 .
</HM>
> Anyone like to comment?
Jeff, over to you:)
Thanks!
Hema
>
> Regards, Ate
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hema Menon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
Ate Douma wrote:
> I want to propose the following:
> - I like to call a vote on merging the J2 deployment_refactoring branch
> with
> CVS HEAD before the end of *this week*
As I have positive responses (and non negative) from at least 3 team members
and several from the community too, I'll try to do the merge this evening already
and will start with the Fusion synchronization branch tomorrow evening :-)
Regards, Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Roger Ruttimann <ro...@apache.org>.
Ate Douma wrote:
<snip>
>>
>>> - Furthermore, I'd like to propose to do releases more often (say
>>> once every
>>> month, maybe two) at least until we reach J2-final.
>>> The next release (M3) could contain the portlet selector (customizer)
>>> from David if he won't be able to commit it in time for M2.
>>> Furthermore, we should try to get most of the outstanding bugs
>>> fixed by then.
>>> I'm willing to work on that a lot.
>>
>>
>>
>> +1 for more releases on J2 until we reach 1.0 but then again,
>> historically development on Jetspeed occurs in waves of big activity
>> when some committers have time to work the project followed by a general
>> slow down when everybody needs to catch up with real work. It has
>> been like this at least since Jetspeed 1.2b1 :)
>> Because of this, releases are rarely created on a regular basis.
>
> I know. Still, I hope to do (much) more the next few weeks/months and I
> would like to target a J2-final before this summer. Its long overdue in
> my opinion and we simple *must* step up our effort if we don't want to
> get too far behind and lose community support...
>
Because each release carries some overhead we have to keep the number of
intermediate releases down.
I propose that we plan for J2-final (June) and decide if a release is
needed between M2 and J2-final.
The M2 release will slow down development since it needs to be
synchronized with J1-Fusion and a lot of refactoring will go in. Once we
get up to speed again we shouldn't be slow down with another release.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
Raphaël Luta wrote:
> Ate Douma wrote:
>
>>> <snip>
>>
>> I want to propose the following:
>> - I like to call a vote on merging the J2 deployment_refactoring
>> branch with
>> CVS HEAD before the end of *this week*
>
>
> No objection here as long as everybody is aware that this will break
> Fusion for a few days.
I guess that'll mean a +1 from you? Or would you prefer a more formal vote
call for the merge?
Fusion is already broken as it is...
As I responded to Hema on the user list, I intend to create a temporary
branch in J1 for synchronizing Fusion with the new J2 head and merge
that back to J1 HEAD once its stable again.
>
> > <snip>
>
>> - Hopefully, beginning next week we have both J2 and Fusion in sync again
>> - If all works out well, I'll propose to do a J2-M2 release as well as a
>> Fusion 1.6 release next weekend (!) as I can dedicate most of my
>> time that
>> weekend doing the release.
>> I haven't done a release before though, so getting at least some
>> help from
>> someone from the team with previous experience will be important I
>> think.
>
>
> Now that seems to me overly ambitious because it means we'll have a
> mostly untested release.
> I don't mind having a Jetspeed M2 going out this way but I think
> Jetspeed 1.6 requires more testing as it is probably the last major
> release of Jetspeed 1, it should be as stable as possible.
>
> How about releasing a Jetspeed M2 and a Jetspeed 1.6 RC1 at this time.
> Advertise the 1.6 RC1 so that users can test out the binary.
> If no major issue is raised on RC1, rerelease it as 1.6 final about
> 1 or 2 weeks after ?
I agree, +1
>
>> - Furthermore, I'd like to propose to do releases more often (say once
>> every
>> month, maybe two) at least until we reach J2-final.
>> The next release (M3) could contain the portlet selector (customizer)
>> from David if he won't be able to commit it in time for M2.
>> Furthermore, we should try to get most of the outstanding bugs fixed
>> by then.
>> I'm willing to work on that a lot.
>
>
> +1 for more releases on J2 until we reach 1.0 but then again,
> historically development on Jetspeed occurs in waves of big activity
> when some committers have time to work the project followed by a general
> slow down when everybody needs to catch up with real work. It has been
> like this at least since Jetspeed 1.2b1 :)
> Because of this, releases are rarely created on a regular basis.
I know. Still, I hope to do (much) more the next few weeks/months and I
would like to target a J2-final before this summer. Its long overdue in
my opinion and we simple *must* step up our effort if we don't want to
get too far behind and lose community support...
>
>> - Furthermore, I am going to spend more time in April on writing
>> documentation
>> as the community really is in dire need of it. I'd say the M3
>> release should
>> contain enough documentation to allow new users to start working
>> with J2
>> on their own.
>> Hopefully, other team members and/or active community users can step
>> up too
>> in providing more documentation...
>>
>
> ++1 on the documentation effort.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Raphaël Luta <ra...@apache.org>.
Ate Douma wrote:
>> <snip>
> I want to propose the following:
> - I like to call a vote on merging the J2 deployment_refactoring branch
> with
> CVS HEAD before the end of *this week*
No objection here as long as everybody is aware that this will break
Fusion for a few days.
> <snip>
> - Hopefully, beginning next week we have both J2 and Fusion in sync again
> - If all works out well, I'll propose to do a J2-M2 release as well as a
> Fusion 1.6 release next weekend (!) as I can dedicate most of my time
> that
> weekend doing the release.
> I haven't done a release before though, so getting at least some help
> from
> someone from the team with previous experience will be important I think.
Now that seems to me overly ambitious because it means we'll have a
mostly untested release.
I don't mind having a Jetspeed M2 going out this way but I think
Jetspeed 1.6 requires more testing as it is probably the last major
release of Jetspeed 1, it should be as stable as possible.
How about releasing a Jetspeed M2 and a Jetspeed 1.6 RC1 at this time.
Advertise the 1.6 RC1 so that users can test out the binary.
If no major issue is raised on RC1, rerelease it as 1.6 final about
1 or 2 weeks after ?
> - Furthermore, I'd like to propose to do releases more often (say once
> every
> month, maybe two) at least until we reach J2-final.
> The next release (M3) could contain the portlet selector (customizer)
> from David if he won't be able to commit it in time for M2.
> Furthermore, we should try to get most of the outstanding bugs fixed
> by then.
> I'm willing to work on that a lot.
+1 for more releases on J2 until we reach 1.0 but then again,
historically development on Jetspeed occurs in waves of big activity
when some committers have time to work the project followed by a general
slow down when everybody needs to catch up with real work. It has been
like this at least since Jetspeed 1.2b1 :)
Because of this, releases are rarely created on a regular basis.
> - Furthermore, I am going to spend more time in April on writing
> documentation
> as the community really is in dire need of it. I'd say the M3 release
> should
> contain enough documentation to allow new users to start working with J2
> on their own.
> Hopefully, other team members and/or active community users can step
> up too
> in providing more documentation...
>
++1 on the documentation effort.
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Scott T Weaver <sc...@binary-designs.net>.
I was speaking more to the actual installer program I put together. I don't
think we need to cover all the versions of Tomcat when it comes to the
installer program. However, I do agree that we should have binary releases,
i.e. zip/tar files, which contain the versions of J2+Tomcat you mention
below.
> -----Original Message-----
> From: Ate Douma [mailto:ate@douma.nu]
> Sent: Tuesday, March 22, 2005 11:11 AM
> To: Jetspeed Developers List
> Subject: Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-
> Bridge & Fusion - David/Ate/others- Pls comment)
>
>
>
> Scott T Weaver wrote:
> >>- I like to call a vote on merging the J2 deployment_refactoring branch
> > +1 on getting it into HEAD ASAP. I'm very excited to see the new code!
> Its been waiting in the deployment_refactoring branch for you all along to
> look at it ;-)
>
> >
> > I am going to take another shot at the binary installer and hopefully
> have a
> > M2+Tomcat 5.5 version available near release time.
> I'd would like to see a M2+Tomcat 5.0.30 or still 5.0.28 available too if
> possible.
>
> Regards, Ate
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge
& Fusion - David/Ate/others- Pls comment)
Posted by Ate Douma <at...@douma.nu>.
Scott T Weaver wrote:
>>- I like to call a vote on merging the J2 deployment_refactoring branch
> +1 on getting it into HEAD ASAP. I'm very excited to see the new code!
Its been waiting in the deployment_refactoring branch for you all along to
look at it ;-)
>
> I am going to take another shot at the binary installer and hopefully have a
> M2+Tomcat 5.5 version available near release time.
I'd would like to see a M2+Tomcat 5.0.30 or still 5.0.28 available too if
possible.
Regards, Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: J2/Fusion synchronisation and release plan (Was: Re: Struts-Bridge & Fusion - David/Ate/others- Pls comment)
Posted by Scott T Weaver <sc...@binary-designs.net>.
> -----Original Message-----
> From: Ate Douma [mailto:ate@douma.nu]
> Sent: Monday, March 21, 2005 4:31 PM
> To: Jetspeed Users List; Jetspeed Developers List
> Subject: J2/Fusion synchronisation and release plan (Was: Re: Struts-
> Bridge & Fusion - David/Ate/others- Pls comment)
...
> I want to propose the following:
> - I like to call a vote on merging the J2 deployment_refactoring branch
> with
> CVS HEAD before the end of *this week*
> - if/once the deployment_refactoring branch is merged, I'll step up and
> work
> on getting Fusion running again with the current J2 CVS HEAD. I'll try
> to do so within a few days, (the sooner we decide if/when to merge the
> branch the more time I will have for it)
> Precondition for success though is that there are not other blocking
> issues
> with Fusion to get it working again. I don't know. Community, David?
> Getting help from some of you currently working with Fusion might help
> too:
> Hema, Jeff?
+1 on getting it into HEAD ASAP. I'm very excited to see the new code!
> - Hopefully, beginning next week we have both J2 and Fusion in sync again
> - If all works out well, I'll propose to do a J2-M2 release as well as a
> Fusion 1.6 release next weekend (!) as I can dedicate most of my time
> that
> weekend doing the release.
> I haven't done a release before though, so getting at least some help
> from
> someone from the team with previous experience will be important I
> think.
+1 on releasing.
> - Furthermore, I'd like to propose to do releases more often (say once
> every
> month, maybe two) at least until we reach J2-final.
> The next release (M3) could contain the portlet selector (customizer)
> from David if he won't be able to commit it in time for M2.
> Furthermore, we should try to get most of the outstanding bugs fixed by
> then.
> I'm willing to work on that a lot.
Huge +1 on this! I feel we should continue with this approach even after
cut the release version.
> - Furthermore, I am going to spend more time in April on writing
> documentation
> as the community really is in dire need of it. I'd say the M3 release
> should
> contain enough documentation to allow new users to start working with
> J2
> on their own.
> Hopefully, other team members and/or active community users can step up
> too
> in providing more documentation...
>
> I know this list is quite ambitious, but well, I am ;-)
> Anyone like to comment?
I am going to take another shot at the binary installer and hopefully have a
M2+Tomcat 5.5 version available near release time.
>
> Regards, Ate
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org