dubbo-spring-boot-project 什么时候release啊？
@mercyblitz @xionghuiCoder @chickenlj @beiwei30
How to judge the two projects? What’s the difference between them ?
@lovepoem good question
@chickenlj Is there a planned release date for dubbo 2.5.10? We need the commit alibaba/dubbo@ce955d5 to fix the graceful shutdown issue
@nobodyiam As we all know, dubbo just entered apache incubator. We may have to obey the release rules recommended by apache. Let me start a discussion in the mailing list first, see if there's any rules, also get some suggestions from mentors.
BTW, i tend to get the 2.5.10 version released as soon as possible. Please subscribe to dev@dubbo.apache.org, i believe we will have a result soon.
oh hi. I forgot this gitter was here. nice :)
@lovepoem I so far was using the second one, seems more recently updated and also it has a release you can download. The other I was told is the official, but it has no release still snapshot
I will try the first one, but having frequently maintained and released code is ideal, especially when trying to make demos for other people to try
Hi adrian, you still now sleep yet.
I live in malaysia :)
in georgetown penang, which is a chinatown too!
so yes.. if asleep now, it would be because too big lunch
Oh great, i thought you were from some western countries. The first time working with pure english for me, a little hard, but will try my best.
I have received your mails about adapting dubbo with spring-cloud-sleuth this morning, will check it later, some other work to do.
no problem no rush just we are finishing sleuth 2.0 soon and want to make sure dubbo is good
looking at it, I think it is very close (by soon not this week)
I am from US and I can't read chinese (yet) so that's why english. Thanks for your patience with me
ok I think I have instructions ready for users who want to use zipkin with dubbo. Spring boot is separate from this https://github.com/openzipkin/brave/pull/637/files
@adriancole welcome to dubbo gitter, Adrian
谢谢
Tracing system(zipkin's a good implementation) is an important part for distributed systems. I have heard many users from dubbo community looking for opensource solutions intgrating with dubbo. That's really an excellent job
I am new to dubbo but it is pretty easy to read code. Just needed some help a little to save time, not because it is hard.
@abciop this is the official one https://github.com/dubbo/dubbo-spring-boot-project/
also was easier because many people already wrote some tracing code for dubbo. always helps
I think @mercyblitz can do something to combine these two starter projects.
sorry for confusing. I think we should look for the owner of the other repository to see if we can transfer it somewhere else.
and adrian, i just noticed that you used the non official one: https://github.com/alibaba/dubbo-spring-boot-starter
I found @xionghuiCoder is a developer of the non official one, can you resolve this issue with @mercyblitz ?
https://github.com/alibaba/dubbo-spring-boot-starter that will be deprecated did not contain production-ready features
yeah I used that one because it is more maintained :P
so I think if the official one becomes released it will be easier to encourage people to use it
Ok
I will still try with snapshot anyway in case I have a suggestion for change
for example, I had a couple issues I raised with the other project which might be the same in the official one
Yeah, agree with you
建议在项目上加上官方标注，备注大家不要混淆 @mercyblitz
Yeah, agree with you, adrian
personally I like to have very polished first experience. that's why I ask you for advice so much
alibaba/dubbo#1427
imagine if we have the starter, and no-one has to build it, they just download normally and everything is beautiful
this will win new people faster
so when the code is all together for zipkin I will announce how to run the demo, but not before
because I don't want people to struggle with snapshot or anything.. sometimes people who struggle never try twice
so let's do it best we can first time
can't agree any more
@mercyblitz I think we should do something to change the current confusion.
Ok
We make a plan to release non-snapshot version
:thumbsup:
I commit an issue a few minutes for this.
I will spend time today changing to it.. starting now :D
alibaba/dubbo#1427
PS the other thing to keep in mind is if apache means same java packages. Usually it does
if you use same java packages in apache release, everyone's life is easier
later on a big release, change the package name if you want. this is my advice
thanks , guys
Can you add a README-zh. Md
@mercyblitz
@mercyblitz
in other words, group id doesn't have to be same as package name (apache is ok with this)
This is a big question for me these days, you mean we need to change the package name to meet apache requirements?
anyway they used to be ok with this :)
no just the artifact name I believe
in jclouds we didn't change package name
so for example, first thing is just getting a release done. this is primary focus and it is mostly about the process of release source code and packages (jar maven etc)
if you also do package name it is more burden, and breaks everyone in ecosystem
so that's why I would suggest to do separate
first do a release then maybe v3 change package name
@abciop You can post me an issue on document
as long as your champion for ASF agrees
you can of course do two releases same time :) 2.x with same code as 3.x just package change, there are many approaches with pros and cons. just my gut feel is that you can do a release faster by not changing package name
valuable experience
if ever zipkin ASF, I will recommend the same as basically it is pragmatic
Thanks for the invite
re package name it does't need to change if there a good reason i.e. legacy support for not changing it
if it does need to change it probably doesn't have to happen in the first release but may need to before graduation
sound advice
Questions like this should be asked on the dev@ list. It's fine to have a channel like this for conversation but any important decisions need to be made on the dev@ list. At the very least any decision here need to be brought back to the dev@ list.
if it didn't happen on the list, it didn't happen :)
exactly
+1
@justinmclean hi, Justin,do issues in github need to be brought back to the dev@ list ?
@kimmking Questions like this should be brought back to dev@ list :smile:
Once Apache git with a mirror to github is set up any issue raised there will be forwarded to the right mailing list so you don't need to do anything there
@justinmclean thx.
but any issues raised on alibaba/dubbo wont be - so the community may need to come up with a way to migrate existing issues or a way with dealing with that if it take too long to transfer the code base
but yes a good question to ask on the dev@ list :-)
ask on the dev@list,hah :-)
I think your guys can ask for GitHub transform service from Infra team, which I did for SkyWalking.
It will transform the whole GitHub repo, nothing lose, including issue, stars, forks, etc.
Of course, you have decided to use GitHub issue, rather than JIRA.
we have set up JIRA but that decision can be reversed
JIRA is good, by using that, I think the repo issue tab should be closed, in case the people got confused.
Only my suggestion, ha.
I agree @justinmclean We could reverse the decision, choosing the issues of the GIthub to track our problem. As for this, we could start up discussion on dev email list .
A problem I faced in using JIRA is that the access is quite slow from China. Given that most of the users come from China, and they are already get used to using github issue, I would prefer using Github issues rather than JIRA. This is just my personal view, I think we can call a vote on this.
@ralf0131 yes, RocketMQ have migrated from the jira to issues, as for that reason.
who wants to start the dev email?
I will ask for issues as it is easier on integration from github. I can easily link and see if something is followed up
For example, last 3 days I made many issues :)
and because this is a RPC layer you can expect many 3rd party integration type issues
Ok, let me start a thread to discuss this
Agree, any GitHub based open source people love issues.
thx I will reply same
Anyone here who don't subscribe the dev@apache.org please follow this issue alibaba/dubbo#1393 @/all
I will keep myself out of mail list for saving my mail box, sorry :) Already to mail for SkyWalking. But, I ask for GitHub issue, because SkyWalking has already integrated with Dubbo, we want to start discussion there. Thanks, everyone.
@lovepoem It's dev@dubbo.apache.org
I think dev@dubbo.incubator.apache.org is right.
@wu-sheng Try using gmail, I use filters to keep my inbox clean. :smile:
both emails addresses will work
@wu-sheng Thanks to the Infra team, you can use them interchangeably.
PS dev often is backend stuff.. I think you will have many users
possible you will want a user mailing list
Already used filter, but still to many :)
@adriancole ASF doesn’t suggest to use user mailing list in incubator stage, I already asked.
ah ok thx didn't know
it is a bit odd because dubbo is already mature
just incubator in apache
Agree.
the incubation process doesn't reflect the maturity of the project but how well it understands how Apache works
and that's about the Apache Way, community building, making releases and (P)PMC oversight
@wu-sheng Any introduction of infrateam? From which place can we learn something about it?
and voting people in as committers and (P)PMC members
@justinmclean that makes sense, but there is a concern right, that we are saturating a dev list :P
very hard to stop people from talking on dev channel
(if users begin using it for routine concerns I mean)
If the email traffic on the dev@ channel becomes too large we can split off a user@ list
re infra if you need anything done ask on the dev@ list and the project mentors can help
ok, just for example that github issue message went to all watchers.. hard to roll back such advice
@chickenlj You can follow what I did.
don't mind me anyway I'm just talking it is fine now.. no one is really using it anyway yet
The transfer need several day in my experience.
but you need to discuss on dev list first!!!!!!
ex big project like dubbo has 2.7K watchers :) anything we recommend on a github issue alerts that many
decisions must be made by the community
I don't think you or anyone else will be able to stop communication on chat. it is something to embrace. we just need to be good at exporting
chatting here is fine / making decisions that effect the entire community is not
there's many reasons for this but one good one if what if you project gains committer in other time zones you can only involve them in the community if your communication is asynchronous i.e. on a mailing list
so I hope that's what we are doing anyway, so we'll continue. I think if someone mentioned correctly we aren't allowed to have a user list anyway
so it is noop
you can have a user list it just not recommend when starting out
ok then I will recommend it on the dev list :P
because literally there are 2.7K watchers on github and I think that's seriously an issue for long term if we route them all to dev for a transient concern
I would wait and see if it becomes a problem before requesting
taking your advice and taking it to the list :) I'm happier heard and dismissed than otherwise. I think it is a concern
fair enough
you don't have to agree to everything I say :-) in fact discussion around different views and consensus building is what makes a lot of Apache Apache
I like it more and more as I get older/more experienced. thanks
re mailing list that are archived and that a legal requirement, I suggest people read the start of http://apache.org/foundation/mailinglists.html
@adriancole It takes time that users get use to ask question on the mailing list. Please feel free to raise it again on the dev list
ok I posted the message. cool beans
haha people are going to think I am a core dev of dubbo soon
maybe I should write some code?
I have another email to write about the spring plugin..
:) If you have time, you can.
heh if I understand correctly, double is lucky in chinese
so maybe having 2 spring boot plugins is ok? :D
:P
@adriancole Contribution is always welcome! Patches, documentation, mails, etc.
and you can be voted in as a committer for things other than just code
heh @wu-sheng knows I am barely breathing like the rest of us, but who knows
I have a problem with feign to sort out before joining any new communities... in fact I have tempted folks to do apache
I have another email to write about the spring plugin..
Great! Actually, eh. at the very first, we pick the name dubbo from a city name in Australia.
fun fact @chickenlj !
JFYI I from Australia. I'm off for the day and will only be here on and off - best to ask any questions of me on the dev@ list
are you from dubbo by chance?
adriancole @adriancole rolls the dice
@adriancole no but I've been there
hey that's a win!
I have a problem with feign to sort out before joining any new communities... in fact I have tempted folks to do apache
Excuese me, do you mean "netflix feign"? I don't fully understand
haha
yeah I didn't effectively transition the project while I was regularly working on it. let this be a lesson to you all! OpenFeign/feign#646
in hind sight, as soon as there was a nice stable time I would have suggested feign to apache, as it would have been easier to bootstrap vs now where I don't have as much "emotional energy" to handle the realities of re-bootstrapping something I've not worked on in a while
luckily the community are putting forth effort, so all is not lost maybe stronger due to it. we'll see!
adriancole @adriancole works on other things for a bit.. will catch up on the plugin stuff maybe tomorrow
请教个问题，dubbo支持provider端异步调用吗？看文档可以通过Callback参数实现，但是对接口入侵很大，还有其他方式做吗？
@birong 本来就是异步调用....
@birong I dont understand your question very clear.