Re: Using roadmap tag for the JIRA

+1 It's a good idea ! Regards JB On 24/05/2018 05:38, Willem Jiang wrote: > Hi Team, > > As JIRA[1] provides the tags for us to lookup issue. My suggestion is we > put the roadmap tag to the issues that we plan to do in the next few > month. In this way we can build up dynamic road map for

Re: Using roadmap tag for the JIRA

+1 It is a so good idea. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-24 11:38 GMT+08:00 Willem Jiang : > Hi Team, > > As JIRA[1] provides the tags for us to lookup issue. My suggestion is we > put the

Re: Third party jar and License check

We have a release guide[1] for the release processing. We can add a check list section for verifying the kit. Please feel free to send a PR for it. [1]https://servicecomb.incubator.apache.org/developers/release-guide/ Willem Jiang Blog: http://willemjiang.blogspot.com (English)

Re: Please Update the JIRA Status for Preparing the Next Release

Hi Yangbo, I found that few guys response to this topic so far, I am not sure wheather they are busy on coding to forget to do this, or they just considered have no need to update. My suggestion is to contact persons which owned the issues through our Gitter tomorrow, thus you can get response

Re: Please Update the JIRA Status for Preparing the Next Release

Yeah, it is nice. Hi mabin , I know someone interested in ServiceComb have contact you to consult how to contribute to the Apache ServiceComb. Perhaps, you can use these issues[1] to help them start the trip. [1] https://issues.apache.org/jira/browse/SCB-500?jql=

Re: Third party jar and License check

I suggest adding a action, black crow scanning. And also , shall we comb out what should be check carefully first according to the first release prepare, then put it to our website. Thus we can just check it step by step accroding to the checklist when we release the next version. Hi Yangbo, To

Re: Using the RC number for the release

Yes this makes sense, we can keep the version numbers same but when we store it in svn we store it in with xx-rc-yy suffix and where as the nexus staging releases are concerned we will keep the staging releases for all the rc candidates till the IPMC approval is done. Regards Asif On

Re: Using the RC number for the release

I think the rc number is just for what we post on the svn dev directory. As the nexus has staging repo, we can drop it any time if we want. So we still use the version without RC in the nexus release, but for the binary release which are push to the svn repo, we need keep the rc number to avoid

Re: Using the RC number for the release

Hi Willem, I think it's a good way for maintaining the release candidates, for service-center this can be easily done but I have some worries for java-chassis and saga. As per the mailing thread referred by you we need to keep release candidates with xx-rc-yy as suffix and once the

ok

Third party jar and License check

Hi team, As we are heading to a new release, let me share a tools from the recently release check in the incubator generic mailing list. I point out some License issue[1] by checking the third party jars, pulsar did a quick fix[2] with a new script. I highly recommend that we can leverage this

Re: Please Update the JIRA Status for Preparing the Next Release

I did some clean up on the Java Chassis 1.0.0-m2 and found out there are bunch of JIRAs are a good start for the user who want to help. I start a page of contribution[1] which has the link of these newbie JIRAs[2]. [1]http://servicecomb.incubator.apache.org/developers/contributing [2]