This will absolutely be one of the priorities in the 1.3 development
We will do some more work on 1.2 before it is final as well as launch a
new look of the Infoglue site before but after that we will start
working on 1.3.
Mattias Bogeblad | PH: +46 31 799 01 16 | MOB: +46 702 80 05 05=20
SPRAWL SOLUTIONS AB
412 50 G=D6TEBORG
FAX: +46 31 799 00 10
Fr=E5n: Harish VS [mailto:harish.vs@...
Skickat: den 11 februari 2004 08:43
Till: Mattias Bogeblad
Kopia: 'infoglue-control'; 'Infoglue Developer List'; 'infoglue-users'
=C4mne: Re: SV: [Infoglue-developer] Report from the InfoGlue
I tried to write a patching procedure some time back . i have attached
it to this email.
Here is Junit FAQ. it answers some of your questions.
and here is website of Jetspeed ( ASF project). This project has both=20
unit testing guide lines and a patching procedure.
here is another jakarta site with patching procedure
here is apache struts guide lines which talks about unit testing
enhancements and bug fixes
I am not a expert on unit testing, but from what i understand they are=20
very much applicable in a environment where the requirements change very
Mainly because the unit tests guarantee that the requirements are met in
a programmatic way , rather than visual inspection. This becomes more
relevant in a environment where there are few (busy) committers and
newbie contributers who supply patches for bug fixes/enhancements. The
committers can see the results of the patch by running the unit tests
and save time.
"Refactoring is the process of changing a software system in such a way
that it does not alter the external behavior of the code yet improves
its internal structure." -- Martin Fowler, Refactoring.=20
Having unit tests make refactoring easy.
Here is a site which summarises the XP methodology
Extremely good O'reily artice about open source and XP
Here is another site which talks about open source and XP
On Mon, 2004-02-02 at 00:43, Mattias Bogeblad wrote:=20
> Hi Harish,
> Thanx for the feedback. The points you state are important. Especially
> getting a patching-procedure which works under way. Now that 1.2 Final
> will ship pretty soon this is an issue to look at before doing further
> development work for 1.3.
> Testcases are important as well. I am not very experienced on how to
> apply unit-testing or similar the best way. We don't want to end up
> writing timeconsuming testcases and we don't want to skip it or write
> meaningless testcases. I guess there is no silver bullet here but some
> best practices must be available?
> How do one for example handle an R&D-situation where the code changes
> dramatically because the requirements are only becoming apparent as
> go along? Testcases early will most likely be worthless pretty soon.
> one write the cases afterwards then or what?
> Mattias Bogeblad
> Mattias Bogeblad | PH: +46 31 799 01 16 | MOB: +46 702 80 05 05=20
> SPRAWL SOLUTIONS AB
> FABRIKSGATAN 7
> 412 50 G=D6TEBORG
> FAX: +46 31 799 00 10
> --Ursprungligt meddelande--
> Fr=E5n: Harish VS [mailto:harish.vs@...
> Skickat: den 30 januari 2004 15:37
> Till: Mattias Bogeblad
> Kopia: infoglue-control; Infoglue Developer List; infoglue-users
> =C4mne: Re: [Infoglue-developer] Report from the InfoGlue steering
> I know i am replying very late to this.
> I am not an expert in Licensing. But from what i read about GPL, it
> doesn't seem
> to be good. Some license like Apache Style license seems to be more
> to the business community. Having said that, my decision to contribute
> does not=20
> very strongly depend on what license you choose.
> I am pro creating a non-profit organization.
> To get more people to contribute, we need to work on
> a.patching procedures for new code contribution
> b.making unit tests or integration tests (cactus) tests mandatory for=20
> any new feature implemented
Harish VS <harish.vs@...>