Hi, Just quickly, a new build page can be seen here [1].
I must say that I agree with Chris in the respect that your concerns are understood regarding migration of code and the subsequent effect that this has on 0.7.0 release etc. But it also means that as an incubating community we are unable to begin working on the ASF Any23 codebase until this is completed. Personally, the quicker the codecase can be dumped in SVN the eariler I can begin working on it, addressing some of the Jira issues and the better this will be for the project as an exciting incubating component. One last thing, thanks for logging the issue we discovered through the Jenkins build, if the solution is trivial then as a committer you should be able to sign up to Jenkins and change the workspace name. I will look at the issue in more detail shortly though and hopefully we can be a stable nightly build sorted out before any 0.7.0 release. Thank you Lewis [1] https://builds.apache.org/view/A-F/view/Any23/ On Mon, Nov 14, 2011 at 3:20 PM, Mattmann, Chris A (388J) < [email protected]> wrote: > Hi Michele, > > On Nov 14, 2011, at 2:11 AM, Michele Mostarda wrote: > > > On 13 November 2011 21:22, Mattmann, Chris A (388J) < > > [email protected]> wrote: > > > >> Guys, speaking of which: > >> > >> I think it's time for a code import, no? I see we're still referencing > the > >> Google > >> Code SVN here. > >> > > > > I agree, let's go ahead. > > > > I'm pushing with the 0.7.0 release but the ETA is not completely under my > > control :) > > :-) No worries. > > Now that the project is at Apache, we need to make sure that any release > that occurs follows the Incubator project release guidelines, here: > > http://incubator.apache.org/guides/releasemanagement.html > > Yes, this is a huge document :-) Yes, this is why I'm asking the question > now. > > I know in certain special cases, Apache has allowed a project coming into > Incubation to do any one of the following things: > > 1. preserve the namespace packaging (I think as you suggest below), e.g., > com.foo.mypackage on the initial Apache release, to maintain some level > of back compat and then move to org.apache.mypackage after that. > > 2. release at some other organization (e.g., Google Code) e.g., in the > case of > Subversion releasing at CollabNet. NOTE: this was highly *not* encouraged > but was allowed due to Subversion's close collaboration with the ASF and > foundation-like status. > > 3. Some combination of the above. > > I know in all cases, 1-3 above are *not* preferred compared to simply: > > 1. Moving the code to the ASF SVN and hardware > 2. Distributing all bits there > 3. Moving all discussion from the external entity to all the ASF mailing > lists. > > Since we're early in Incubation, it might make most sense to simply take > care > of 1-3 now. > > > > > > My only concern is that a code repackaging in the Apache repo would make > > really painful > > a merge with the subsequent code developed for the 0.7.0 release in the > > Google code. > > I hear you. Can you elaborate on what would be required other than a > namespace > change, and moving the bits to SVN? One option might be to (in parallel): > > 1. SVN dump Google code right now to Apache > 2. Finish up whatever is going on at Google code > 3. Merge into SVN at Apache > 4. Make 0.7.0 release at Apache > > Would that work? > > > > > A workaround would be to preserve the original source packaging until the > > final 0.7.0 merge, > > (and the dismission of the Google Code repo). > > Yep, I think this is 1-4 above, right? > > > > > Is that possible? > > It's definitely possible if we're talking about 1-4 :-) > > > > > > >> > >> Can we make it a priority over the next week or two to get Any23 code > into > >> https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to grab > >> the latest trunk from Google code and do the import? Alternatively > another > >> approach would be to try and svnadmin dump the full history and then > >> work with INFRA to import it. Any preferences? > >> > > > > Adding you (Chris) as admin of the Any23 Google Code prj [1]. > > Let me know if you need any support. > > Thanks. I'll try and dump the SVN out of there over the next few days > and do an import into the ASF SVN. I'll get in touch with infra@ and > CC this list to keep folks up to date. > > > > > The best. > > You too! > > 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*
