Alex, let me know if your stuff is all checked in. If so, we can let John finish migrating the other repos.
Based on testing with the website repo, I think we do need to re-clone post-move. jon On Fri, May 17, 2019, 3:09 PM Jon Malkin <[email protected]> wrote: > Silly me. Yeah, that'll be the issue. > > Oh, and on loss of teams, well, it is what it is. We'll be fine. > > On Fri, May 17, 2019 at 2:38 PM Kenneth Knowles <[email protected]> wrote: > > > > Are you logged in to Jira? Note that the Jira account is separate from > your > > ASF account. > > > > Kenn > > > > On Fri, May 17, 2019 at 2:30 PM Jon Malkin <[email protected]> wrote: > > > > > I don't seem to be able to comment on that JIRA, so it's hard to ask > > > John questions directly. > > > > > > I tried checking out memory from the old link and it seems to have > > > been ok, although there haven't been any commits since the move so > > > it's hard to be completely sure which version I pulled. The safe > > > approach seems to be to re-clone things from the new location. This > > > migration will take everything -- release tags, branches, commit > > > history, etc -- right? If so it should be fine to continue. > > > > > > jon > > > > > > On Thu, May 16, 2019 at 6:50 PM leerho <[email protected]> wrote: > > > > > > > > 2) The other capability we lose is the fine control of teams and > which > > > > contributors have access to which repos. I am not too concerned > about > > > > this as whoever we decide can be on our committers list we need to be > > > able > > > > to trust that they know what they are doing. Again, your thoughts on > > > this > > > > issue would be appreciated. > > > > > > > > Lee. > > > > > > > > On Thu, May 16, 2019 at 6:43 PM leerho <[email protected]> wrote: > > > > > > > > > The website has been copied over but the new one is not yet active. > > > > > > > > > > The Memory repo has been moved so far. I asked apache Infra to > pause > > > > > while we understand the consequences. > > > > > > > > > > Before we move the rest we need to feel comfortable with how it is > > > going > > > > > to work and how we can best alert and notify our customers. > > > > > > > > > > There are some consequences to this that we need to understand: > > > > > > > > > > 1) A link such as github.com/datasketches/memory will forward to > > > > > github.com/apache/incubator-datasketches-memory. But the name > > > "memory" > > > > > will disappear from the list of repos on the > github.com/datasketches > > > > > site. This is unfortunate, but I don't think there is a way around > it. > > > > > > > > > > I have put notices on the top of the github.com/datasketches page > as > > > well > > > > > as on the front page of datasketches.github.io. These notices > have > > > > > links to a table allowing folks to find our repos while we are in > > > > > transition. You will find a table at > > > > > > https://github.com/apache/incubator-datasketches/blob/master/README.md > > > . > > > > > > > > > > I'm not sure what else we can do. > > > > > > > > > > After tomorrow (Friday, May 17th) I'll be gone for 3 weeks. If you > > > folks > > > > > feel comfortable with this process you can signal John Andrunas > (via > > > > > https://issues.apache.org/jira/browse/INFRA-18362) to go ahead > with > > > the > > > > > other moves. I feel it would be better to get all the key repos > moved > > > so > > > > > that we can start the work of refactoring. There is no reason to > wait > > > > > until I return, but it is up to Alex and Jon. > > > > > > > > > > Please state your opinions/ positions here on dev@ for the record > :) > > > > > > > > > > Lee. > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > >
