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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Hema Menon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
