Bugzilla – Full Text Bug Listing
| Summary: | Transfer aCute GitHub repo to eclipse area | ||
|---|---|---|---|
| Product: | Community | Reporter: | Mickael Istria <mistria> |
| Component: | GitHub | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | lbullen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://git.eclipse.org/r/104025 | ||
| Whiteboard: | |||
|
Description
Mickael Istria
I have some questions: 1) Has the history already been squashed? 2) Does master contain the initial contribution that was approved or is there a tag? 3) When works best for you? When we have the answers we can get started. Once we've aggreed on a time the first step will be to transfer the repo to the 'eclipsewebmaster' user on Github. The basic process is here: https://wiki.eclipse.org/Github -M. (In reply to Eclipse Webmaster from comment #1) > 1) Has the history already been squashed? No. Should I do it, or will you? > 2) Does master contain the initial contribution that was approved or is > there a tag? Tab CQ-14020 contains the content that should was approved by IP team. master still contains some more recent commit that we'd like to port to the new repo later. We need to keep them and cherry-pick them after migration. > 3) When works best for you? The sooner the better ;) > When we have the answers we can get started. Once we've aggreed on a time > the first step will be to transfer the repo to the 'eclipsewebmaster' user > on Github. Ok, just tell me when you consider the repo to be ready for it. > The basic process is here: https://wiki.eclipse.org/Github One issue with this document is that it's not clear what's expected to be done by committers and what's to be done by webmasters. So I don't know what I should do right now ;) (In reply to Mickael Istria from comment #2) > (In reply to Eclipse Webmaster from comment #1) > > 1) Has the history already been squashed? > > No. Should I do it, or will you? It's flexible. If you want to do it so that the move is 'faster'(you won't have to wait for Webmaster to do it) that's fine. If you'd rather we did it that's fine as well. > > > 2) Does master contain the initial contribution that was approved or is > > there a tag? > > Tab CQ-14020 contains the content that should was approved by IP team. I presume this was supposed to be 'tag'? > > > 3) When works best for you? > > The sooner the better ;) How about Friday the 1st of September at 2pm Eastern? > One issue with this document is that it's not clear what's expected to be > done by committers and what's to be done by webmasters. So I don't know what > I should do right now ;) That document is what I follow if I'm squashing the history. As noted above if you want to follow it 'pre-emptively' that's fine too. If the commits you would like to cherry pick have followed the Eclipse development process then if you wanted to you could squash, cherry pick and then we could just change the ownership of the repo and you'd be off and running. -M. I've recreated the master branch from the initial code approved by CQ (as a single comment) and by cherry-picking the ones that were merged after the approval of the CQ and which conform to the Eclipse.org rules. I've transferred ownership to `eclipsewebmaster`. And of course, I've got a local backup of the repository on my filesystem and other places ;) So you can proceed with the migration whenever you want, from now on. Only the master branch is useful, you can get rid of all other ones. Done. You should receive an invite to join the aCute GitHub team shortly. -M. |