Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=617592 --- Comment #10 from Chen Lei <supercyper1@xxxxxxxxx> 2010-08-05 10:45:09 EDT --- (In reply to comment #9) > Regarding the Harmattan/Meego x Upstream qmf, i already had some patches to > upstream and exchanged a few mails with Nokia guys about this. > The position is not change current meego version and in near future pass to > upstream, so we should go with upstream version. > Minor patches, like enable convenient headers, etc. Currently, I packaged the meego-messagingframework[1], it seems nokia messagingframework[2] hasn't integrated with libaccounts yet, is it right? What's the meaning of "we should go with upstream version"? [1]http://meego.gitorious.org/meego-middleware/messagingframework [2]http://qt.gitorious.org/qt-labs/messagingframework > Regarding the F14, would not be wise having everyone using current Meego and > get F14 launched with old version, so people start to bug everyone about > backport from day 1 of F14 release. > So, i'm fine if you really want to keep old version, i just think that will be > a little upsetting for users interested in use F14. I don't oppose you to update particular meego packages to the lastest git tag if you are really familiar with the code of those packages(e.g. libaccounts), it'll greater if users can experience more new features in F14. But for the major packages in F14, we should track meego 1.1 src.rpm tightly, meego 1.1 isn't an old release, the release date of meego 1.1[1] is almost the same as F14's[2]. Old versions don't mean they have more bugs than newer release, especially for enhancement update. Meego has its own bug report system, if we use the same version as meego 1.1, actually we can forward most bugs to upstream instead of treating it by ourselves, I wonder it's impossible to fix bugs for dozens(>50) of packages without upstream support. Also, it's very easier to track the daily change of meego 1.1's rpms, we can update those changed rpms weekly, many of those rpms already backport some patches from git repos and fix known bugs. [1]http://wiki.meego.com/Release_Engineering/Plans/1.1 [2]http://fedoraproject.org/wiki/Releases/14/Schedule -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review