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 think we should all help out with the documentation.
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...
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 [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
