Raphael Luta wrote:

> This post is about the current status of the Jetspeed adn how I propose
> that we move forward with this project.
>
> First things first: Santiago, thank you for fixing the CVS,
> you're great :) I could download the new HEAD and compile with issues.
>

With issues or without issues? I think it should be clean, after I removed
the references to nonexistent packages.

>
> However, looking at the code I got from the CVS, I discovered a lot of
> issues and I don't think we can release something soon without a lot
> of clean-up, so I came up with a list of things I'd like to clear before
> releasing something.
>

I know, we have to clean and document properly. For instance, code in the
DiskCache exports too many things and has several redundant methods. It
needs heavy refactoring. I would ask everybody for discipline in cleaning
code, and testing before committing or sending patches. I.E.:

Try to build.sh clean; build.sh before committing, as new files are commonly
forgotten to add to CVS
Try to at least run Jetspeed, look at the home, login, logout, ... and see
the Applications and the Feed process before committing.
Try to work in small incremental jumps, leaving non working functionality
embedded in comments as "work in progress" to ensure that the system is
always on and running, and commit frequently to discover clashes early in
the process.

If you cannot bo like in the road repair business (working without stopping
traffic), try to build a detour (a branch) before starting major repairs and
inform people in the list that things will break. Or hack a provisory
algorithm (commented, again) while you repair a major thing.

Don't forget it: the code is our major source of communications, even more
than the list.

Note: I have the habitude of putting //SGP in small patches to other
people's code (it means Santiago Gala Perez). If you see this and have
problems with the code, ask me.

I know that everybody should know this, but, well, maybe somebody does not
:-)

>
> To simplify the discussion of the following points, I'll break up the
> subject in several mail. I'd really appreciate if at least all active
> committers to the project could voice their opinions on the subject.
>
> --
> Rapha�l Luta - [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Archives and Other:  <http://java.apache.org/main/mail.html>
> Problems?:           [EMAIL PROTECTED]



--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to