avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Groth <sgr...@yahoo-inc.com.INVALID>
Subject Re: [DISCUSS] Release and code management
Date Fri, 30 Oct 2015 15:18:12 GMT
+1 for moving to github.
-1 for splitting the release. I agree with Philip that it will be more complex.

Sam 


     On Thursday, October 29, 2015 6:56 PM, Sean Busbey <busbey@cloudera.com> wrote:
   

 Why can't we do a single release vote that covers multiple components?

-- 
Sean
On Oct 29, 2015 6:51 PM, "Philip Zeyliger" <philip@cloudera.com> wrote:

> -0.
>
> If you divide the world into N releases, you'll end up having to do release
> management N times.  I think this will make doing releases that much more
> complicated, time-consuming, and error-prone.
>
> Note that you could separate release trains while remaining in a single
> repo.  I'd certainly prefer that than separating into many smaller repos.
>
> -- Philip
>
> On Thu, Oct 29, 2015 at 11:31 AM Ryan Blue <blue@cloudera.com> wrote:
>
> > On 10/29/2015 11:28 AM, Sean Busbey wrote:
> > > On Oct 29, 2015 1:19 PM, "Ryan Blue" <blue@cloudera.com> wrote:
> > >
> > > Where would the language interop tests live if we don't break them out?
> > >
> > > (We already have interop tests, in case that was lost in my original
> > email.)
> >
> > We could either keep them where they are or add a separate repo. Running
> > them with a release candidate would have to be part of the release
> checks.
> >
> > rb
> >
> >
> > --
> > Ryan Blue
> > Software Engineer
> > Cloudera, Inc.
> >
>


  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message