perfsonar development work

[Loukik Kudarimoti <>]

Hi Guilherme, all,

Making a new RC every time a change is made in the STABLE is not 
recommended. In fact this will cause confusion with the testing team if 
you create a new RC when they are still testing the previous RC.

Here are some general guidelines (We tried to stress on this in the hand 
over document and also in some emails)

* If you are creating the first RC for your service, make sure you 
create it only if you are convinced that you have put in everything that 
is needed (for the hand over). What I mean to say is that you should 
complete all the necessary documentation and installation scripts for 
your service before making the RC.

* Once you have prepared the RC, you will begin the hand over process by 
notifying the Release management team that your RC is ready. As part of 
this process, testing will be done and bugs/feature requests will start 
emerging.

* The Release Management team will notify you when all the tests are 
complete and the status. If the release management team asks you to fix 
the bugs and make some changes, only then will you need to produce a new 
RC. However, since there are many types of tests being done, bugs 
reports / feature requests will appear gradually and not all together.* 
IMPORTANT: You can start working on fixing the bugs or improving your 
service as soon as you get the bug notifications. But please do not 
produce an RC as soon as a bug report is filed. Fix the one which is 
filed and wait for all the tests to be complete. After you have taken 
care of all the bugs and feature requests, then produce the next RC.

** After producing each RC, please notify the release management team. 
This is equivalent to initiating the hand over process all over again.

Let me know if you have any questions. I have prepared a flow chart 
illustrating this process. Its on the wiki here: 
http://wiki.perfsonar.net/jra1-wiki/images/1/1c/Micro-Release-Mgmt-for-perfSONAR.png

Loukik


Guilherme Fernandes wrote:
> Hi,
>
> What's the guideline for new RC's? Should I make a new RC everytime I 
> change anything in the STABLE branch? or should I wait for a 
> significant change that actually affects the service functionality 
> (instead of a structural/aesthetical change, like remodeling of 
> questions in the installation process)?
>
> Thanks,
>
> Guilherme