Excellent! :-)

On 2021/05/23 14:29:43, Kaxil Naik <kaxiln...@gmail.com> wrote: 
> Yup, this is what we do at Apache Airflow too.
> 
> And I did the same for the recently released Apache Airflow Helm Chart.
> 
> Example:
> https://lists.apache.org/x/thread.html/rd2a0a6386c22bb0942c28746d59d105adc0364715c15ea772e23e105@%3Cdev.airflow.apache.org%3E
> 
> I have releasing Airflow versions from past 3 or so years, so have good
> experience with ASF guidelines around it.
> 
> Regards,
> Kaxil
> 
> 
> 
> On Sun, May 23, 2021, 15:24 Sharan Foga <sha...@apache.org> wrote:
> 
> >
> >
> > On 2021/05/23 14:15:32, Kaxil Naik <kaxiln...@gmail.com> wrote:
> > > Yeah, as far as I know we don't have a release. For Kibble 2 we can
> > release
> > > Python wheel/binary artifacts.
> >
> > I know there is some discussion going on about binary artifacts and Apache
> > releases as generally Apache releases need to be source code, though they
> > have been supplemented with binary artifacts. We just need to make sure we
> > adhere to the current policy.
> >
> > Thanks
> > Sharan
> >
> > >
> > > Regards,
> > > Kaxil
> > >
> > > On Sun, May 23, 2021, 15:10 Tomasz Urbaszek <turbas...@apache.org>
> > wrote:
> > >
> > > > As far as I know Apache Kibble was never released. I would propose
> > > > using Github milestones to track future releases of new Kibble:
> > > > https://github.com/apache/kibble/milestone/1
> > > >
> > > > Tomek
> > > >
> > > > On Sun, 23 May 2021 at 16:00, Sharan Foga <sha...@apache.org> wrote:
> > > > >
> > > > > Hi All
> > > > >
> > > > > Thanks to all who helped review our Board report. We got some
> > feedback
> > > > comment to include details of our last release in our next report. I've
> > > > been searching through our mailing archives and can't find any details
> > or
> > > > Vote of the project ever doing a release.
> > > > >
> > > > > If this is the case then we need to think about planning one as part
> > of
> > > > our roadmap.
> > > > >
> > > > > Thanks
> > > > > Sharan
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> 

Reply via email to