perfsonar development work

[Loukik Kudarimoti <>]

There are some thoughts on this topic. We discussed this during the 
tech. event but couldn't make a concrete decision. For the upcoming 
release, whatever we have currently, seems ok (we are using primary and 
backup repositories). For the future, we need to discuss further (I have 
some new proposals which might fix this problem..but thats for the next 
meeting and next release).

Loukik.


Roman Lapacz wrote:
> Nicolas Simar wrote:
> > Hi,
> >
> > what is the outcome of this thread?
> > Any decision made? (not relevant, change done, other change proposed)
>
> There was no interest to tie jar repository with releases. I event 
> don't have clear idea how we could do it (using versions of jar 
> repository? ). Anyway, it's not a big problem (if it is at all) in 
> this moment.
>
> Roman
>
>
>
> > Cheers,
> > Nicolas
> >
> > Roman Lapacz wrote:
> > > Hi,
> > >
> > > we haven't thought about jar-repository in the release process. I 
> > > wouldn't see the problem if we used only public repository with 
> > > libraries maintained by other project groups. But unfortunately we 
> > > created new two directories in our repository (axis and rrdjtool, 
> > > the rest are copied from the public repository) and I think now we 
> > > should tie them somehow with service releases. For example, if I 
> > > want to create branch STABLE for RRD MA should I include also our 
> > > all jar-repository or just those two directories created by us? What 
> > > do you think?
> > >
> > > Roman