Author: jdk370
Description:
no way to get extensions from snapshot (since now in git)
Version: unspecified
Severity: normal
Description
Description
Details
Details
- Reference
- bz35574
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | Nikerabbit | T39569 [Translate] Internal error: MediaWiki namespace cannot be edited with Extension:Translate installed | |||
| Declined | • demon | T40188 [Regression] ExtensionDistributor: SVN-only extensions no longer downloadable | |||
| Declined | None | T38802 ExtensionDistributor: Implement support for having both Git extensions and SVN extensions (both with appropiate branch list and trunk/master) | |||
| Resolved | • demon | T24596 Migrate subversion to git | |||
| Resolved | None | T37574 Add support for Git in ExtensionDistributor |
Event Timeline
Comment Actions
Only 121 extensions out of 680 are in git. If we switch ExtensionDistributor over to Git then we'd lose the bulk of the extensions.
Comment Actions
(In reply to comment #1)
Only 121 extensions out of 680 are in git. If we switch ExtensionDistributor
over to Git then we'd lose the bulk of the extensions.
We could make a "githead" branch, and allow downloading from either. Not the tidiest (and also potentially confusing to some users), but it would work.
Needs the changes I made backporting, but that part is relatively trivial
Comment Actions
Also note that, contrary to how we managed extensions on the Subversion server, on the Git server every extension has its own repository. Which means they are no longer automatically branched with core.
In a way this is a good thing because it means there won't be any ghost branches that the extensions maintainer never choose for. On the other hand it means that:
- There is no longer a generic known set of branch names that both core and extensions will all have
- Extension maintainers have to branch themselves.
So ExtensionDistributor would have to fetch a list of branches and tags from the repo itself after the extension repo is selected on the first page (rather then knowing ahead of time which branches there will be).
Also, I'm not sure we have to choose between git or svn, as far as I'm concerned we can just support both. If need be the code may have to be slightly adjusted but I don't think it's anything major.
It would periodically pull all repo's from Git that start with "mediawiki/extensions/" (just like it currently already svn up's periodically all of [mediawiki]/trunk/extensions and a select number of branches).
And then in the interface it could either mix the names alphabetically, or if there is ambiguity it could add " (git)" / " (svn)" to the <option> name. And for svn it still uses the selected branches and for Git it fetches available tags/branches.
Comment Actions
Git support exists. Might need some work for extension branches in the future, but considering we don't have a format for doing this yet, support can't be added
Comment Actions
(In reply to comment #6)
Git support exists. Might need some work for extension branches in the future,
but considering we don't have a format for doing this yet, support can't be
added
bug 38012.