[GitHub] Hanks10100 closed pull request #198: * [doc] Add release note for 0.19.0
Hanks10100 closed pull request #198: * [doc] Add release note for 0.19.0 URL: https://github.com/apache/incubator-weex-site/pull/198 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/source/releasenote.md b/source/releasenote.md index 5ead27163..77284fa24 100644 --- a/source/releasenote.md +++ b/source/releasenote.md @@ -4,6 +4,94 @@ type: releasenote layout: post --- + +## v0.19.0 + +- [WEEX-219][Android] support copy action for text component [#1037](https://github.com/apache/incubator-weex/pull/1037) +- [WEEX-228][Android] ShouldStopPropagation Use ShortName StopPropagation [#1042](https://github.com/apache/incubator-weex/pull/1042) +- [WEEX-222][Android] Sticky header in waterfall is not sticky [#1041](https://github.com/apache/incubator-weex/pull/1041) +- [WEEX-210][Android] Weex Auto Scan Component And Module Discover [#1032](https://github.com/apache/incubator-weex/pull/1032) +- [WEEX-216][Android] WXAnimation Fix Memory Leak and performance improve [#1026](https://github.com/apache/incubator-weex/pull/1026) +- [WEEX-368][Android] Turn single process switch on for jsEngine [#1178](https://github.com/apache/incubator-weex/pull/1178) +- [WEEX-380][Android] Fix weex show abnormally in single process [#1188](https://github.com/apache/incubator-weex/pull/1188) +- [WEEX-281][Android] Auto Startup Time Quick [#1141](https://github.com/apache/incubator-weex/pull/1141) +- [WEEX-325][Android] Some MeiZhu Mobole throw NoClassDefFoundError: android/support/design/widget/AppBarLayout$OnOffsetChangedListener [#1140](https://github.com/apache/incubator-weex/pull/1140) +- [WEEX-299][Android] Touch event will transmit to next layer, requestDisallowInterceptTouchEvent should be reset for every touch event [#1138](https://github.com/apache/incubator-weex/pull/1138) +- [WEEX-303][Android] fix nullPoint [#1106](https://github.com/apache/incubator-weex/pull/1106) +- [WEEX-218][Android] support leftGap and rightGap for waterfall recycle-list's orientation support update attrs [#1031](https://github.com/apache/incubator-weex/pull/1031) +- [Weex-260][Android] switch supports setting color [#1085](https://github.com/apache/incubator-weex/pull/1085) +- [WEEX-224][Android] WXDomObject Destory Method Should Be Called avoid Memory Leak [#1086](https://github.com/apache/incubator-weex/pull/1086) +- [WEEX-378][Android] wson support for weex-core new architecture and remove rapidjson [#1187](https://github.com/apache/incubator-weex/pull/1187) +- [WEEX-399][Android] remove extra api js [#1203](https://github.com/apache/incubator-weex/pull/1203) +- [WEEX-376][Android] Fix div layeroverflow event [#1191](https://github.com/apache/incubator-weex/pull/1191) +- [WEEX-244][Android] Weex Android Support W3c Force Api [#1060](https://github.com/apache/incubator-weex/pull/1060) +- [WEEX-240][Android] feature update for weexsandbox [#1088](https://github.com/apache/incubator-weex/pull/1088) +- [WEEX-261][Android] Flat GUI NullPointerException fix [#1081](https://github.com/apache/incubator-weex/pull/1081) +- [WEEX-288][Android] bug fix, fix on some case cannot get bundle type [#1110](https://github.com/apache/incubator-weex/pull/1110) +- [WEEX-342][Android] when animation module or transition parser properties, some propers may be not right, so add try catch to handle the exceptions [#1275](https://github.com/apache/incubator-weex/pull/1275) +- [WEEX-465][Android] fix performance point interactionTime record bug [#1278](https://github.com/apache/incubator-weex/pull/1278) +- [WEEX-342][Android] ava.util.ConcurrentModificationException at java util.ArrayList$ArrayListIterator.next(ArrayList.java:573)at com.taobao.weex.ui.component.WXComponent.applyEvents(WXComponent.java:290) [#1273](https://github.com/apache/incubator-weex/pull/1273) +- [WEEX-565][Android] do not set view's id if there is a id in this view [#1436](https://github.com/apache/incubator-weex/pull/1436) +- [WEEX-564][Android] fix check screen empty logic [#1435](https://github.com/apache/incubator-weex/pull/1435) +- [WEEX-562][Android] task may be null ,should be check ,not try/catch [#1425](https://github.com/apache/incubator-weex/pull/1425) +- [WEEX-560][Android] fix null point of apm && report initJSFM fail info [#1422](https://github.com/apache/incubator-weex/pull/1422) +- [WEEX-342][Android] ava.util.ConcurrentModificationException at java.util.ArrayList$ArrayListIterator.next(ArrayList.java:573)at [#1268](https://github.com/apache/incubator-weex/pull/1268) +- [WEEX-457][Android] add back performance point of maxVDomDeep && int… [#1262](https://github.com/apache/incubator-weex/pull/1262) +- [WEEX-454][Android] fix can't find libweexjss when deploy
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[
https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669536#comment-16669536
]
ASF GitHub Bot commented on WEEX-648:
-
wqyfavor commented on a change in pull request #1644: [WEEX-648][iOS]native
batch for dom operations generating from JavaScript
URL: https://github.com/apache/incubator-weex/pull/1644#discussion_r229549612
##
File path: ios/sdk/WeexSDK/Sources/Manager/WXComponentManager.mm
##
@@ -991,13 +992,41 @@ - (void) _printFlexComponentFrame:(WXComponent
*)component
- (void)_syncUITasks
{
-NSArray *blocks = _uiTaskQueue;
-_uiTaskQueue = [NSMutableArray array];
-dispatch_async(dispatch_get_main_queue(), ^{
-for(dispatch_block_t block in blocks) {
-block();
+NSInteger mismatchBeginIndex = _uiTaskQueue.count;
+for (NSInteger i = _uiTaskQueue.count - 1;i >= 0;i --) {
+if (_uiTaskQueue[i] == WXPerformUITaskBatchEndBlock) {
+_syncUITaskCount = 0;
+// clear when find the matches for end and begin tag
+break;
}
-});
+if (_uiTaskQueue[i] == WXPerformUITaskBatchBeginBlock) {
+mismatchBeginIndex = i;
+break;
+}
+}
+
+if (mismatchBeginIndex == _uiTaskQueue.count) {
+// here we get end tag or there are not begin and end directives
+} else {
+_syncUITaskCount ++;
+// we only find begin tag but missing end tag,
+if (_syncUITaskCount > (MAX_DROP_FRAME_FOR_BATCH)) {
+// when the wait times come to MAX_DROP_FRAME_FOR_BATCH, we will
pop all the stashed operations for user experience.
+mismatchBeginIndex = _uiTaskQueue.count;
+_syncUITaskCount = 0;
+}
+}
+
+if (mismatchBeginIndex > 0) {
+NSArray *blocks = nil;
+blocks = [_uiTaskQueue subarrayWithRange:NSMakeRange(0,
mismatchBeginIndex)];
+[_uiTaskQueue removeObjectsInRange:NSMakeRange(0, mismatchBeginIndex)];
+dispatch_async(dispatch_get_main_queue(), ^{
Review comment:
加上if ([blocks count] == 0) return;吧
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> introduce native batch for dom operations generating from javaScript
>
>
> Key: WEEX-648
> URL: https://issues.apache.org/jira/browse/WEEX-648
> Project: Weex
> Issue Type: Improvement
> Components: Android, iOS
>Reporter: xingZhang
>Assignee: xingZhang
>Priority: Major
>
> We will introduce native batch for dom operations generating from javaScript
> wrap a series of dom operations with beginBatch and endBatch directives, when
> every V-sync signal comes, we ensure that the operations between beginBatch
> and endBatch can be performed in current V-sync, this policy can drop frames
> maybe, for our policy dropping frames, we only allow 20 frames at most.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669538#comment-16669538 ] ASF GitHub Bot commented on WEEX-648: - weex-bot edited a comment on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-430659894 Messages :book: No android file has been changed. :book: android build verification finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/;>dangerJS This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669534#comment-16669534 ] ASF GitHub Bot commented on WEEX-648: - weex-bot edited a comment on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-430659894 Warnings :warning: No Changelog changes! Messages :book: danger test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/;>dangerJS This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669535#comment-16669535 ] ASF GitHub Bot commented on WEEX-648: - weex-bot edited a comment on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-430659894 Messages :book: has no jsfm file changed. :book: jsfm test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/;>dangerJS This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669527#comment-16669527 ] ASF GitHub Bot commented on WEEX-648: - weex-bot edited a comment on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-430659894 Messages :book: No android file has been changed. :book: android build verification finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/;>dangerJS This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669524#comment-16669524 ] ASF GitHub Bot commented on WEEX-648: - acton393 commented on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-434541826 @wqyfavor thanks for your suggestions，I have updated my pull request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669523#comment-16669523 ] ASF GitHub Bot commented on WEEX-648: - weex-bot edited a comment on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-430659894 Warnings :warning: No Changelog changes! Messages :book: danger test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/;>dangerJS This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-648) introduce native batch for dom operations generating from javaScript
[ https://issues.apache.org/jira/browse/WEEX-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669522#comment-16669522 ] ASF GitHub Bot commented on WEEX-648: - weex-bot edited a comment on issue #1644: [WEEX-648][iOS]native batch for dom operations generating from JavaScript URL: https://github.com/apache/incubator-weex/pull/1644#issuecomment-430659894 Messages :book: has no jsfm file changed. :book: jsfm test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/;>dangerJS This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > introduce native batch for dom operations generating from javaScript > > > Key: WEEX-648 > URL: https://issues.apache.org/jira/browse/WEEX-648 > Project: Weex > Issue Type: Improvement > Components: Android, iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > We will introduce native batch for dom operations generating from javaScript > wrap a series of dom operations with beginBatch and endBatch directives, when > every V-sync signal comes, we ensure that the operations between beginBatch > and endBatch can be performed in current V-sync, this policy can drop frames > maybe, for our policy dropping frames, we only allow 20 frames at most. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] The Content of Weex Podling Report
"It's not happened if it is not on the mailing list. " We leverage the mail to talk to the developer and community. And we make the consensus decision through the mail. I think we need stay a bit longer in the incubator to let all the committer and PPMC member knows about it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 30, 2018 at 7:25 PM Hanks Zhang wrote: > > Here is the draft of the podling report, please share your opinions if you > found something improper. > > > Weex > > Weex is a framework for building high-performance mobile apps with modern > web development experience. > > Weex has been incubating since 2016-11-30. > > Three most important issues to address in the move towards graduation: > > 1. Propose more open discussions in the mailing list, improve the > activity. > 2. Establish a regular release schedule and a clear roadmap. > 3. Develop more committers and PPMCs, stay focused on the community. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > Apologize for missing the last podling report. > > The main reason for it is the PPMC and committers does not pay enough > attention in the mailing list. We have realized this mistake and decide to > take more efforts on building the community. > > Here are some actions: > 1. Hold meetings regularly among core contributors of Weex and publish > the summary to the mailing list. > 2. Take turns on duty for each release and podling reports. > > How has the community developed since the last report? > > * Released a new version (v0.19.0) of Weex. > https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E > * Hold a meetup in Shanghai at 2018-09-15, discussed technologies about > the new render pipeline and interactive experience of Weex. > * Migrate the source code from (git-wip-us.apache.org) to ( > gitbox.apache.org) and enabled the issue panel on the GitHub. > > How has the project developed since the last report? > > * In average, more than 10 PRs or commits were merged to the main branch > each week. The Github repository now has 162 contributors (8 new since the > last > report) and 1451 forks (130 new). > * Weex has developed a new render pipeline and used it in production, but > it still needs more improvement. > * A more CSS-friendly Weex Renderer is under discussing, it can fix many > cross-platform inconsistency problems. > > How would you assess the podling's maturity? Please feel free to add your > own commentary. > > [ ] Initial setup > [ ] Working towards the first release > [x] Community building > [x] Nearing graduation > [ ] Other: > > Date of the last release: > > 2018-10-08 (v0.19.0) > > When were the last committers or PPMC members elected? > > New PPMC member: jondong (Jonathan Dong) > > Signed-off-by: > > IPMC/Shepherd notes: > > -- > > By the way, I am not the PPMC member yet and not authorized to edit this > page: https://wiki.apache.org/incubator/September2018 > I wish someone could help me to update this content to the report page. > > Best Regards, > Hanks Zhang
[GitHub] cxfeng1 opened a new pull request #198: * [doc] Add release note for 0.19.0
cxfeng1 opened a new pull request #198: * [doc] Add release note for 0.19.0 URL: https://github.com/apache/incubator-weex-site/pull/198 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: [DISCUSS] The Content of Weex Podling Report
Update: the IPMC report page is https://wiki.apache.org/incubator/November2018 >
Re: [DISCUSS] The Content of Weex Podling Report
Here is the draft of the podling report, please share your opinions if you found something improper. Weex Weex is a framework for building high-performance mobile apps with modern web development experience. Weex has been incubating since 2016-11-30. Three most important issues to address in the move towards graduation: 1. Propose more open discussions in the mailing list, improve the activity. 2. Establish a regular release schedule and a clear roadmap. 3. Develop more committers and PPMCs, stay focused on the community. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Apologize for missing the last podling report. The main reason for it is the PPMC and committers does not pay enough attention in the mailing list. We have realized this mistake and decide to take more efforts on building the community. Here are some actions: 1. Hold meetings regularly among core contributors of Weex and publish the summary to the mailing list. 2. Take turns on duty for each release and podling reports. How has the community developed since the last report? * Released a new version (v0.19.0) of Weex. https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E * Hold a meetup in Shanghai at 2018-09-15, discussed technologies about the new render pipeline and interactive experience of Weex. * Migrate the source code from (git-wip-us.apache.org) to ( gitbox.apache.org) and enabled the issue panel on the GitHub. How has the project developed since the last report? * In average, more than 10 PRs or commits were merged to the main branch each week. The Github repository now has 162 contributors (8 new since the last report) and 1451 forks (130 new). * Weex has developed a new render pipeline and used it in production, but it still needs more improvement. * A more CSS-friendly Weex Renderer is under discussing, it can fix many cross-platform inconsistency problems. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards the first release [x] Community building [x] Nearing graduation [ ] Other: Date of the last release: 2018-10-08 (v0.19.0) When were the last committers or PPMC members elected? New PPMC member: jondong (Jonathan Dong) Signed-off-by: IPMC/Shepherd notes: -- By the way, I am not the PPMC member yet and not authorized to edit this page: https://wiki.apache.org/incubator/September2018 I wish someone could help me to update this content to the report page. Best Regards, Hanks Zhang
Re: [DISCUSS] The Content of Weex Podling Report
We need to make sure all the PPMC monitors the dev mailing list. The Report request mail were send the mailing list serval time. It's hard to miss it if we keep an eye on the mailing list. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 30, 2018 at 4:31 PM Adam Feng wrote: > > As we failed to report last month, we were asked to answer these questions > for the board: > - Why this report was missed > - Why requests for the report to the dev and private mailing lists were > ignored > - What you are going to do to educate your committers about why the report is > important (see the reply on dev list) > - What will be done to improve this and make sure it doesn't happen again. > > > Here is my proposal to avoid missing podling report again: > 1. Add more PPMCs as there’re not enough members in PPMC who are taking > notice of the private@ and dev@ mailing list. > 2. Make a reporting schedule for next year, try to involve main committers to > participate in the reporting rather than same PPMC every time. For example, > this quarter is Hanks and next quarter is Jonathan, thus tell all the > committers what a podling report is and why it is important to our community. > > > Thanks. > Adam Feng > 在 2018年10月30日 +0800 AM11:23，Hanks Zhang ，写道： > > Hi, Weex Community > > > > The board meeting of Apache is near, we should finish the IPMC report this > > week. > > > > Here is the report outline, there are many questions we should answer. I > > will prepare the most of them, please feel free to add your comments. > > > > > > > > Weex > > > > Weex is a framework for building high-performance mobile apps with modern > > web development experience. > > > > Weex has been incubating since 2016-11-30. > > > > Three most important issues to address in the move towards graduation: > > > > 1. > > 2. > > 3. > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > > of? > > > > How has the community developed since the last report? > > > > How has the project developed since the last report? > > > > How would you assess the podling's maturity? Please feel free to add your > > own commentary. > > > > [ ] Initial setup > > [ ] Working towards the first release > > [x] Community building > > [ ] Nearing graduation > > [ ] Other: > > > > Date of the last release: > > > > 2018-10-08 (v0.19.0) > > > > When were the last committers or PPMC members elected? > > > > Have your mentors been helpful and responsive or are things falling > > through the cracks? In the latter case, please list any open issues > > that need to be addressed. > > > > Signed-off-by: > > > > IPMC/Shepherd notes: > > > > - > > > > Best Regards, > > Hanks
Re: [DISCUSS] The Content of Weex Podling Report
As we failed to report last month, we were asked to answer these questions for the board: - Why this report was missed - Why requests for the report to the dev and private mailing lists were ignored - What you are going to do to educate your committers about why the report is important (see the reply on dev list) - What will be done to improve this and make sure it doesn't happen again. Here is my proposal to avoid missing podling report again: 1. Add more PPMCs as there’re not enough members in PPMC who are taking notice of the private@ and dev@ mailing list. 2. Make a reporting schedule for next year, try to involve main committers to participate in the reporting rather than same PPMC every time. For example, this quarter is Hanks and next quarter is Jonathan, thus tell all the committers what a podling report is and why it is important to our community. Thanks. Adam Feng 在 2018年10月30日 +0800 AM11:23，Hanks Zhang ，写道： > Hi, Weex Community > > The board meeting of Apache is near, we should finish the IPMC report this > week. > > Here is the report outline, there are many questions we should answer. I > will prepare the most of them, please feel free to add your comments. > > > > Weex > > Weex is a framework for building high-performance mobile apps with modern > web development experience. > > Weex has been incubating since 2016-11-30. > > Three most important issues to address in the move towards graduation: > > 1. > 2. > 3. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > How has the community developed since the last report? > > How has the project developed since the last report? > > How would you assess the podling's maturity? Please feel free to add your > own commentary. > > [ ] Initial setup > [ ] Working towards the first release > [x] Community building > [ ] Nearing graduation > [ ] Other: > > Date of the last release: > > 2018-10-08 (v0.19.0) > > When were the last committers or PPMC members elected? > > Have your mentors been helpful and responsive or are things falling > through the cracks? In the latter case, please list any open issues > that need to be addressed. > > Signed-off-by: > > IPMC/Shepherd notes: > > - > > Best Regards, > Hanks
