+1 and thanks for the info. Cheers Greg
On 30 December 2015 at 16:11, Nicholas Padilla < nicho...@monstersoftwarellc.com> wrote: > Last thing, > > Here is a write up by the originator of the "Git Flow" idea. > http://nvie.com/posts/a-successful-git-branching-model/ Just to be clear, > you end up having a master and develop branches. The master only contains > the approved production releases. Features are managed in their own > branches, using the create feature "feature", this can mean any change set > gets a new feature branch. When done, you finish feature and it is merged > into develop branch. After you are done with the versions features, they > are all merged with develop, you can do a Release. The Release process > just takes the remote develop and tags it, with your provided version, and > then merges develop with master. That is a really quick summary of the > process. I am sure everyone can see the benefit behind using such a > process. > > > Thanks! > > Nicholas Padilla > www.monstersoftwarellc.com > > “Problems cannot be solved by the same level of thinking that created > them.” > “Learn from yesterday, live for today, hope for tomorrow. The important > thing is not to stop questioning. > < > http://thinkexist.com/quotation/learn_from_yesterday-live_for_today-hope_for/222120.html > > > ” > > Albert Einstein <http://thinkexist.com/quotes/albert_einstein/> > > On Wed, Dec 30, 2015 at 9:04 AM, Nicholas Padilla < > nicho...@monstersoftwarellc.com> wrote: > > > Hello All! > > > > Been a long while since I was active in the Roller community. Since my > > time with Roller, I have used Git heavily. I do believe it is the right > > solution to managing a code base. If you use Source Tree, a Git client > > provided by Atlassian, you will see the Git Flow button that allows you > to > > manage releases, feature branches, and hot fixes. This process was first > > outlined by this, http://datasift.github.io/gitflow/ It was intuitive > > and easy to use, source tree just went a step further. I use this > > functionality daily to manage all my versioned projects, with the GUI > > interface it makes it hard for noobs to make mistakes (Source Tree really > > is one of the best Git clients). > > > > If you choose not to use Git Flow, that is fine, but using Git is the > > right direction. > > > > Theres my two cents. > > Happy New Year! > > > > > > Thanks! > > > > Nicholas Padilla > > www.monstersoftwarellc.com > > > > “Problems cannot be solved by the same level of thinking that created > > them.” > > “Learn from yesterday, live for today, hope for tomorrow. The important > > thing is not to stop questioning. > > < > http://thinkexist.com/quotation/learn_from_yesterday-live_for_today-hope_for/222120.html > > > > ” > > > > Albert Einstein <http://thinkexist.com/quotes/albert_einstein/> > > > > On Wed, Dec 30, 2015 at 7:42 AM, Dave <snoopd...@gmail.com> wrote: > > > >> On Tue, Dec 29, 2015 at 2:39 AM Greg Huber <gregh3...@gmail.com> wrote: > >> > >> > Don't use it my self, have tried but made just made a mess, so went > back > >> > to svn. So -1 for me. > >> > > >> > btw, worth checking out what Struts are doing, using a develop branch, > >> > beforehand. > >> > > >> > >> How strongly do you feel about that -1 Greg? > >> > >> I took a quick look at Struts. They use ASF Git repo and is also able to > >> accept Pull Requests via Git. > >> https://struts.apache.org/submitting-patches.html. > >> > >> I'm not why they use a branch called "develop" instead of master, maybe > >> that is part of the "Git Flow" process they are using? > >> > >> Dave > >> > >> > >> On 28 December 2015 at 15:59, Dave <snoopd...@gmail.com> wrote: > >> > > >> > > Now that Git is officially supported by the ASF, would anybody be > >> opposed > >> > > to moving Roller to Git? All we have to do is to ask the INFRA team > >> to > >> > > switch us over. > >> > > > >> > > My reasons for this move are mostly selfish: I prefer Git, find it > >> easier > >> > > to use and use it on all other projects. Also, a move to Git would > >> make > >> > it > >> > > possible for us to accept GitHub pull-requests. > >> > > > >> > > Thoughts? > >> > > > >> > > Dave > >> > > > >> > > >> > > > > >
