+1
On Thu, Jul 14, 2016 at 4:42 PM, Chris Riccomini
wrote:
> (might want to have a look at
> http://incubator.apache.org/guides/releasemanagement.html as well)
>
> On Thu, Jul 14, 2016 at 4:41 PM, Chris Riccomini
> wrote:
> > @bolke, is the release ready for an RC? If so, I can ship to our
> >
(might want to have a look at
http://incubator.apache.org/guides/releasemanagement.html as well)
On Thu, Jul 14, 2016 at 4:41 PM, Chris Riccomini wrote:
> @bolke, is the release ready for an RC? If so, I can ship to our
> environments and vote accordingly.
>
> On Mon, Jul 11, 2016 at 3:28 PM, Chr
@bolke, is the release ready for an RC? If so, I can ship to our
environments and vote accordingly.
On Mon, Jul 11, 2016 at 3:28 PM, Chris Riccomini wrote:
>> If we need to update this branch I prefer very much to have commits that
>> are also applied against master.
>
> Absolutely +1 to this. Ev
> If we need to update this branch I prefer very much to have commits that
are also applied against master.
Absolutely +1 to this. Everything must go through master first.
On Mon, Jul 11, 2016 at 7:06 AM, Bolke de Bruin wrote:
> Ok. I created a “branch-1.7.2-apache” branch based on airbnb_rb1.7
Ok. I created a “branch-1.7.2-apache” branch based on airbnb_rb1.7.1_4 to which
I added cherry-picked commits to establish Apache compliancy (I think!). If we
need to update this branch I prefer very much to have commits that are also
applied against master.
- Bolke
> Op 11 jul. 2016, om 15:
Ok. I am seeing a “airbnb_rb1.7.1_4” branch, I am assuming this is the branch
to start from (?).
I will work on applying the commits that are required to become compliant.
- Bolke
> Op 11 jul. 2016, om 05:22 heeft Maxime Beauchemin
> het volgende geschreven:
>
> +1
>
> On Fri, Jul 8, 2016
+1
On Fri, Jul 8, 2016 at 5:16 PM, Dan Davydov
wrote:
> +1 the minimal apache cherrypick release makes sense to me.
>
> On Fri, Jul 8, 2016 at 1:14 PM, Chris Riccomini
> wrote:
>
> > Hey Bolke,
> >
> > A fast release with the 1.7.1.3 + cherry picks listed above sounds like
> the
> > way to go.
+1 the minimal apache cherrypick release makes sense to me.
On Fri, Jul 8, 2016 at 1:14 PM, Chris Riccomini
wrote:
> Hey Bolke,
>
> A fast release with the 1.7.1.3 + cherry picks listed above sounds like the
> way to go. Then, a second release in sept where we just cut from master.
>
> I'm +1 on
Hey Bolke,
A fast release with the 1.7.1.3 + cherry picks listed above sounds like the
way to go. Then, a second release in sept where we just cut from master.
I'm +1 on this. Lets us get our Apache ducks in a row without worrying
about stabilizing everything simultaneously.
Cheers,
Chris
On Fr
This was my assessment as well, thus I agree. My suggestion is to start the
process and see if we get questions about this that require us the change our
point of view.
If we do an earlier release I would like to aim for July 19, but that might be
a bit short notice. If needed I can put myself
> but it's acceptable to have a soft dependency on an LGPL component, such
that a user could deploy the LGPL component separately to enable additional
optional features
This is precisely what I believe is going on with Airflow. It's under an
airflow[postgres] package (so `pip install airflow` does
Here are more details on Apache release requirements:
http://www.apache.org/dev/release-publishing.html
http://www.apache.org/dev/release
To summarize, it's much more focused on compliance with licensing, signing
and Apache infrastructure requirements. That's the kind of scrutiny that
a relea
Hi,
This sounds very reasonable to me, though we may be able to do an earlier
release as a practice run for an Apache release with a snapshot of our
production which would consists of the latest release plus a set of cherry
picked PRs.
How does an Apache release differ from a standard release aga
One other thing to note is that I'm planning to run the RCs in all of our
environments to exercise things. We should make sure that we're all
committed (as well as the community) to burning the RCs in on our
respective environments for a few weeks.
On Wed, Jul 6, 2016 at 7:58 PM, Chris Riccomini
Hey Bolke,
> should we aim for a release 1st week of September
Sounds good to me!
> I would want to aim earlier, but due to holidays I guess it might be
smarter to schedule it a bit after?
So would I, personally. I'd be OK with starting RCs now, to be frank. What
do others think?
> Should we v
Hi,
As I don’t think there are any show stoppers to have an Apache release should
we aim for a release 1st week of September? I would want to aim earlier, but
due to holidays I guess it might be smarter to schedule it a bit after?
- RC last week of August giving about two weeks to have it run i
16 matches
Mail list logo
