Until now, nobody could explain me the real technical improvement of GitFlow. We are talking about using git and not GitFlow. Git does not require GitFlow
At Apache we are only using process as much as needed and not as possible! And my personal advice is: Start with a model as simple as possible. Regards Bernd On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann <[email protected]> wrote: > +1 > > Wha's wrong with GitFlow? > > ___ > > Kito D. Mann | @kito99 | Author, JSF in Action > Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting > Virtua, Inc. | virtua.tech > JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info > +1 203-998-0403 <(203)%20998-0403> > > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj > <http://bit.ly/2kr0fWI> > * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com > > > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann < > [email protected]> wrote: > >> Hello >> >> I think the changes will be not so complicated. The deltaspike pom looks >> nice :-) >> If someone talks about git-flow process i'm out. >> >> Regards >> >> Bernd >> >> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe <[email protected]> >> wrote: >> >>> +1 >>> >>> Change the release process is a pain, but I agree there are some >>> benefits moving to git. >>> >>> But when I see here: >>> >>> https://github.com/apache/myfaces >>> >>> It says: >>> >>> mirrored from git://git.apache.org/myfaces.git >>> >>> But I have never checked where that file is or how to change it. >>> >>> Looking in deltaspike, the svn repo only has the site (for the CMS) and >>> the source code lives on git. If that so, we still need the svn, so I agree >>> it is a good idea to move only some subprojects to git. >>> >>> regards, >>> >>> Leonardo Uribe >>> >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>> Virus-free. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >>> <#m_-1665615671155989291_m_312095376341812428_m_228356912083513587_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> 2017-04-17 11:40 GMT-05:00 Grant Smith <[email protected]>: >>> >>>> +1 >>>> >>>> Couldn't agree more. >>>> >>>> Grant Smith - V.P. Information Technology >>>> Marathon Computer Systems, LLC. >>>> >>>> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann < >>>> [email protected]> wrote: >>>> >>>>> From my side a big >>>>> >>>>> +1 >>>>> >>>>> I'm still happy with subversion but for others the collaboration is >>>>> easier and the project visibility a little bit better. >>>>> >>>>> Regards >>>>> >>>>> Bernd >>>>> >>>>> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" < >>>>> [email protected]>: >>>>> >>>>>> +0 >>>>>> I usually just work on MF core and there it doesn't make much >>>>>> difference. >>>>>> >>>>>> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst <[email protected]>: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> have you ever thought of migrating to Git? I see more and more Apache >>>>>>> projects moving. In the past SVN or Git didn't make any difference >>>>>>> to me >>>>>>> but now I'm thinking that as an Open Source project you need to be >>>>>>> present on GitHub to get Pull Requests from the community. It's much >>>>>>> more fun contributing there than attaching patches to JIRA issues. >>>>>>> >>>>>>> We could start with Trinidad and Tobago to avoid conflicts with the >>>>>>> 2.3 >>>>>>> release. >>>>>>> >>>>>>> Cheers >>>>>>> Dennis >>>>>>> >>>>>> >>>>>> >>>> >>> >> >
