Closed
Bug 805998
Opened 13 years ago
Closed 8 years ago
Finish renaming Android sync code to allow for landing multiple services features
Categories
(Android Background Services Graveyard :: Build & Test, defect, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rnewman, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #798043 +++
Real Soon Now we will be developing Android Sync and "the Android snippets client delivery service" in the android-sync git repo. The repo includes a lot of Android Sync specific things that we might choose to address as part of a large renaming/rebranding.
We might want to:
* generalize the distribution process away from just Sync. (See also Bug 773050.)
* generalize the manifest structure.
* generalize the resource structure.
* support *not* deploying certain parts of android-services.
* refactor shared code in a slightly saner way. (For example, move HTTP client things to a separate directory. Or our configuration/branch handling tools.)
Reporter | ||
Comment 1•13 years ago
|
||
This is the kind of bug we'll fix as we're accomplishing other things.
Priority: -- → P3
Reporter | ||
Updated•13 years ago
|
Component: Android Sync → Android Sync: Build & Test
Reporter | ||
Comment 2•12 years ago
|
||
Note that we cannot rename the repo and preserve links:
-----
support@github.com
To: rnewman
Re: Renaming a repo *with* redirects from the old name?
---
Hi Richard,
I am afraid this is not possible currently.
Cheers,
Petros
-----
Assignee | ||
Updated•12 years ago
|
Component: Android Sync: Build & Test → Build & Test
Product: Mozilla Services → Android Background Services
Unactionable refactor bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•