[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977788#comment-15977788
]
Neil Griffin commented on PORTLETBRIDGE-188:
This is being implemented
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1597#comment-1597
]
Neil Griffin edited comment on PORTLETBRIDGE-192 at 4/20/17 11:23 PM:
---
Ah, this may be why it's worked for me -- smaller projects with defined
release cycles.
Anyway, I never meant to imply that git == git flow. We will need some sort
of process, though, and the DeltaSpike one seems like a good place to start.
___
Kito D. Mann | @kito99 | Author, JSF in Action
Web
I prefer working with GIT, and agree with the points already made in this
thread about its benefits. I'm not sure how much pain a meaningful
transition will cause - from that perspective, starting with the components
is a great idea.
+1
Regards,
Bill
On Thu, Apr 20, 2017 at 8:24 AM, Bernd Bohma
Thanks Mark
gitflow is not solving any technical problem. It's just more complicated
and it's looks good from a high level perspective.
Regards
Bernd
On Thu, Apr 20, 2017 at 2:02 PM, Mark Struberg wrote:
> gitflow is pure pita ;)
> It basically only works for companies where you have a single
gitflow is pure pita ;)
It basically only works for companies where you have a single manager who
decides what goes in and what not.
But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is
just a fancy name for a development process with an explicit build-branch and a
bui
hi @ all,
just fyi:
[1] works very well for ds since the beginning.
regards,
gerhard
[1] https://deltaspike.apache.org/suggested-git-workflows.html
2017-04-19 14:45 GMT+02:00 Kito Mann :
> Hello Bernd,
>
> I like GitFlow for coordinating with multiple developers. However, if
> everyone is se