perfsonar development work

[Szymon Trocha <>]

Dear developers,

Some time ago we separated pS base from the rest of pS services to 
collect common functionalities. This became a core of Java services thus 
having a big impact on all our development. That's why any changes to 
this part are crucial and we want to be sure that before committed they 
are tested and communicated to the others. Of course it is not our 
intention to limit any useful changes improving any parts of the current 
working code or adding new components to the base. Developing your 
services or using them you probably see places for improvements and they 
are always more then welcome.
But to prevent some breaks of the code, make sure that changes work with 
current service implementations and have some control on the evolution 
of pS base I'd like to ask you to follow some basic rules before changes 
are made so that Roman and Maciej can look after code consistency and 
the group is informed:
- If the change, according to your best knowledge, is small and with 
little impact you may just drop an e-mail to the mailing list to let us 
know about it before committing changes. It will also enable discussing 
it if necessary and checking change's impact.
- If the change is bigger or has big or unknown impact it should of 
course be discussed first and an SVN branch should be created to include 
changes. Test should also be done to test compatibility. This involves 
release management group at this level of change too.
Finally I encourage you to use Bugzilla to announce such changes so that 
all involved persons can easily follow the process. pS base is already a 
product there.

Thank you and regards,
--
Szymon Trocha

Poznan Supercomputing & Ntw. Center ::: NETWORK OPERATION CENTER
Tel. (+48 61) 8582022
http://noc.man.poznan.pl  ::: http://noc.pionier.gov.pl