[TYPO3-core] [RFC] Upcoming Git changes
michael.stucki at typo3.org
Mon May 27 14:29:52 CEST 2013
there was no reaction from you after Ernesto's reply. Do you disagree about
the plans? Do have anything to add?
Here is the current state of the migration script which Thomas created:
And this is the result of it:
What we plan to do is this:
1. Announce a merge freeze
2. Run the script again on the current repository (this will take 1.5-2
3. Push the changes
Additionally, we will rename the repository to
2013/5/18 Helmut Hummel <helmut.hummel at typo3.org>
> On 15.05.13 10:57, Michael Stucki wrote:
> We see a lot of problems coming if Git history will be rewritten.
> Can you elaborate on the problems?
> I would still prefer the history rewrite.
> My suggestion would be to:
> 1. Create a new repo and Gerrit project following the new naming scheme
> 2. Fill the new repo with the rewritten history
> 3. Make the old repo read only
> optional: Have a script to transfer all open changes in Gerrit to the new
> * Clean history
> # No hassels when fetching older versions where submodules are used
> # Working git blam without manual interaction
> * No breaking changes for clones of the "old" repo
> * Merge freeze for the time until the new repo is ready (1 Day?)
> * Bit of more work for tranfering open change requests
> * forge core project could have broken associated merges in the tickets
> Are there more downsides? Or dou you consider the last one as blocker
> (which I would understand)?
> Kind regards,
> Helmut Hummel
> Release Manager TYPO3 6.0
> TYPO3 Core Developer, TYPO3 Security Team Member
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> Before posting to this list, please have a look to the posting rules
> on the following websites:
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.**org <TYPO3-team-core at lists.typo3.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the TYPO3-team-core