I personally expect the patches to be attached to the JIRAs as before because it allows the decisions made and comments left to be revisited at the later point in time if needed.
I don't think it is a good idea to use multiple remotes for cross-merges without proper audit in the JIRA. Cos On Fri, Feb 14, 2014 at 07:59AM, Jay Vyas wrote: > +1 to adopt it, > > .but now I'm still wondering , it's not clear: does this mean we can use > pull requests to submit patches? > > It seems to say the jiras will track pull requests...but doesn't say that > the github is a proper medium for allowing pull requests to be commited? > > > On Feb 14, 2014, at 12:22 AM, Mark Grover <[email protected]> wrote: > > > > I am a +1. Expands our ecosystem to developers who prefers using github:-) > > > > Unless there's a -1, I create an INFRA jira. > > > > > >> On Thu, Feb 13, 2014 at 9:12 PM, Konstantin Boudnik <[email protected]> > >> wrote: > >> > >> What benefits you expect the gain from it? > >> > >> I am pretty much -0 on the thing, just trying to educate myself ;) > >> Cos > >> > >>> On Thu, Feb 13, 2014 at 03:25PM, Roman Shaposhnik wrote: > >>> Hi! > >>> > >>> this is pretty cool: > >> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and > >>> > >>> Can somebody, please, volunteer to do the > >>> required thing with INFRA? > >>> > >>> Thanks, > >>> Roman. > >>
