On 10 January 2012 17:14, Lewis John Mcgibbney <[email protected]>wrote:
> Yeah +1 Michele to your patch. I think whatever makes life easiest for us > whilst maintaining some level of traceability should be implemented. > Well, the patch has been applied as tracked on issue ANY23-23. Please confirm next steps: 1. Update packages (ANY23-21) 2. Update headers (ANY23-21 or a dedicated issue ?) 3. Bug fixing (opening some issues to report possible bugs that need to be verified) 4. Plan release I created an issue (ANY23-29) to link all the tasks related to the code base migration. The best. Mic > > On Tue, Jan 10, 2012 at 3:39 PM, Mattmann, Chris A (388J) < > [email protected]> wrote: > > > Hey Michele, > > > > On Jan 10, 2012, at 3:46 AM, Michele Mostarda wrote: > > > > > On 10 January 2012 11:19, Michele Mostarda <[email protected] > > >wrote: > > > > > >> > > >> > > >> On 9 January 2012 15:03, Lewis John Mcgibbney < > > [email protected]>wrote: > > >> > > >>> Hi tomasso. Thanks for your comments. I am happy to progress with > the > > >>> website task [1] but I think it would be beneficial to consider a few > > >>> points at this stage. > > >>> > > >> > > >> Thanks Lewis, > > >> > > >> > > >>> 1) We discussed briefly moving the existing site documentation out of > > the > > >>> trunk codebase to its own separate directory within our Any23 SVN > area. > > >>> Does anyone have any thoughts on running this over the ASF CMS? I > have > > >>> been > > >>> trying to get up to speed with it but to be honest I'm a bit unclear > > as to > > >>> where to get started with this... I'm waiting on hearing back from > some > > >>> people I've asked but if anyone is up to speed with this then please > > say > > >>> so. > > >>> > > >>> So just to clarify... > > >>> > > >>> Michele, > > >>> > > >>> Can you confirm that all recent changes made to the Googlecode can be > > >>> ported to the ASF Any23 code residing in our SVN area? > > >>> > > >> > > >> Not yet, we still miss on the ASF repo the revisions from r1548 to > > r1607. > > >> I just opened an issue: [1]. > > >> > > >> Which is the best way to synch the repositories without producing an > > >> incremental svn dump? (Chris asked to avoid the ASF INFRA guys > further). > > >> I can try with 'svn sync' but I'm not sure it works (1). This would > > allow > > >> to preserve also the SVN logs. > > >> The other solution is to produce a patch and apply it on the ASF SVN > > (2). > > >> This will cause the lost of the SVN logs. > > >> The definitive solution would be to import patch by patch all the > > >> revisions (3), but it is really time consuming. > > >> > > >> Attempting with (1) first. > > >> > > > > > > Solution (1) is not applicable with standard SVN tools, may be somebody > > > knows some python-ish script that can be used for this purpose. > > > Meanwhile I attempted with solution (2), I have merged the > modifications > > in > > > a single patch ready to be committed. > > > Waiting for your confirmation. > > > > > > Chris, do you agree? > > > > I'm fine either way. If you want to ask infra@ that's OK too I was just > > saying that > > it might take them too long in case you wanted to get going or this is > > holding us > > up. In that case, a patch is fine IMO. We're not too too far off in > > revisions and > > even if it's a big patch, we still have the history, just not > > incrementally. > > > > +1 for patch, or whatever you (who is doing the work) decides :) > > > > Cheers, > > Chris > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Chris Mattmann, Ph.D. > > Senior Computer Scientist > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > Office: 171-266B, Mailstop: 171-246 > > Email: [email protected] > > WWW: http://sunset.usc.edu/~mattmann/ > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Adjunct Assistant Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > -- > *Lewis* > -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: [email protected] site : http://www.michelemostarda.com
