Re: [DISCUSSION] plan to release TubeMQ 0.3.0 version
Let's cut and stabilize the branch-0.3 for now. And do the 0.3.0 release when it is ready. Thanks Saisai 俊平堵 于2020年3月9日周一 下午5:16写道： > Thanks Goson for proposing this. It sounds like a reasonable plan. +1. > > PS: In most Apache projects, there is no need to vote for release plan. > Just make sure no -1 (from PMC as binding vote) for your proposal (branch, > version, timeline, etc.), and go ahead to do the release work (but we vote > for your release bits). > > Thanks, > > Junping > > Goson zhang 于2020年3月9日周一 下午5:12写道： > > > I plan to release version 0.3.0. Let ’s see if it ’s OK and then start > > voting. > > > > The current version is stable, and the 0.3.0 version is planned to be > > released at the end of March. I will first establish a 0.3.0 branch, > which > > will no longer accept new requirements, and the bugs will be merged into > > the master and the branch, until the 0.3.0 version is released. > > >
Re: Bootstrapping process
IIUC, the current block issue is SGA thing. And I think from code/doc level, we also have several other things: 1. Change to use Apache License V2 and enable RAT check 2. Refactor README to remove any proprietary word 3. Fix the version number and add versioning track in JIRA. 4. Bootstrap apache tubemq website ASAP. 5. Add document about how to contribute to formalize the way of contributing . 6. Add document about how to commit. Some of them may not be blocking issues, but I think it is necessary to fix. Thanks Saisai Justin Mclean 于2020年1月15日周三 上午9:08写道： > Hi, > > A couple of weeks back I posted an email asking about progress of this > podling. > > I can see a lot of work has been done but there still some more to do: > > - Submitting the software grant? > This doesn’t seem to have been submitted yet, is that correct? > > - Moving the repos over to ASF infrastructure. > Work was done on this before the SGA was submitted. This is not ideal. > > - Moving the website over to ASF infrastructure > I’ve got conflicting information on what happening here. There is > development off list and a POC being shown onlist. I’ve received no answer > about the incubator requirements for this website or where this work is > being done. > > - Having all PPMC members sign ICLAs > I believe this has been completed. > > - Adding all PPMC members to the roster > I believe this has been completed. > > - Having all PPMC members signed up to the private list > A couple of PPMC members are still not signed up. > > Anyone add anything to the above? > > Thanks, > Justin
[DISCUSS] About the version number of TubeMQ
I see there're three open issues about about TubeMQ version number: 1. The version number is x.y-SNASHOT, typically it would be x.y.z-SNAPHOST 2. For incubating project, it should have "incubating" suffix, x.y.z-incubating-SNAPSHOT. 3. There's no version number tracking for each JIRA. So I think we should properly choose an initial version and fix the above issues. Can anyone volunteer to fix them. Thanks Saisai
Re: Change TubeMQ's License to use Apache License V2 and enable RAT check
Hi Goson, why don't you create a JIRA to track this issue? 俊平堵 于2020年1月8日周三 下午5:17写道： > +1. I think we *must* use standard Apache license given this is an apache > project. > Would like to hear other mentors' opinion here as well. > > Thanks, > > Junping > > Goson zhang 于2020年1月8日周三 下午5:14写道： > > > Hi community > > > > I've noticed that the License in code files need modify, for example : > > > > /* > > > > > > * * Tencent is pleased to support the open source community by making > > TubeMQ available. * * Copyright (C) 2012-2019 Tencent. All Rights > > Reserved.* > > * > > * Licensed under the Apache License, Version 2.0 (the "License"); you > may > > not use > > * this file except in compliance with the License. You may obtain a copy > > of the > > * License at > > * > > > > Should we use the standard Apache License for declaration? > > >
Re: PR title format
I agreed, I think there should a wiki about "how to contribute". Also about the commit log, I think we should use the script to formalize the commit log and use this to merge, not directly using GH button, one consideration is to formalize the commit log, another is to avoid additional merge commit. Here is what Spark community does ( https://github.com/apache/spark/blob/master/dev/merge_spark_pr.py) . Thanks Saisai Yiheng Wang 于2020年1月8日周三 上午11:38写道： > Hi community > > I've noticed that PR titles are little causal. For example: > >- optimization for delete unnecessary code >- TUBEMQ-7: Using StringBuilder instead of StringBuffer in BaseResult > > Should we consider follow common Apache project pattern, like: > [TUBEMQ-XXX] PR description > or > [TUBEMQ-XXX][Component] PR description > > Thanks > Yiheng >
Re: Podling Tubemq Report Reminder - January 2020
I've updated some parts of the report, please help to review, thanks! Besides, we will follow the Apache way to bring out all the discussions on the mail list, thanks for your guidance. Thanks Saisai Saisai Shao 于2020年1月3日周五 上午11:27写道： > Thanks Justin for your reply, I will amend the report soon. > > Best regards, > Saisai > > Justin Mclean 于2020年1月3日周五 上午7:03写道： > >> Hi, >> >> Thanks for submitting the report but it will not be accepted in it's >> currently form as it doesn't accurately reflect the current podlings state >> and what it needs to do. Next time I suggest you work on the report in the >> open before the due date. >> >> You have user the three most important unfinished issues to address >> before graduating: >> 1. Grow the community to involve more contributors and increase the >> diversity. >> 2. Polish the code and document to satisfy the Apache way. >> 3. Publish the Apache release. >> >> There are far more serious matters that need to be sorted out before >> those are addressed. Number one being moving conversation to this mailing >> list. >> >> Under "Are there any issues that the IPMC or ASF Board need to be aware >> of?" you have said "No" this is incorrect. >> >> Under "How has the community developed since the last report?" you >> mention PRs and commits but the repos have not moved to the ASF yet so how >> is this possible? >> >> User "How has the project developed since the last report?" you mention >> working on the first release and website. I see no conversation of this on >> list or any work towards those gaols. http://tubemq.apache.org currently >> gives 404 not found. >> >> Please rewrite the report to accurately reflect where the podling >> currently is and what issues it faces. >> >> Thanks, >> Justin >> >> >> >> >> >>
Re: Podling Tubemq Report Reminder - January 2020
Thanks Justin for your reply, I will amend the report soon. Best regards, Saisai Justin Mclean 于2020年1月3日周五 上午7:03写道： > Hi, > > Thanks for submitting the report but it will not be accepted in it's > currently form as it doesn't accurately reflect the current podlings state > and what it needs to do. Next time I suggest you work on the report in the > open before the due date. > > You have user the three most important unfinished issues to address before > graduating: > 1. Grow the community to involve more contributors and increase the > diversity. > 2. Polish the code and document to satisfy the Apache way. > 3. Publish the Apache release. > > There are far more serious matters that need to be sorted out before those > are addressed. Number one being moving conversation to this mailing list. > > Under "Are there any issues that the IPMC or ASF Board need to be aware > of?" you have said "No" this is incorrect. > > Under "How has the community developed since the last report?" you mention > PRs and commits but the repos have not moved to the ASF yet so how is this > possible? > > User "How has the project developed since the last report?" you mention > working on the first release and website. I see no conversation of this on > list or any work towards those gaols. http://tubemq.apache.org currently > gives 404 not found. > > Please rewrite the report to accurately reflect where the podling > currently is and what issues it faces. > > Thanks, > Justin > > > > > >
Re: Podling Tubemq Report Reminder - January 2020
Hi Justin, Sorry about the late reply, we will work on this today. Thanks a lot for your reminder. Best regards, Saisai Justin Mclean 于2020年1月2日周四 上午10:05写道： > Hi, > > This is the second report in a row the project has missed, one missed > report is OK, two are cause for concern, three and you may be kicked out of > the Incubator. I can see that you are still moving resources to the > incubator and start up here has been slow. You need to provide the IPMC > with oversight to how the project is going and what issues it is facing and > still need to submit reports in the start up phase. > > It seems to me that some of your mentors are missing, if this is the case > please mention this in your report. I've reached out to them (on the > private list) and if they don't reply they will be removed and other > mentors found to replace them. > > I suggest you discuss on this list what is need to move the project over, > I'm not seeing a lot of communication on these lists, and it seems that > some communication is currently occurring elsewhere. Please fix this. > > Thanks, > Justin >
