On Fri, Jun 10, 2016 at 7:26 PM, Markus Koschany <a...@debian.org> wrote: > On 10.06.2016 14:15, Chirayu Desai wrote: > [...] >> Hi, >> I have just pushed my changes to apktool and frameworks/base. >> frameworks/base has some other changes from seamlik (android.jar), so >> I'm not sure what we want to do there with regards to releasing the >> new android-framework-res package. >> >> I agree with that. I'm still new to debian packaging, which is why I >> went ahead and forked all repos, so I could push anything I want to >> show you guys without thinking, and then later push it directly to >> Debian. Or create branches on Debian's git repos, as preferred. >> > > Hi, > > I suggest we move seamlik's changes to another branch for the moment and > release your changes as soon as possible on master. The package has to > go through the so called NEW queue again (a review by our FTP team) > because we create a new binary package. This will take usually a few > days. Since seamlik will be busy until next week, we can use this time > with fixing the current bugs in apktool. I agree. I talked with Kai-Chung, and what we could do is: Push current master as-is to a new branch "android-jar-old" Reset master to last release tag (debian/1%6.0.1+r16-1) Pick the aapt changes, and framework-res.apk package, release it. After that: Pick the r43 update, then also update to r46 (current latest) to master, which could be kept unreleased for now. Kai-Chung could then create a new android-jar branch from the then current master and try to squash stuff from android-jar-old (current master), or as he prefers.
I can do all of the above shortly if it sounds good to you. > > Regards, > > Markus > > > _______________________________________________ > Android-tools-devel mailing list > android-tools-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel
