OK, just to double-confirm. We will move the `soc` and `attic` branches to
tags[*] with the next releases (Nov 4th that will be).
[*] Loosely: A branch is just tag that updates right? You can check them
out, or create new branches from them just as easily. And these are
"branches" that never
+1 for keeping some way to reach these.
I was going to suggest two steps: Moving the soc*/* branches "under"
attic (that is, renaming them with the attic prefix), and using
something like "zzzattic" for the attic prefix so all attic branches
get pushed to the end of the list and don't get in the
Tom’s Tag idea seems to hit the balance.
I’d like to clean them out. I use git branch all day and they’re just noise
there.
Tags would keep the references we’d need to check them out, without the
additional work of creating a separate repo, or learning new/arcane git
features, which don’t merit
Same proposal from
2016: https://groups.google.com/d/topic/django-developers/sf2adeIAkQA/discussion
On Thursday, October 10, 2019 at 4:09:24 PM UTC-4, Tom Forbes wrote:
>
> I second this, there are a few other branches in that list (successful or
> not) that have historic value to Django. Is
I second this, there are a few other branches in that list (successful or not)
that have historic value to Django. Is there a pressing need to delete them,
other than spring cleaning?
I guess maybe it’s sentimental value, and nobody would ever check them out, but
still...
Tom
> On 10 Oct
Can we leave magic-removal as a tag since it’s such a pivotal point in
djangos history? xD
On Thu, 10 Oct 2019 at 19:09, Mariusz Felisiak
wrote:
> Hi y'all,
>
> We're going to remove some old branches from the Django Git repository
> on 1st November 2019:
>
>- *9* old branches related
Hi y'all,
We're going to remove some old branches from the Django Git repository
on 1st November 2019:
- *9* old branches related with Google SOC projects:
- soc2009/admin-ui
- soc2009/http-wsgi-improvements
- soc2009/i18n-improvements
- soc2009/model-validation
