On 08/31/2016 02:24 AM, wei xiao wrote:Hi all, I have prepared a patch for aarch64 platform mozjs based on its trunk. But i also want to push the patch into Fedora next release. What's the process for doing it? ThanksHi Wei, thanks for reaching out on the CommOps mailing list! Awesome to hear you're working on some secondary architectures. :) I don't think this list will be able to advise too heavily to this. I would recommend reaching out to the ARM community in Fedora for some help and advice on how to move forward. You can find more information about the ARM community, their mailing list, and how to get involved below: * Wiki page: https://fedoraproject.org/wiki/Architectures/ARM * Mailing list: https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org/ * Issue tracker: https://fedorahosted.org/arm Hope all of this info is helpful!!
_______________________________________________ Fedora Community Operations (CommOps) mailing list commops@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org
Wei,
For the bug fix, contact the arm folks as Justin suggested, as
well as the QA and Devel/ Rel-eng folks for getting it both fast
tracked into the CURRENT release as well as getting it into the
BETA compose so its still viable and tested for the 25 release
(presently expected around Christmas 2016 ). To help stay up on
the important dates take read here: [0]
[0] https://fedoraproject.org/wiki/Releases/25/Schedule
Also, I am a member of the QA,security teams, feel free to reach out to me or the teams if you have issues , questions.
--
Corey Sheldon
+1 310.909.7672
0x8B4E89435A88E539 | C006 564F FA67 CDEA E29B F202 8B4E 8943 5A88
E539
0x59276298D2264944 | 6292 9ABD 6374 6AA7 6D4B 730F 5927 6298 D226
4944
https://gist.github.com/linux-modder/ac5dc6fa211315c633c9 ||
https://keybase.io/linuxmodder
'Have no limitation, as limitation, have no way as way....'
--Bruce Lee
'Everything is impossible, until it's Done!' -- Nelson Mandela
'Any man willing to sacrifice freedom for security, deserves
neither' --Benjamin Franklin
Disclaimer: All correspondence shall be deemed privileged and
confidential unless otherwise stated in the contents of respective
correspondence. All emails ARE signed with at least one of the
keys shown above. Any email or correspondence lacking such shall
be regarded as suspect. The key signed or encrypted with IS ALWAYS
attached as a $keyid.asc, $keyid.sig, or included in the attached
csv file. If this correspondence has reached you in error please
disregard it and it is kindly requested that a return email with a
simple subject 'Miss-routed mail, please remove me' shall be
sufficient. GPG mail is openly and freely solicited.