I thought a simple git fetch would detect deleted branches?
Probably wise to send a mail to separate mail to dev@
-------------
Subject: [NOTICE] All branches will be gone on Monday
We plan to remove up all historic branches in the new solr.git repostiory, and leave
only the "main" branch. We'll do this by replacing the branch with a git tag, e.g.
branch_8x will be replaced with tag history/branches/lucene-solr/branch_8x.
This is the same procedure we did when moving from svn to git. No history is lost!
We encourage all committers to work on features in feature branches in your
private git fork instead of pushing your branches to the central repository.
For larger collaborative efforts like reference_branch and refactorings, it's ok
to use central branches.
Should you have a work-in-progress on a central feature branch, such as an
active PR against lucene-solr.git, please push the PR branch to your private
fork and re-create the PR in new repo using the private branch. All PRs will
need to be re-created anyway so this is a small extra step.
If you are aware of branches that should stay central, other than
reference_impl_dev and reference_impl, please reply to this email.
The removal of these branches will happen on Monday March 15th.
After the removal you will need to run "git remote prune origin"
PS: The lucene-solr.git repo, where 8.x development continues, will not be affected.
-------------
> 11. mar. 2021 kl. 07:47 skrev Dawid Weiss <dawid.weiss@gmail.com>:
>
> This will also require people who already made their clones/ forks to
> prune their copy of the remote as this isn't done automatically.
>
> git remote prune origin
>
> Other than that -- looks good to me.
>
> D.
>
> On Wed, Mar 10, 2021 at 11:19 PM Jan Høydahl <jan.asf@cominvent.com> wrote:
>>
>> Yep, I updated it with a check that the command succeeded.
>>
>> Jan
>>
>> 10. mar. 2021 kl. 23:09 skrev Ilan Ginzburg <ilansolr@gmail.com>:
>>
>> Any risk in the script that command:
>> git push ${REMOTE} cominvent/$BRANCH:refs/tags/history/branches/lucene-solr/$BRANCH
>> errors out in some exotic way (?) but the script continues anyway and proceeds with the delete:
>> git push ${REMOTE} --delete $BRANCH
>>
>>
>> On Wed, Mar 10, 2021 at 10:35 PM Jan Høydahl <jan.asf@cominvent.com> wrote:
>>>
>>> Ok, I took a stab at this
>>>
>>> We have 113 branches. Here is a script I prepared that will work directly on a git remote, first creating the tag then deleting the branch.
>>> https://gist.github.com/80a7eea6bacd4e32646a7958d1e9a870
>>>
>>> In the script I have added the list of branches that I propose to "archive".
>>>
>>> Below that there is a commented section of branches that are reported as "active" by GitHub that should probably stay for now
>>> Finally, we have some branches we might want to keep around for refernce?
>>> I'm not sure how useful it is to keep a branch in solr.git for, say branch_8_8, as it will fall behind as branch_8_8 in lucene-solr.git gets updated. So probably archive those as well?
>>>
>>> The pure lucene branches like LUCENE-9004 won't need a tag at all I suppose, but it won't hurt either.
>>>
>>> Jan
>>>
>>>> 10. mar. 2021 kl. 21:16 skrev Dawid Weiss <dawid.weiss@gmail.com>:
>>>>
>>>>> We already did this before, see list of existing tags (git tag -l)
>>>>
>>>> I know, I did it, after all... :) This was a move from subversion
>>>> though... slightly different. Anyway - if you guys want to proceed
>>>> with this, please go ahead, I don't mind. A spring cleaning is needed
>>>> every couple of years... If we just leave the main branch it'll be
>>>> very elegant. People work on their local repos these days anyway, it's
>>>> not like everyone pollutes the same workspace.
>>>>
>>>> D.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org