perfsonar development work

[Loukik Kudarimoti <>]

Jeff W. Boote wrote:
> Loukik Kudarimoti wrote:
> > Roman,
> >
> > After noticing the following error message in catalina.out for RRD MA 
> > (see my other email), I tried to investigate. I noticed that the  
> > following might have happened...
> >
> > 1) On 30th of October, Jason made some changes to objects.config 
> > file. (the change log is attached to this email). I don't know the 
> > effect of these changes but I am positive that the error message 
> > appearing in Catalina.out is because of this.
> >
> > 2) I don't know if changes to the objects.config file is going to 
> > affect the schema or the way rrd ma service works...Roman can you 
> > please investigate this?
> >
> > Based on this event, my suggestions are:
> > (these suggestions are in the hand over document that we will 
> > circulate later today):
> >
> > * All developers, whenever you think your code is ready, please 
> > create a STABLE branch and test your code using the STABLE branch. 
> > This branch applies only to your service. Snapshots and Release 
> > branches should be created from this STABLE branch. Please remember, 
> > you will be doing the release management for your own service....
> >
> > * Whenever such changes to the schema are being made, it would be 
> > good to let the development team know in advance preferably via a 
> > conf. call or something and advice on what is going to change. Its 
> > best to avoid such surprise situations....
>
> Hello all.
>
> (This is my first day back after several weeks - I'm about 1000 email 
> messages behind, so I'm starting with later days and will eventually 
> catch up. I'm sorry if I mis-speak but it looks like there has been 
> some issues with release branching that I could perhaps help with. If 
> I'm misunderstanding these messages please let me know and I'll shut 
> up. :) )
>
> Loukik,
>
> This sounds a bit backwards from the process that is defined in the 
> release engineering documents. Trunc is by definition the 'unstable' 
> branch. If you want somewhere stable where things will not change - 
> then create the stable branch and even more importantly this close to 
> a release: Create your release branch! Changes to trunc should not be 
> causing any problems for a new release. That is be definition the 
> place for new features to be put.
>
> The process should be:
> 1) create a stable branch from trunc (current).
> 2) Tell developers it is time for MFC sweeps. (They have X amount of 
> days to get changes in the new 'stable' branch before it becomes the 
> 'release' branch).
> 3) At code freeze time, branch off stable to release and ONLY release 
> management accesses it.
Hi Jeff,

Welcome back..I hope you enjoyed your holidays..

What you listed out is exactly what I meant but it looks like my email 
was quite cryptic :) Luis and myself have tried to explain this concept 
in the hand-over document. Hopefully, it will make things clearer.

Loukik.


> This allows normal development to continue on the trunc (current) 
> branch without causing problems for the release.
>
> I will be busy with our member meeting over the next week but if you 
> have any questions that you want me to try and prioritize please put 
> 'IMPORTANT' in the subject line and I'll try and prioritize it and 
> answer as best I can.
>
> jeff