community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zinhtut aung <zinhtutaun...@gmail.com>
Subject Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
Date Thu, 23 Jul 2015 17:33:59 GMT
https://docs.google.com/document/d/1-8FzDaDG1u71IOo4Kx_mg-xWHa3Gv4L8zcBdBGMn98U/edit?usp=docslist_api
On 13 Jul 2015 02:50, "Hervé BOUTEMY" <herve.boutemy@free.fr> wrote:

> Le dimanche 12 juillet 2015 15:41:13 sebb a écrit :
> > On 12 July 2015 at 14:56, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:
> > > Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
> > >> On 12 July 2015 at 13:58,  <hboutemy@apache.org> wrote:
> > >> > Author: hboutemy
> > >> > Date: Sun Jul 12 12:58:09 2015
> > >> > New Revision: 1690454
> > >> >
> > >> > URL: http://svn.apache.org/r1690454
> > >> > Log:
> > >> > updated explanation on import scripts vs update scripts
> > >> >
> > >> > Modified:
> > >> >     comdev/projects.apache.org/scripts/README.txt
> > >> >
> > >> > Modified: comdev/projects.apache.org/scripts/README.txt
> > >> > URL:
> > >> >
> http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.
> > >> > tx
> > >> > t?rev=1690454&r1=1690453&r2=1690454&view=diff
> > >> >
> =======================================================================
> > >> > ==
> > >> > ===== --- comdev/projects.apache.org/scripts/README.txt (original)
> > >> > +++ comdev/projects.apache.org/scripts/README.txt Sun Jul 12
> 12:58:09
> > >> > 2015
> > >> >
> > >> > @@ -43,3 +43,8 @@ various sources:
> > >> >    in: data/projects.xml + projects' DOAP files
> > >> >    out: site/json/projects/*.json +
> site/json/foundation/projects.json
> > >> >
> > >> >        + site/doap/{committeeId}/{project}.rdf
> > >> >
> > >> > +
> > >> > +NOTICE: what prevents import scripts to be added to cron?
> > >> > +1. parse committees.py requires committee-info.txt, which is not
> > >> > available on project-vm (require authentication)
> > >>
> > >> Agreed this means the script must be run by a process with suitable
> karma
> > >>
> > >> > +2. both scripts not only update files but sometimes need to add new
> > >> > files
> > >> > (new committees or new projects) or move +   (projects going to
> Attic
> > >> > or
> > >> > retired committees)
> > >>
> > >> Why should it make a difference if files need to be added?
> > >> There is already a cronjob that detects new files and runs 'svn add'
> for
> > >> them
> > >
> > > the real problem is when moving a file is required: if we blindly add
> new
> > > files for files that should be moved, not only do we get too much
> files,
> > > but when removing the old file we loose history (that could have been
> > > useful)
> > In which case, why not run 'svn add' and 'svn mv' as part of the
> > script where necessary?
> we need to detect when a project moves to Attic
> then integrate svn commands to the python script
>
> feasible, but adds complexity...
>
> >
> > This would be safer than the cronjob which assumes that all new files
> > are to be added to SVN.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message