perfsonar development work

[Loukik Kudarimoti <>]

Martin Swany wrote:
> Hi All,
>
> > I just spoke to Roman and as I understand it, the changes made here 
> > are changing the schema as well (please correct me if I am wrong). If 
> > we haven't discussed with the JRA4 guys on the changes made here, the 
> > SQL MA being developed will not work with the analysis tools and 
> > hence it will not be usable.
>
> I don't know why you guys are drawing that conclusion (that the
> schema has been changed.)  This seems like a compilation
> error and is probably just a bug.
>
> Let me repeat -- THIS IS NOT A CHANGE TO THE SCHEMA.
Thanks for the clarification, Martin.
> > I think we require a procedure defined and followed for such major 
> > changes. One such procedure would be to
> > * make use of a branch, put your code there first
> > * send out a proposal to all parties involved.
> > * If an agreement is reached, merge it with the trunk.
>
> In general, I think that the procedure used by most
> projects is to make a branch for the upcoming release
> and have general forward development happen on
> the trunk.  Invasive changes that should probably
> happen on a trunk.  This however, seems like a bug
> fix/enhancement (regarding the new topology stuff
> that Jason has been working on to help Ulisses) that
> has introduced a short-term bug.
>
> Again, if the release is so imminent that that a compilation
> error is a major threat to the release, then it probably should
> have been in a branch.  Or if the release management team
> decided that this would be handled by a "code freeze" and
> someone committed during one, then shame on them  
I was only worried about schema changes as they will affect other 
projects (JRA4).

Loukik.
> -- but
> it is easily fixed.
>
> regards,
> martin