You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by yukon <yu...@apache.org> on 2017/03/10 05:14:25 UTC
The new branching model has been put into effect.
Hi all,
Our new branching model has been put into effect, more details please refer
to [1].
So, please kindly send pull requests to develop branch instead of master
branch. Thanks.
[1]. http://rocketmq.incubator.apache.org/docs/branching-model
Regards,
yukon
Re: The new branching model has been put into effect.
Posted by Bruce Snyder <br...@gmail.com>.
I just caught this myself as well and called it out in my suggestions for
improving the website. At a minimum, attribution to the original author
must be provided. As Justin mentions, it's probably also a better idea to
link to the Gitflow page that contains the images rather than lift them and
place them on the RocketMQ site.
Bruce
On Thu, Mar 16, 2017 at 10:43 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> Also it looks like the images used on that page [1] are from here [2].
>
> Do you know how they are licensed and do you have permission to use them?
>
> Thanks,
> Justin
>
> 1. http://rocketmq.incubator.apache.org/docs/branching-model
> 2. http://nvie.com/posts/a-successful-git-branching-model/
>
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bsnyder.org/ <http://bruceblog.org/>
Twitter: http://twitter.com/brucesnyder
Re: The new branching model has been put into effect.
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Yes, we have already added [2] to the end of [1] as a reference, but we
> didn't try to touch the author for the permission from now.
Adding a reference may not be enough depending on how the original content is licensed.
AFAICS the image are copyright the original author and is not under a permissive license so we don't have permission to use them.
You can ask for permission but until that is given I think it would be best to remove the images.
> Call a vote ? It seems too formal. Or keep this thread open util we reach
> an agreement.
It's too early to call a vote and hopefully one will not be required. Lets see if people can agree on the best way forward without a vote.
I think this shows why it a good idea to discuss things on the mailing list before before deciding on a course of action.
Thanks,
Justin
Re: The new branching model has been put into effect.
Posted by yukon <yu...@apache.org>.
Hi Justin and Bruce,
Thanks for your reminder, a reference is not enough indeed, and we should
always take copyright of digital assets seriously, sorry for
our carelessness.
I have took down the branching model page from the web site temporarily,
and I am requesting the permission from the author actively.
Regards,
yukon
On Sun, Mar 19, 2017 at 1:30 AM, Bruce Snyder <br...@gmail.com>
wrote:
> This may seem too formal if you are new to the process, but the ASF takes
> very seriously the topic of copyright and ownership of digital assets. This
> is why linking to the page is a much safer path than simply lifting the
> images.
>
> Bruce
>
> On Fri, Mar 17, 2017 at 12:38 AM, yukon <yu...@apache.org> wrote:
>
> > Hi Justin,
> >
> > Yes, we have already added [2] to the end of [1] as a reference, but we
> > didn't try to touch the author for the permission from now.
> >
> > BTW, we will touch the author soon.
> >
> > And I have no idea about how to handle this situation that the community
> > has some disagreements on the branching model.
> >
> > Call a vote ? It seems too formal. Or keep this thread open util we reach
> > an agreement.
> >
> > Regards,
> > yukon
> >
> > On Fri, Mar 17, 2017 at 12:43 PM, Justin Mclean <
> justin@classsoftware.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Also it looks like the images used on that page [1] are from here [2].
> > >
> > > Do you know how they are licensed and do you have permission to use
> them?
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. http://rocketmq.incubator.apache.org/docs/branching-model
> > > 2. http://nvie.com/posts/a-successful-git-branching-model/
> > >
> >
>
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bsnyder.org/ <http://bruceblog.org/>
> Twitter: http://twitter.com/brucesnyder
>
Re: The new branching model has been put into effect.
Posted by Bruce Snyder <br...@gmail.com>.
This may seem too formal if you are new to the process, but the ASF takes
very seriously the topic of copyright and ownership of digital assets. This
is why linking to the page is a much safer path than simply lifting the
images.
Bruce
On Fri, Mar 17, 2017 at 12:38 AM, yukon <yu...@apache.org> wrote:
> Hi Justin,
>
> Yes, we have already added [2] to the end of [1] as a reference, but we
> didn't try to touch the author for the permission from now.
>
> BTW, we will touch the author soon.
>
> And I have no idea about how to handle this situation that the community
> has some disagreements on the branching model.
>
> Call a vote ? It seems too formal. Or keep this thread open util we reach
> an agreement.
>
> Regards,
> yukon
>
> On Fri, Mar 17, 2017 at 12:43 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > Also it looks like the images used on that page [1] are from here [2].
> >
> > Do you know how they are licensed and do you have permission to use them?
> >
> > Thanks,
> > Justin
> >
> > 1. http://rocketmq.incubator.apache.org/docs/branching-model
> > 2. http://nvie.com/posts/a-successful-git-branching-model/
> >
>
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bsnyder.org/ <http://bruceblog.org/>
Twitter: http://twitter.com/brucesnyder
Re: The new branching model has been put into effect.
Posted by Von Gosling <vo...@apache.org>.
> And I have no idea about how to handle this situation that the community
> has some disagreements on the branching model.
>
> Call a vote ? It seems too formal. Or keep this thread open util we reach
> an agreement.
IMO, we’d better give some reasonable explaination about our branch preferable model.
> 在 2017年3月17日，14:38，yukon <yu...@apache.org> 写道：
>
> Hi Justin,
>
> Yes, we have already added [2] to the end of [1] as a reference, but we
> didn't try to touch the author for the permission from now.
>
> BTW, we will touch the author soon.
>
> And I have no idea about how to handle this situation that the community
> has some disagreements on the branching model.
>
> Call a vote ? It seems too formal. Or keep this thread open util we reach
> an agreement.
>
> Regards,
> yukon
>
> On Fri, Mar 17, 2017 at 12:43 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
>> Hi,
>>
>> Also it looks like the images used on that page [1] are from here [2].
>>
>> Do you know how they are licensed and do you have permission to use them?
>>
>> Thanks,
>> Justin
>>
>> 1. http://rocketmq.incubator.apache.org/docs/branching-model
>> 2. http://nvie.com/posts/a-successful-git-branching-model/
>>
Re: The new branching model has been put into effect.
Posted by yukon <yu...@apache.org>.
Hi Justin,
Yes, we have already added [2] to the end of [1] as a reference, but we
didn't try to touch the author for the permission from now.
BTW, we will touch the author soon.
And I have no idea about how to handle this situation that the community
has some disagreements on the branching model.
Call a vote ? It seems too formal. Or keep this thread open util we reach
an agreement.
Regards,
yukon
On Fri, Mar 17, 2017 at 12:43 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> Also it looks like the images used on that page [1] are from here [2].
>
> Do you know how they are licensed and do you have permission to use them?
>
> Thanks,
> Justin
>
> 1. http://rocketmq.incubator.apache.org/docs/branching-model
> 2. http://nvie.com/posts/a-successful-git-branching-model/
>
Re: The new branching model has been put into effect.
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Also it looks like the images used on that page [1] are from here [2].
Do you know how they are licensed and do you have permission to use them?
Thanks,
Justin
1. http://rocketmq.incubator.apache.org/docs/branching-model
2. http://nvie.com/posts/a-successful-git-branching-model/
Re: The new branching model has been put into effect.
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Our new branching model has been put into effect, more details please refer
> to [1].
I find it a little odd that seems to be have been decided upon off list. Sorry if I’m mistaken or missed it being discussed.
While gitflow was popular, these days it’s recognised to have same issues for example [1]
Thanks,
Justin
1. http://endoflineblog.com/gitflow-considered-harmful
Re: The new branching model has been put into effect.
Posted by Xinyu Zhou <zh...@xinyu.im>.
Don't worry. The latest release is right, contains everything in the release note. We just should do a duplex merge after the release, simple, right?
On Wed, Aug 02, 2017 at 8:51am, Roman Shtykh < rshtykh@yahoo.com.invalid [rshtykh@yahoo.com.invalid] > wrote:
Hi Yukon,
Thanks a lot!
There are two issues then.
1. The latest release is wrong and probably doesn't contain everything as advertised. Shall we cancel it and re-release?Do mentors consider it a problem?
2. How can we make sure that the next release is done correctly?
Obviously, 'develop' branch introduces extra efforts for merging and release. It doesn't seem work well.
-- Roman
On Tuesday, August 1, 2017 6:02 PM, yukon <yu...@apache.org> wrote:
Hi Roman,
The last release didn't do a right merge between develop and master branch,
so we saw a big commit gap.
I have made a synchronization between these two branches just now.
Regards
On Tue, Aug 1, 2017 at 4:12 PM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> Hi Yukon,
> Can you confirm the release was done correctly (with all modifications
> incorporated, as advertised)?
> -- Roman
>
>
> On Friday, July 14, 2017 10:37 AM, yukon <yu...@apache.org> wrote:
>
>
> Hi,
>
>
> Thanks guys, actually the release manager will do a sync between `master`
> and `develop`(duplex merge) when release a new version, so this diff only
> will occur in the gap between two releases.
>
> But... Maybe there is something wrong, I will check it~
>
>
> Regards,
> yukon
>
> On Thu, Jul 13, 2017 at 10:00 AM, Zhanhui Li <li...@gmail.com> wrote:
>
> > Agree, develop and master branches should not split. We need to fix this
> > issue.
> >
> > > 在 2017年7月12日，下午9:23，Roman Shtykh <rs...@yahoo.com.INVALID> 写道：
> > >
> > > Folks,
> > > Please have a look at https://github.com/apache/
> incubator-rocketmq/tree/
> > develop
> > > This branch is 82 commits ahead, 74 commits behind master. <-- how can
> > this happen? considering we had a recent release.
> > > Do we have the situation Justin described before -- "In project where
> we
> > had this split it just ends up being more work, people accidentally check
> > into the wrong branch and I’ve see a lot of merge issues"?
> > >
> > > I'll say it again, but it is very inconvenient to use gitflow model on
> > github (when on github you normally commit on master branch).
> > >
> > > -- Roman
> > >
> > > On Friday, March 17, 2017 11:41 AM, Justin Mclean <
> > justin@classsoftware.com> wrote:
> > >
> > >
> > > Hi,
> > >
> > > I also don't see there's a real need to split master and develop. In
> > project where we had this split it just ends up being more work, people
> > accidentally check into the wrong branch and I’ve see a lot of merge
> issues.
> > >
> > > That being said the project is free to select whatever model they want.
> > >
> > > Thanks,
> > > Justin
> > >
> >
> >
>
>
>
Re: The new branching model has been put into effect.
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Hi Yukon,
Thanks a lot!
There are two issues then.
1. The latest release is wrong and probably doesn't contain everything as advertised. Shall we cancel it and re-release?Do mentors consider it a problem?
2. How can we make sure that the next release is done correctly?
Obviously, 'develop' branch introduces extra efforts for merging and release. It doesn't seem work well.
-- Roman
On Tuesday, August 1, 2017 6:02 PM, yukon <yu...@apache.org> wrote:
Hi Roman,
The last release didn't do a right merge between develop and master branch,
so we saw a big commit gap.
I have made a synchronization between these two branches just now.
Regards
On Tue, Aug 1, 2017 at 4:12 PM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> Hi Yukon,
> Can you confirm the release was done correctly (with all modifications
> incorporated, as advertised)?
> -- Roman
>
>
> On Friday, July 14, 2017 10:37 AM, yukon <yu...@apache.org> wrote:
>
>
> Hi,
>
>
> Thanks guys, actually the release manager will do a sync between `master`
> and `develop`(duplex merge) when release a new version, so this diff only
> will occur in the gap between two releases.
>
> But... Maybe there is something wrong, I will check it~
>
>
> Regards,
> yukon
>
> On Thu, Jul 13, 2017 at 10:00 AM, Zhanhui Li <li...@gmail.com> wrote:
>
> > Agree, develop and master branches should not split. We need to fix this
> > issue.
> >
> > > 在 2017年7月12日，下午9:23，Roman Shtykh <rs...@yahoo.com.INVALID> 写道：
> > >
> > > Folks,
> > > Please have a look at https://github.com/apache/
> incubator-rocketmq/tree/
> > develop
> > > This branch is 82 commits ahead, 74 commits behind master. <-- how can
> > this happen? considering we had a recent release.
> > > Do we have the situation Justin described before -- "In project where
> we
> > had this split it just ends up being more work, people accidentally check
> > into the wrong branch and I’ve see a lot of merge issues"?
> > >
> > > I'll say it again, but it is very inconvenient to use gitflow model on
> > github (when on github you normally commit on master branch).
> > >
> > > -- Roman
> > >
> > > On Friday, March 17, 2017 11:41 AM, Justin Mclean <
> > justin@classsoftware.com> wrote:
> > >
> > >
> > > Hi,
> > >
> > > I also don't see there's a real need to split master and develop. In
> > project where we had this split it just ends up being more work, people
> > accidentally check into the wrong branch and I’ve see a lot of merge
> issues.
> > >
> > > That being said the project is free to select whatever model they want.
> > >
> > > Thanks,
> > > Justin
> > >
> >
> >
>
>
>
Re: The new branching model has been put into effect.
Posted by yukon <yu...@apache.org>.
Hi Roman,
The last release didn't do a right merge between develop and master branch,
so we saw a big commit gap.
I have made a synchronization between these two branches just now.
Regards
On Tue, Aug 1, 2017 at 4:12 PM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> Hi Yukon,
> Can you confirm the release was done correctly (with all modifications
> incorporated, as advertised)?
> -- Roman
>
>
> On Friday, July 14, 2017 10:37 AM, yukon <yu...@apache.org> wrote:
>
>
> Hi,
>
>
> Thanks guys, actually the release manager will do a sync between `master`
> and `develop`(duplex merge) when release a new version, so this diff only
> will occur in the gap between two releases.
>
> But... Maybe there is something wrong, I will check it~
>
>
> Regards,
> yukon
>
> On Thu, Jul 13, 2017 at 10:00 AM, Zhanhui Li <li...@gmail.com> wrote:
>
> > Agree, develop and master branches should not split. We need to fix this
> > issue.
> >
> > > 在 2017年7月12日，下午9:23，Roman Shtykh <rs...@yahoo.com.INVALID> 写道：
> > >
> > > Folks,
> > > Please have a look at https://github.com/apache/
> incubator-rocketmq/tree/
> > develop
> > > This branch is 82 commits ahead, 74 commits behind master. <-- how can
> > this happen? considering we had a recent release.
> > > Do we have the situation Justin described before -- "In project where
> we
> > had this split it just ends up being more work, people accidentally check
> > into the wrong branch and I’ve see a lot of merge issues"?
> > >
> > > I'll say it again, but it is very inconvenient to use gitflow model on
> > github (when on github you normally commit on master branch).
> > >
> > > -- Roman
> > >
> > > On Friday, March 17, 2017 11:41 AM, Justin Mclean <
> > justin@classsoftware.com> wrote:
> > >
> > >
> > > Hi,
> > >
> > > I also don't see there's a real need to split master and develop. In
> > project where we had this split it just ends up being more work, people
> > accidentally check into the wrong branch and I’ve see a lot of merge
> issues.
> > >
> > > That being said the project is free to select whatever model they want.
> > >
> > > Thanks,
> > > Justin
> > >
> >
> >
>
>
>
Re: The new branching model has been put into effect.
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Hi Yukon,
Can you confirm the release was done correctly (with all modifications incorporated, as advertised)?
-- Roman
On Friday, July 14, 2017 10:37 AM, yukon <yu...@apache.org> wrote:
Hi,
Thanks guys, actually the release manager will do a sync between `master`
and `develop`(duplex merge) when release a new version, so this diff only
will occur in the gap between two releases.
But... Maybe there is something wrong, I will check it~
Regards,
yukon
On Thu, Jul 13, 2017 at 10:00 AM, Zhanhui Li <li...@gmail.com> wrote:
> Agree, develop and master branches should not split. We need to fix this
> issue.
>
> > 在 2017年7月12日，下午9:23，Roman Shtykh <rs...@yahoo.com.INVALID> 写道：
> >
> > Folks,
> > Please have a look at https://github.com/apache/incubator-rocketmq/tree/
> develop
> > This branch is 82 commits ahead, 74 commits behind master. <-- how can
> this happen? considering we had a recent release.
> > Do we have the situation Justin described before -- "In project where we
> had this split it just ends up being more work, people accidentally check
> into the wrong branch and I’ve see a lot of merge issues"?
> >
> > I'll say it again, but it is very inconvenient to use gitflow model on
> github (when on github you normally commit on master branch).
> >
> > -- Roman
> >
> > On Friday, March 17, 2017 11:41 AM, Justin Mclean <
> justin@classsoftware.com> wrote:
> >
> >
> > Hi,
> >
> > I also don't see there's a real need to split master and develop. In
> project where we had this split it just ends up being more work, people
> accidentally check into the wrong branch and I’ve see a lot of merge issues.
> >
> > That being said the project is free to select whatever model they want.
> >
> > Thanks,
> > Justin
> >
>
>
Re: The new branching model has been put into effect.
Posted by yukon <yu...@apache.org>.
Hi,
Thanks guys, actually the release manager will do a sync between `master`
and `develop`(duplex merge) when release a new version, so this diff only
will occur in the gap between two releases.
But... Maybe there is something wrong, I will check it~
Regards,
yukon
On Thu, Jul 13, 2017 at 10:00 AM, Zhanhui Li <li...@gmail.com> wrote:
> Agree, develop and master branches should not split. We need to fix this
> issue.
>
> > 在 2017年7月12日，下午9:23，Roman Shtykh <rs...@yahoo.com.INVALID> 写道：
> >
> > Folks,
> > Please have a look at https://github.com/apache/incubator-rocketmq/tree/
> develop
> > This branch is 82 commits ahead, 74 commits behind master. <-- how can
> this happen? considering we had a recent release.
> > Do we have the situation Justin described before -- "In project where we
> had this split it just ends up being more work, people accidentally check
> into the wrong branch and I’ve see a lot of merge issues"?
> >
> > I'll say it again, but it is very inconvenient to use gitflow model on
> github (when on github you normally commit on master branch).
> >
> > -- Roman
> >
> > On Friday, March 17, 2017 11:41 AM, Justin Mclean <
> justin@classsoftware.com> wrote:
> >
> >
> > Hi,
> >
> > I also don't see there's a real need to split master and develop. In
> project where we had this split it just ends up being more work, people
> accidentally check into the wrong branch and I’ve see a lot of merge issues.
> >
> > That being said the project is free to select whatever model they want.
> >
> > Thanks,
> > Justin
> >
>
>
Re: The new branching model has been put into effect.
Posted by Zhanhui Li <li...@gmail.com>.
Agree, develop and master branches should not split. We need to fix this issue.
> 在 2017年7月12日，下午9:23，Roman Shtykh <rs...@yahoo.com.INVALID> 写道：
>
> Folks,
> Please have a look at https://github.com/apache/incubator-rocketmq/tree/develop
> This branch is 82 commits ahead, 74 commits behind master. <-- how can this happen? considering we had a recent release.
> Do we have the situation Justin described before -- "In project where we had this split it just ends up being more work, people accidentally check into the wrong branch and I’ve see a lot of merge issues"?
>
> I'll say it again, but it is very inconvenient to use gitflow model on github (when on github you normally commit on master branch).
>
> -- Roman
>
> On Friday, March 17, 2017 11:41 AM, Justin Mclean <ju...@classsoftware.com> wrote:
>
>
> Hi,
>
> I also don't see there's a real need to split master and develop. In project where we had this split it just ends up being more work, people accidentally check into the wrong branch and I’ve see a lot of merge issues.
>
> That being said the project is free to select whatever model they want.
>
> Thanks,
> Justin
>
Re: The new branching model has been put into effect.
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Folks,
Please have a look at https://github.com/apache/incubator-rocketmq/tree/develop
This branch is 82 commits ahead, 74 commits behind master. <-- how can this happen? considering we had a recent release.
Do we have the situation Justin described before -- "In project where we had this split it just ends up being more work, people accidentally check into the wrong branch and I’ve see a lot of merge issues"?
I'll say it again, but it is very inconvenient to use gitflow model on github (when on github you normally commit on master branch).
-- Roman
On Friday, March 17, 2017 11:41 AM, Justin Mclean <ju...@classsoftware.com> wrote:
Hi,
I also don't see there's a real need to split master and develop. In project where we had this split it just ends up being more work, people accidentally check into the wrong branch and I’ve see a lot of merge issues.
That being said the project is free to select whatever model they want.
Thanks,
Justin
Re: The new branching model has been put into effect.
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
I also don't see there's a real need to split master and develop. In project where we had this split it just ends up being more work, people accidentally check into the wrong branch and I’ve see a lot of merge issues.
That being said the project is free to select whatever model they want.
Thanks,
Justin
Re: The new branching model has been put into effect.
Posted by Xinyu Zhou <zh...@xinyu.im>.
Yes, if use CTR mechanism, the rollback or little polishes maybe will happen very often, this new branching model can cover this situation.
BTW, as Xin and Roman mentioned, develop on `master` branch doesn’t have problems, so does develop on `develop` branch.
Regards, yukon
On Fri, Mar 10, 2017 at 3:51 PM, Von Gosling <vo...@apache.org> wrote:
The master branch is a stable baseline.
The develop branch is a CI baseline.
IMO, the develop and master branch model are easy to scalable, especially for CTR mechanism and more and more guys contributions. :-)
> 在 2017年3月10日，15:39，Xin Wang <da...@gmail.com> 写道：
>
> Agree with Roman, I don't think developing on master is a problem. Just
> like many bigdata projects: Storm,Spark,Flink..
>
> - Xin
>
> 2017-03-10 15:34 GMT+08:00 yukon <yu...@apache.org>:
>
>> Hi,
>>
>> We also use tags for releases, but make master branch in a stable state may
>> be better. And this branching model is very classical and used widely.
>>
>> Regards
>>
>> On Fri, Mar 10, 2017 at 3:07 PM, Roman Shtykh <rs...@yahoo.com.invalid>
>> wrote:
>>
>>> Guys, what is the reason for not developing on master branch and using
>>> tags for releases? It works for many other projects.
>>> Roman
>>>
>>>
>>> On Friday, March 10, 2017 3:14 PM, yukon <yu...@apache.org> wrote:
>>>
>>>
>>> Hi all,
>>>
>>> Our new branching model has been put into effect, more details please
>> refer
>>> to [1].
>>>
>>> So, please kindly send pull requests to develop branch instead of master
>>> branch. Thanks.
>>>
>>> [1]. http://rocketmq.incubator.apache.org/docs/branching-model
>>>
>>> Regards,
>>> yukon
>>>
>>>
>>>
>>>
>>
Re: The new branching model has been put into effect.
Posted by Von Gosling <vo...@apache.org>.
The master branch is a stable baseline.
The develop branch is a CI baseline.
IMO, the develop and master branch model are easy to scalable, especially for CTR mechanism and more and more guys contributions. :-)
> 在 2017年3月10日，15:39，Xin Wang <da...@gmail.com> 写道：
>
> Agree with Roman, I don't think developing on master is a problem. Just
> like many bigdata projects: Storm,Spark,Flink..
>
> - Xin
>
> 2017-03-10 15:34 GMT+08:00 yukon <yu...@apache.org>:
>
>> Hi,
>>
>> We also use tags for releases, but make master branch in a stable state may
>> be better. And this branching model is very classical and used widely.
>>
>> Regards
>>
>> On Fri, Mar 10, 2017 at 3:07 PM, Roman Shtykh <rs...@yahoo.com.invalid>
>> wrote:
>>
>>> Guys, what is the reason for not developing on master branch and using
>>> tags for releases? It works for many other projects.
>>> Roman
>>>
>>>
>>> On Friday, March 10, 2017 3:14 PM, yukon <yu...@apache.org> wrote:
>>>
>>>
>>> Hi all,
>>>
>>> Our new branching model has been put into effect, more details please
>> refer
>>> to [1].
>>>
>>> So, please kindly send pull requests to develop branch instead of master
>>> branch. Thanks.
>>>
>>> [1]. http://rocketmq.incubator.apache.org/docs/branching-model
>>>
>>> Regards,
>>> yukon
>>>
>>>
>>>
>>>
>>
Re: The new branching model has been put into effect.
Posted by Xin Wang <da...@gmail.com>.
Agree with Roman, I don't think developing on master is a problem. Just
like many bigdata projects: Storm,Spark,Flink..
- Xin
2017-03-10 15:34 GMT+08:00 yukon <yu...@apache.org>:
> Hi,
>
> We also use tags for releases, but make master branch in a stable state may
> be better. And this branching model is very classical and used widely.
>
> Regards
>
> On Fri, Mar 10, 2017 at 3:07 PM, Roman Shtykh <rs...@yahoo.com.invalid>
> wrote:
>
> > Guys, what is the reason for not developing on master branch and using
> > tags for releases? It works for many other projects.
> > Roman
> >
> >
> > On Friday, March 10, 2017 3:14 PM, yukon <yu...@apache.org> wrote:
> >
> >
> > Hi all,
> >
> > Our new branching model has been put into effect, more details please
> refer
> > to [1].
> >
> > So, please kindly send pull requests to develop branch instead of master
> > branch. Thanks.
> >
> > [1]. http://rocketmq.incubator.apache.org/docs/branching-model
> >
> > Regards,
> > yukon
> >
> >
> >
> >
>
Re: The new branching model has been put into effect.
Posted by yukon <yu...@apache.org>.
Hi,
We also use tags for releases, but make master branch in a stable state may
be better. And this branching model is very classical and used widely.
Regards
On Fri, Mar 10, 2017 at 3:07 PM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> Guys, what is the reason for not developing on master branch and using
> tags for releases? It works for many other projects.
> Roman
>
>
> On Friday, March 10, 2017 3:14 PM, yukon <yu...@apache.org> wrote:
>
>
> Hi all,
>
> Our new branching model has been put into effect, more details please refer
> to [1].
>
> So, please kindly send pull requests to develop branch instead of master
> branch. Thanks.
>
> [1]. http://rocketmq.incubator.apache.org/docs/branching-model
>
> Regards,
> yukon
>
>
>
>
Re: The new branching model has been put into effect.
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Guys, what is the reason for not developing on master branch and using tags for releases? It works for many other projects.
Roman
On Friday, March 10, 2017 3:14 PM, yukon <yu...@apache.org> wrote:
Hi all,
Our new branching model has been put into effect, more details please refer
to [1].
So, please kindly send pull requests to develop branch instead of master
branch. Thanks.
[1]. http://rocketmq.incubator.apache.org/docs/branching-model
Regards,
yukon