forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: [jira] Commented: (FOR-742) trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
Date Wed, 04 Apr 2007 23:48:32 GMT
Ross Gardler wrote:
> Ross Gardler (JIRA) wrote:
> >    [ 
> >
> >
> >Ross Gardler commented on FOR-742:
> >----------------------------------
> >
> >I've deployed the plugins by manually copying the relevant versioned 
> >plugins to as the unversioned plugin. 
> I added these by ssh to then doing copying the files 
> in /www/* followed by relevant svn add.
> Am I correct in thinking these changes will make it to the live server 
> on the next automated update?

Yes they would be picked up on the next rsync.

I have a local SVN working copy of forrest/site/ so i do
such things locally. I didn't think to do it via ssh.
That should work.

You should have done an 'svn copy' rather than manual copy
and then 'svn add'. Also i notice that you haven't done 'svn commit'.

However there are other issues ...

The plugins have been deployed haphazardly over the time
since the 0.7 release. I was hoping that someone would
review and deploy each. Then we would follow up with copying
them to the unversioned space.

That way we are sure that everying is synchronised at
the time of 0.8 release.

I wonder if you done things the wrong way around.
When we deploy a plugin, it goes into the forrest/site SVN
at plugins/0.8/ directory. So i would have thought that they
would get copied up to the higher level directory.

Also i see a lot of additions in the 0.7 directory. Why?

Should this action of "copying to the unversioned space"
have happened at a later stage of the release process?
I wonder if they are now busted for users of the current
0.7 release.

I see that you don't have your 'umask' set, so now the files
that you copied have the wrong group permissions and so the
other committers cannot update.


View raw message