You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@madlib.apache.org by Orhan Kislal <ok...@vmware.com> on 2022/02/28 21:29:27 UTC

Convenience Artifacts and Mac OS Support

Dear MADlib Community,

As you might have noticed, recent release candidates had a number of issues with convenience artifacts. The ASF rules indicate that a release is viable as long as it has the source code so I propose we stop releasing binaries.
In addition, Mac OS support is getting tricky since the end of support for python 2. Without official support, the local libraries are getting harder to maintain which causes instability for MADlib. I propose we drop the official support for Mac OS until we have python 3 support and/or have more confidence in the reproducibility of issues.

Per ASF lazy consensus rules, if no one objects within three days, I'll assume acceptance for both of the proposals.

Thanks,

Orhan Kislal

Re: Convenience Artifacts and Mac OS Support

Posted by Nikhil Kak <nk...@vmware.com>.
+1 to both proposals

________________________________
From: Orhan Kislal <ok...@vmware.com>
Sent: Monday, February 28, 2022 1:29 PM
To: dev@madlib.apache.org <de...@madlib.apache.org>; user@madlib.apache.org <us...@madlib.apache.org>
Subject: Convenience Artifacts and Mac OS Support

Dear MADlib Community,

As you might have noticed, recent release candidates had a number of issues with convenience artifacts. The ASF rules indicate that a release is viable as long as it has the source code so I propose we stop releasing binaries.
In addition, Mac OS support is getting tricky since the end of support for python 2. Without official support, the local libraries are getting harder to maintain which causes instability for MADlib. I propose we drop the official support for Mac OS until we have python 3 support and/or have more confidence in the reproducibility of issues.

Per ASF lazy consensus rules, if no one objects within three days, I'll assume acceptance for both of the proposals.

Thanks,

Orhan Kislal
+

Re: Convenience Artifacts and Mac OS Support

Posted by Nikhil Kak <nk...@vmware.com>.
+1 to both proposals

________________________________
From: Orhan Kislal <ok...@vmware.com>
Sent: Monday, February 28, 2022 1:29 PM
To: dev@madlib.apache.org <de...@madlib.apache.org>; user@madlib.apache.org <us...@madlib.apache.org>
Subject: Convenience Artifacts and Mac OS Support

Dear MADlib Community,

As you might have noticed, recent release candidates had a number of issues with convenience artifacts. The ASF rules indicate that a release is viable as long as it has the source code so I propose we stop releasing binaries.
In addition, Mac OS support is getting tricky since the end of support for python 2. Without official support, the local libraries are getting harder to maintain which causes instability for MADlib. I propose we drop the official support for Mac OS until we have python 3 support and/or have more confidence in the reproducibility of issues.

Per ASF lazy consensus rules, if no one objects within three days, I'll assume acceptance for both of the proposals.

Thanks,

Orhan Kislal
+

Re: Convenience Artifacts and Mac OS Support

Posted by Orhan Kislal <ok...@vmware.com>.
Dear MADlib community,
Thank you for providing feedback on the proposals. We will drop the support for Mac OS and convenience binaries for future releases.
Stay tuned for 1.19.0-RC3.

Thanks,
Orhan Kislal

PS: Ed, thanks for pointing out the wiki pages. I'll archive the redundant steps, in case we need them at some point.
________________________________
From: Orhan Kislal
Sent: Monday, February 28, 2022 4:29 PM
To: dev@madlib.apache.org <de...@madlib.apache.org>; user@madlib.apache.org <us...@madlib.apache.org>
Subject: Convenience Artifacts and Mac OS Support

Dear MADlib Community,

As you might have noticed, recent release candidates had a number of issues with convenience artifacts. The ASF rules indicate that a release is viable as long as it has the source code so I propose we stop releasing binaries.
In addition, Mac OS support is getting tricky since the end of support for python 2. Without official support, the local libraries are getting harder to maintain which causes instability for MADlib. I propose we drop the official support for Mac OS until we have python 3 support and/or have more confidence in the reproducibility of issues.

Per ASF lazy consensus rules, if no one objects within three days, I'll assume acceptance for both of the proposals.

Thanks,

Orhan Kislal

Re: Convenience Artifacts and Mac OS Support

Posted by Ed Espino <es...@apache.org>.
+1 - thank you for considering this release optimization. If this
opimization becomes a reality, It will be important to update the
respective Apache MADlib release process wiki pages as well. I am able to
review release process updates as needed.

-=e

On Mon, Feb 28, 2022 at 3:13 PM Ekta Khanna <kh...@apache.org> wrote:

> +1 for both the proposals
>
> On 2022/02/28 21:29:27 Orhan Kislal wrote:
> > Dear MADlib Community,
> >
> > As you might have noticed, recent release candidates had a number of
> issues with convenience artifacts. The ASF rules indicate that a release is
> viable as long as it has the source code so I propose we stop releasing
> binaries.
> > In addition, Mac OS support is getting tricky since the end of support
> for python 2. Without official support, the local libraries are getting
> harder to maintain which causes instability for MADlib. I propose we drop
> the official support for Mac OS until we have python 3 support and/or have
> more confidence in the reproducibility of issues.
> >
> > Per ASF lazy consensus rules, if no one objects within three days, I'll
> assume acceptance for both of the proposals.
> >
> > Thanks,
> >
> > Orhan Kislal
> >
>

Re: Convenience Artifacts and Mac OS Support

Posted by Ekta Khanna <kh...@apache.org>.
+1 for both the proposals

On 2022/02/28 21:29:27 Orhan Kislal wrote:
> Dear MADlib Community,
> 
> As you might have noticed, recent release candidates had a number of issues with convenience artifacts. The ASF rules indicate that a release is viable as long as it has the source code so I propose we stop releasing binaries.
> In addition, Mac OS support is getting tricky since the end of support for python 2. Without official support, the local libraries are getting harder to maintain which causes instability for MADlib. I propose we drop the official support for Mac OS until we have python 3 support and/or have more confidence in the reproducibility of issues.
> 
> Per ASF lazy consensus rules, if no one objects within three days, I'll assume acceptance for both of the proposals.
> 
> Thanks,
> 
> Orhan Kislal
> 

Re: Convenience Artifacts and Mac OS Support

Posted by Domino Valdano <do...@valdano.email>.
+1

On Mon, Feb 28, 2022 at 1:29 PM Orhan Kislal <ok...@vmware.com> wrote:

> Dear MADlib Community,
>
> As you might have noticed, recent release candidates had a number of
> issues with convenience artifacts. The ASF rules indicate that a release is
> viable as long as it has the source code so I propose we stop releasing
> binaries.
> In addition, Mac OS support is getting tricky since the end of support for
> python 2. Without official support, the local libraries are getting harder
> to maintain which causes instability for MADlib. I propose we drop the
> official support for Mac OS until we have python 3 support and/or have more
> confidence in the reproducibility of issues.
>
> Per ASF lazy consensus rules, if no one objects within three days, I'll
> assume acceptance for both of the proposals.
>
> Thanks,
>
> Orhan Kislal
>

Re: Convenience Artifacts and Mac OS Support

Posted by Domino Valdano <do...@valdano.email>.
+1

On Mon, Feb 28, 2022 at 1:29 PM Orhan Kislal <ok...@vmware.com> wrote:

> Dear MADlib Community,
>
> As you might have noticed, recent release candidates had a number of
> issues with convenience artifacts. The ASF rules indicate that a release is
> viable as long as it has the source code so I propose we stop releasing
> binaries.
> In addition, Mac OS support is getting tricky since the end of support for
> python 2. Without official support, the local libraries are getting harder
> to maintain which causes instability for MADlib. I propose we drop the
> official support for Mac OS until we have python 3 support and/or have more
> confidence in the reproducibility of issues.
>
> Per ASF lazy consensus rules, if no one objects within three days, I'll
> assume acceptance for both of the proposals.
>
> Thanks,
>
> Orhan Kislal
>

Re: Convenience Artifacts and Mac OS Support

Posted by Orhan Kislal <ok...@vmware.com>.
Dear MADlib community,
Thank you for providing feedback on the proposals. We will drop the support for Mac OS and convenience binaries for future releases.
Stay tuned for 1.19.0-RC3.

Thanks,
Orhan Kislal

PS: Ed, thanks for pointing out the wiki pages. I'll archive the redundant steps, in case we need them at some point.
________________________________
From: Orhan Kislal
Sent: Monday, February 28, 2022 4:29 PM
To: dev@madlib.apache.org <de...@madlib.apache.org>; user@madlib.apache.org <us...@madlib.apache.org>
Subject: Convenience Artifacts and Mac OS Support

Dear MADlib Community,

As you might have noticed, recent release candidates had a number of issues with convenience artifacts. The ASF rules indicate that a release is viable as long as it has the source code so I propose we stop releasing binaries.
In addition, Mac OS support is getting tricky since the end of support for python 2. Without official support, the local libraries are getting harder to maintain which causes instability for MADlib. I propose we drop the official support for Mac OS until we have python 3 support and/or have more confidence in the reproducibility of issues.

Per ASF lazy consensus rules, if no one objects within three days, I'll assume acceptance for both of the proposals.

Thanks,

Orhan Kislal