[jira] [Resolved] (YUNIKORN-897) CLONE - CLONE - Update the copyright years in NOTICE file

2021-10-22 Thread Chaoran Yu (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaoran Yu resolved YUNIKORN-897.
-
  Assignee: Chaoran Yu  (was: Tao Yang)
Resolution: Not A Problem

This Jira was generated after cloning the parent Jira of the 0.11 release. It 
is no longer applicable for the 1.0 release as we are still in the year of 2021

> CLONE - CLONE - Update the copyright years in NOTICE file
> -
>
> Key: YUNIKORN-897
> URL: https://issues.apache.org/jira/browse/YUNIKORN-897
> Project: Apache YuniKorn
>  Issue Type: Sub-task
>Reporter: Chaoran Yu
>Assignee: Chaoran Yu
>Priority: Major
>  Labels: newbie, pull-request-available
> Fix For: 0.11
>
>
> Currently, the NOTICE file in the release tarball has the following context: 
> "Copyright 2019-2020 The Apache Software Foundation". According to 
> https://www.apache.org/legal/src-headers.html#notice, we need to update the 
> YEAR-YEAR to 2019-2021.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-903) CLONE - Cleanup release area

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-903:
---

 Summary: CLONE - Cleanup release area
 Key: YUNIKORN-903
 URL: https://issues.apache.org/jira/browse/YUNIKORN-903
 Project: Apache YuniKorn
  Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


This step should be performed after the website updates have been made as the 
download links change.

There should only be one release, the latest, in the release area. Any release 
that has been in the release area will be automatically copied to the archive. 
Older releases should be downloaded from the archive directly, not from the 
release area.

The releases need to clean up in two locations:
 * Remove the newly released version from the _dev_ area by removing the old 
release candidate directory. For the location see [release candidate 
location|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#Upload-Release-Candidate-Artefacts]
 * Remove the non-current release from the _release_ area by removing the old 
release directory. For the location see [release 
location|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#Publish-the-Release]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-904) CLONE - Update website announce bar

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-904:
---

 Summary: CLONE - Update website announce bar
 Key: YUNIKORN-904
 URL: https://issues.apache.org/jira/browse/YUNIKORN-904
 Project: Apache YuniKorn
  Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-898) CLONE - Add 0.11.0 to the artifact hub

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-898:
---

 Summary: CLONE - Add 0.11.0 to the artifact hub
 Key: YUNIKORN-898
 URL: https://issues.apache.org/jira/browse/YUNIKORN-898
 Project: Apache YuniKorn
  Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


We need to update our gh-pages in the release repository, so the artifacthub 
will have the new release as well: 
https://artifacthub.io/packages/helm/yunikorn/yunikorn




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-901) CLONE - Update the website for v0.11

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-901:
---

 Summary: CLONE - Update the website for v0.11
 Key: YUNIKORN-901
 URL: https://issues.apache.org/jira/browse/YUNIKORN-901
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: website
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


Updates include:
* Create a new documentation version.
* Create the release announcement.
* Update the download page of the website.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-894) CLONE - Create the docs release for v0.11

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-894:
---

 Summary: CLONE - Create the docs release for v0.11
 Key: YUNIKORN-894
 URL: https://issues.apache.org/jira/browse/YUNIKORN-894
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: documentation
Reporter: Chaoran Yu
Assignee: Chen Yu Teng
 Fix For: 0.11


Update the doc version and add the release announcement on the web site 
following the [release 
procedure|https://github.com/apache/incubator-yunikorn-release/blob/master/docs/release-procedure.md#update-the-website]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-900) CLONE - Update helm index for v0.11

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-900:
---

 Summary: CLONE - Update helm index for v0.11
 Key: YUNIKORN-900
 URL: https://issues.apache.org/jira/browse/YUNIKORN-900
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: release
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-902) CLONE - Update the CHANGELOG and generate the release

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-902:
---

 Summary: CLONE - Update the CHANGELOG and generate the release
 Key: YUNIKORN-902
 URL: https://issues.apache.org/jira/browse/YUNIKORN-902
 Project: Apache YuniKorn
  Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


* Go to the [releases page in 
jira|https://issues.apache.org/jira/projects/YUNIKORN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released-unreleased]
 * Click on the version that is about to be released, i.e. {{0.11}}
 * Click on the {{Release Notes}} link on the top of the page
 * Click the button {{Configure Release Notes}}
 * Select the style {{Text}} and click {{create}}
 * Scroll to the bottom of the page and copy the content of the text area and 
update the 
[CHANGELOG|https://github.com/apache/incubator-yunikorn-release/blob/master/release-top-level-artifacts/CHANGELOG]
 file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-893) CLONE - Create 0.11.0 release notes

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-893:
---

 Summary: CLONE - Create 0.11.0 release notes
 Key: YUNIKORN-893
 URL: https://issues.apache.org/jira/browse/YUNIKORN-893
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: release
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


Release notes should be updated in CHANGELOG file which will be added into the 
release artifacts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-895) CLONE - Update shim and core dependencies on master branch

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-895:
---

 Summary: CLONE - Update shim and core dependencies on master branch
 Key: YUNIKORN-895
 URL: https://issues.apache.org/jira/browse/YUNIKORN-895
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: shim - kubernetes
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


The current scheduler is building with an older release of the core.

There are two changes that need to be made:
 * In preparation for the v0.11 release we need to update the dependency in 
branch-0.11 to start pointing to a core version in branch-0.11
 * The master of the shim needs an update to point to the latest version of the 
core master



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-899) CLONE - [Helm chart] Update supported K8s versions

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-899:
---

 Summary: CLONE - [Helm chart] Update supported K8s versions
 Key: YUNIKORN-899
 URL: https://issues.apache.org/jira/browse/YUNIKORN-899
 Project: Apache YuniKorn
  Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Wen-Chien,Juan
 Fix For: 0.11


Right now the README in the Helm chart has the following info related the 
supported K8s versions:

upported K8s versions
|K8s Version|Support?|
|-|:-:|
|1.12.x (or earlier)|X|
|1.13.x|√|
|1.14.x|√|
|1.15.x|√|
|1.16.x|To be verified|
|1.17.x|To be verified|

This is not true anymore, since the shim already uses 1.16 version, and the 
tests are running with 1.17 1.18 and 1.19.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-891) [Umbrella] YuniKorn 1.0 release-related efforts

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-891:
---

 Summary: [Umbrella] YuniKorn 1.0 release-related efforts
 Key: YUNIKORN-891
 URL: https://issues.apache.org/jira/browse/YUNIKORN-891
 Project: Apache YuniKorn
  Issue Type: Task
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


This umbrella is to track the work items needed for 0.11.0 release.
 Release manager: Kinga Marton.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-897) CLONE - CLONE - Update the copyright years in NOTICE file

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-897:
---

 Summary: CLONE - CLONE - Update the copyright years in NOTICE file
 Key: YUNIKORN-897
 URL: https://issues.apache.org/jira/browse/YUNIKORN-897
 Project: Apache YuniKorn
  Issue Type: Sub-task
Reporter: Chaoran Yu
Assignee: Tao Yang
 Fix For: 0.11


Currently, the NOTICE file in the release tarball has the following context: 
"Copyright 2019-2020 The Apache Software Foundation". According to 
https://www.apache.org/legal/src-headers.html#notice, we need to update the 
YEAR-YEAR to 2019-2021.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-892) CLONE - Create 0.11.0 helm chart release

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-892:
---

 Summary: CLONE - Create 0.11.0 helm chart release
 Key: YUNIKORN-892
 URL: https://issues.apache.org/jira/browse/YUNIKORN-892
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: release
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


Release the helm charts in yunikorn-release repository with following steps:
 * create a new branch: branch-0.11
 * update version to 0.110 in helm-charts/yunikorn/Chart.yaml
 * tag v0.11.0 ( after 0.11.0 release notes have been )



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-896) CLONE - Tag release 0.11.0 and update go mod files

2021-10-22 Thread Chaoran Yu (Jira) 
Chaoran Yu created YUNIKORN-896:
---

 Summary: CLONE - Tag release 0.11.0 and update go mod files
 Key: YUNIKORN-896
 URL: https://issues.apache.org/jira/browse/YUNIKORN-896
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: core - common, shim - kubernetes
Reporter: Chaoran Yu
Assignee: Kinga Marton
 Fix For: 0.11


After tagging for the 0.11.0 release the dependencies for the core and shim 
need to be updated to point to the new tag.
 Order:
 * tag si and web
 * tag core and go mod update (si ref)
 * tag shim and go mod update (core and si ref)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Weiwei Yang 
Hi Chaoran/Sunil

I don't think we have the wiki sort of thing.
For in-progress releases, we can use the JIRA tag to track, like Chaoran
pointed out:
https://issues.apache.org/jira/projects/YUNIKORN/versions/12350288.
For released versions, we publish them to our website:
https://yunikorn.apache.org/community/download/.

On Fri, Oct 22, 2021 at 4:02 PM Chaoran Yu  wrote:

> I saw that we already have a JIRA filter for 1.0
> .
> Sunil, where is the release Wiki supposed to be? I'll create one for 1.0
>
> On Fri, Oct 22, 2021 at 12:16 PM Sunil Govindan  wrote:
>
> > +1
> >
> > Yes. Lets start the planning.
> >
> > Chaoran, @Chenya, and Wilfred,
> > Could we create a release wiki and place this timeline with a Jira
> filter?
> > I think it will be a good start for this entire process.
> >
> > Thanks
> > Sunil
> >
> >
> > On Fri, Oct 22, 2021 at 11:54 AM Chenya Zhang <
> chenyazhangche...@gmail.com
> > >
> > wrote:
> >
> > > Great to see that we are going to have a new 1.0.0 release!
> > >
> > > I could help Chaoran and shadow this release. Would be interested in
> > > becoming our next release manager but happy to take a fight when it
> > comes.
> > > :D
> > >
> > > Will follow up on this thread for v1.0.0.
> > >
> > > Best,
> > > Chenya
> > >
> > > On Fri, Oct 22, 2021 at 11:37 AM Weiwei Yang  wrote:
> > >
> > > > Hi Craig
> > > >
> > > > I think officially supporting 3 major K8s versions should be enough,
> > but
> > > we
> > > > need to update to 1.19, 1.20, and 1.21.
> > > > 1.18 is EoL per https://endoflife.date/kubernetes . If we continue
> our
> > > > release cadence, most likely we can move 1 major release at a time
> and
> > > that
> > > > aligns with the K8s releases.
> > > >
> > > > On Fri, Oct 22, 2021 at 9:29 AM Craig Condit  >
> > > > wrote:
> > > >
> > > > > Looking forward to 1.0 release as well, and thanks Chaoran for
> > > > > volunteering to manage the release.
> > > > >
> > > > > Should we also update our supported version matrix to include 1.18,
> > > 1.19,
> > > > > 1.20, and 1.21? Updating the e2e test matrix should be a one-line
> > > change,
> > > > > and as part of the rebuild against 1.20, I verified that 1.21 is
> > > > functional.
> > > > >
> > > > > Craig
> > > > >
> > > > > > On Oct 22, 2021, at 2:15 AM, Weiwei Yang 
> wrote:
> > > > > >
> > > > > > Sounds great, thank you Chaoran!
> > > > > >
> > > > > > On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu <
> > yuchaoran2...@gmail.com
> > > >
> > > > > wrote:
> > > > > >
> > > > > >> Hey guys,
> > > > > >>
> > > > > >> I volunteer to be the release manager this time, if nobody else
> > has
> > > > > >> volunteered already.
> > > > > >>
> > > > > >> The proposed timeline sounds right to be. It will allow for
> ample
> > > time
> > > > > for
> > > > > >> stabilization and verification.
> > > > > >>
> > > > > >> Chaoran
> > > > > >>
> > > > > >>
> > > > > >> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang 
> > > wrote:
> > > > > >>
> > > > > >>> Hi Wilfred
> > > > > >>>
> > > > > >>> Thanks. Sounds good to me.
> > > > > >>> Does anyone want to be the release manager for 1.0? The apache
> > way
> > > > > >>> encourages more people to get involved in the release process.
> > > > > >>>
> > > > > >>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> > > > > >>> wilfr...@apache.org>
> > > > > >>> wrote:
> > > > > >>>
> > > > >  Hi,
> > > > > 
> > > > >  We have been making big steps since our last release. Some
> major
> > > > > >> changes
> > > > >  have gone in and some are almost ready. The changes include:
> > > > >  - rest API updates
> > > > >  - new node storage and sorting
> > > > >  - upgrade to a later K8s version as a build dependency
> > > > >  - scheduler interface change
> > > > > 
> > > > >  Work is ongoing on generating a new set of performance
> figures.
> > > This
> > > > >  includes documenting how to run our performance tests so we
> can
> > > > repeat
> > > > > >>> them
> > > > >  when we want to.
> > > > > 
> > > > >  Based on all this work I would like to propose a 1.0.0 release
> > to
> > > be
> > > > > >>> ready
> > > > >  for a vote by the incubator PMC by the start of December 2021.
> > > This
> > > > > >> will
> > > > >  give us some time to get the last fixes in and stabilise the
> > > > release.
> > > > > A
> > > > >  release for us is still a multistep project:
> > > > >  - fork and prepare the release
> > > > >  - vote in the project
> > > > >  - vote in the incubator PMC
> > > > >  Looking back at the last release cycles that means we should
> > have
> > > a
> > > > > >> build
> > > > >  ready for voting by 22 November on the dev list. Which would
> > mean
> > > > that
> > > > > >> we
> > > > >  fork the release at the latest in the second week of November.
> > > > > 
> > > > >  Please let me know if the timeline is too ambitious or not
>

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Chaoran Yu 
I saw that we already have a JIRA filter for 1.0
.
Sunil, where is the release Wiki supposed to be? I'll create one for 1.0

On Fri, Oct 22, 2021 at 12:16 PM Sunil Govindan  wrote:

> +1
>
> Yes. Lets start the planning.
>
> Chaoran, @Chenya, and Wilfred,
> Could we create a release wiki and place this timeline with a Jira filter?
> I think it will be a good start for this entire process.
>
> Thanks
> Sunil
>
>
> On Fri, Oct 22, 2021 at 11:54 AM Chenya Zhang  >
> wrote:
>
> > Great to see that we are going to have a new 1.0.0 release!
> >
> > I could help Chaoran and shadow this release. Would be interested in
> > becoming our next release manager but happy to take a fight when it
> comes.
> > :D
> >
> > Will follow up on this thread for v1.0.0.
> >
> > Best,
> > Chenya
> >
> > On Fri, Oct 22, 2021 at 11:37 AM Weiwei Yang  wrote:
> >
> > > Hi Craig
> > >
> > > I think officially supporting 3 major K8s versions should be enough,
> but
> > we
> > > need to update to 1.19, 1.20, and 1.21.
> > > 1.18 is EoL per https://endoflife.date/kubernetes . If we continue our
> > > release cadence, most likely we can move 1 major release at a time and
> > that
> > > aligns with the K8s releases.
> > >
> > > On Fri, Oct 22, 2021 at 9:29 AM Craig Condit 
> > > wrote:
> > >
> > > > Looking forward to 1.0 release as well, and thanks Chaoran for
> > > > volunteering to manage the release.
> > > >
> > > > Should we also update our supported version matrix to include 1.18,
> > 1.19,
> > > > 1.20, and 1.21? Updating the e2e test matrix should be a one-line
> > change,
> > > > and as part of the rebuild against 1.20, I verified that 1.21 is
> > > functional.
> > > >
> > > > Craig
> > > >
> > > > > On Oct 22, 2021, at 2:15 AM, Weiwei Yang  wrote:
> > > > >
> > > > > Sounds great, thank you Chaoran!
> > > > >
> > > > > On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu <
> yuchaoran2...@gmail.com
> > >
> > > > wrote:
> > > > >
> > > > >> Hey guys,
> > > > >>
> > > > >> I volunteer to be the release manager this time, if nobody else
> has
> > > > >> volunteered already.
> > > > >>
> > > > >> The proposed timeline sounds right to be. It will allow for ample
> > time
> > > > for
> > > > >> stabilization and verification.
> > > > >>
> > > > >> Chaoran
> > > > >>
> > > > >>
> > > > >> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang 
> > wrote:
> > > > >>
> > > > >>> Hi Wilfred
> > > > >>>
> > > > >>> Thanks. Sounds good to me.
> > > > >>> Does anyone want to be the release manager for 1.0? The apache
> way
> > > > >>> encourages more people to get involved in the release process.
> > > > >>>
> > > > >>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> > > > >>> wilfr...@apache.org>
> > > > >>> wrote:
> > > > >>>
> > > >  Hi,
> > > > 
> > > >  We have been making big steps since our last release. Some major
> > > > >> changes
> > > >  have gone in and some are almost ready. The changes include:
> > > >  - rest API updates
> > > >  - new node storage and sorting
> > > >  - upgrade to a later K8s version as a build dependency
> > > >  - scheduler interface change
> > > > 
> > > >  Work is ongoing on generating a new set of performance figures.
> > This
> > > >  includes documenting how to run our performance tests so we can
> > > repeat
> > > > >>> them
> > > >  when we want to.
> > > > 
> > > >  Based on all this work I would like to propose a 1.0.0 release
> to
> > be
> > > > >>> ready
> > > >  for a vote by the incubator PMC by the start of December 2021.
> > This
> > > > >> will
> > > >  give us some time to get the last fixes in and stabilise the
> > > release.
> > > > A
> > > >  release for us is still a multistep project:
> > > >  - fork and prepare the release
> > > >  - vote in the project
> > > >  - vote in the incubator PMC
> > > >  Looking back at the last release cycles that means we should
> have
> > a
> > > > >> build
> > > >  ready for voting by 22 November on the dev list. Which would
> mean
> > > that
> > > > >> we
> > > >  fork the release at the latest in the second week of November.
> > > > 
> > > >  Please let me know if the timeline is too ambitious or not
> > ambitious
> > > >  enough.
> > > > 
> > > >  Wilfred
> > > > 
> > > > >>>
> > > > >>
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > > > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Sunil Govindan 
+1

Yes. Lets start the planning.

Chaoran, @Chenya, and Wilfred,
Could we create a release wiki and place this timeline with a Jira filter?
I think it will be a good start for this entire process.

Thanks
Sunil


On Fri, Oct 22, 2021 at 11:54 AM Chenya Zhang 
wrote:

> Great to see that we are going to have a new 1.0.0 release!
>
> I could help Chaoran and shadow this release. Would be interested in
> becoming our next release manager but happy to take a fight when it comes.
> :D
>
> Will follow up on this thread for v1.0.0.
>
> Best,
> Chenya
>
> On Fri, Oct 22, 2021 at 11:37 AM Weiwei Yang  wrote:
>
> > Hi Craig
> >
> > I think officially supporting 3 major K8s versions should be enough, but
> we
> > need to update to 1.19, 1.20, and 1.21.
> > 1.18 is EoL per https://endoflife.date/kubernetes . If we continue our
> > release cadence, most likely we can move 1 major release at a time and
> that
> > aligns with the K8s releases.
> >
> > On Fri, Oct 22, 2021 at 9:29 AM Craig Condit 
> > wrote:
> >
> > > Looking forward to 1.0 release as well, and thanks Chaoran for
> > > volunteering to manage the release.
> > >
> > > Should we also update our supported version matrix to include 1.18,
> 1.19,
> > > 1.20, and 1.21? Updating the e2e test matrix should be a one-line
> change,
> > > and as part of the rebuild against 1.20, I verified that 1.21 is
> > functional.
> > >
> > > Craig
> > >
> > > > On Oct 22, 2021, at 2:15 AM, Weiwei Yang  wrote:
> > > >
> > > > Sounds great, thank you Chaoran!
> > > >
> > > > On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu  >
> > > wrote:
> > > >
> > > >> Hey guys,
> > > >>
> > > >> I volunteer to be the release manager this time, if nobody else has
> > > >> volunteered already.
> > > >>
> > > >> The proposed timeline sounds right to be. It will allow for ample
> time
> > > for
> > > >> stabilization and verification.
> > > >>
> > > >> Chaoran
> > > >>
> > > >>
> > > >> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang 
> wrote:
> > > >>
> > > >>> Hi Wilfred
> > > >>>
> > > >>> Thanks. Sounds good to me.
> > > >>> Does anyone want to be the release manager for 1.0? The apache way
> > > >>> encourages more people to get involved in the release process.
> > > >>>
> > > >>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> > > >>> wilfr...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  Hi,
> > > 
> > >  We have been making big steps since our last release. Some major
> > > >> changes
> > >  have gone in and some are almost ready. The changes include:
> > >  - rest API updates
> > >  - new node storage and sorting
> > >  - upgrade to a later K8s version as a build dependency
> > >  - scheduler interface change
> > > 
> > >  Work is ongoing on generating a new set of performance figures.
> This
> > >  includes documenting how to run our performance tests so we can
> > repeat
> > > >>> them
> > >  when we want to.
> > > 
> > >  Based on all this work I would like to propose a 1.0.0 release to
> be
> > > >>> ready
> > >  for a vote by the incubator PMC by the start of December 2021.
> This
> > > >> will
> > >  give us some time to get the last fixes in and stabilise the
> > release.
> > > A
> > >  release for us is still a multistep project:
> > >  - fork and prepare the release
> > >  - vote in the project
> > >  - vote in the incubator PMC
> > >  Looking back at the last release cycles that means we should have
> a
> > > >> build
> > >  ready for voting by 22 November on the dev list. Which would mean
> > that
> > > >> we
> > >  fork the release at the latest in the second week of November.
> > > 
> > >  Please let me know if the timeline is too ambitious or not
> ambitious
> > >  enough.
> > > 
> > >  Wilfred
> > > 
> > > >>>
> > > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> > >
> > >
> >
>

Re: Broadcast YuniKorn to the Industry!

2021-10-22 Thread Sunil Govindan 
Awesome!

Yes, we can create PR against our website branch and get this information
posted.
@wilfr...@apache.org  , could we create a banner on
yunikorn website for this?

Also, let's broadcast from YuniKorn twitter handle as well. Once we have
that writeup, I can help to post that.

Thanks
Sunil

On Fri, Oct 22, 2021 at 12:03 PM Chenya Zhang 
wrote:

> +1 need a short description from Wilfred, thanks!
>
> Meanwhile, I'm thinking about adding a new section "Meetup" under
> "Community" on our website and also adding a section on our homepage for
> the next event.
>
> Do we have a process that can be shared to update our website?
>
> Thanks,
> Chenya
>
> On Fri, Oct 22, 2021 at 11:42 AM Weiwei Yang  wrote:
>
> > ACK'd, sounds great.
> > We need to have a sharable message to adv this. @Wilfred Spiegelenburg
> >  , could you pls share a short description of the
> > session so we can put that in a message + planedDate + howToJoin and
> start
> > to spread?
> >
> > On Fri, Oct 22, 2021 at 7:17 AM Chenya Zhang <
> chenyazhangche...@gmail.com>
> > wrote:
> >
> > > Wonderful, thanks Sunil and Chaoran for the input!
> > >
> > > Our first speaker will be Wilfred sharing about features in the latest
> > > release, Gang scheduling, bin packing, node sorting improvement, etc.
> > >
> > > We will post an event from YuniKorn website, use LinkedIn meetup &
> posts
> > to
> > > attract more attendees, and YouTube for a live broadcast.
> > >
> > > If everyone agrees, we will finalize our 1st external meetup this year
> on
> > > Nov 18th 4:30 - 6:00pm PST.
> > >
> > > Look forward to more ideas from everyone, and let’s get ready &
> excited!
> > >
> > > Cheers,
> > > Chenya
> > >
> > >
> > > On Thu, Oct 21, 2021 at 11:57 PM Chaoran Yu 
> > > wrote:
> > >
> > > > Thanks Sunil for the input. Then let's do Nov 18th for the first
> event.
> > > > 4:30-6:00pm PST should be a good start. We can gauge interest and
> then
> > > > change time to cater to multiple time zones for alternating
> > occurrences.
> > > >
> > > >
> > > > On Mon, Oct 18, 2021 at 7:42 AM Sunil Govindan 
> > > wrote:
> > > >
> > > > > Thanks, Charon. Yes, I second this.
> > > > > Monthly events could be organized from Linkedin also. Meetup is not
> > > much
> > > > > used, I think.
> > > > >
> > > > > Let's start with November 18th, as you suggested. And each
> > alternative
> > > > > month, we can do one on PST morning and then during the evening.
> > > > > This will help to cover all time zones as we have folks from
> > Budapest,
> > > > > India, China, East Asia, and Australia.
> > > > >
> > > > > On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang <
> > > > chenyazhangche...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Sure, that sounds great!
> > > > > >
> > > > > > If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st
> event,
> > > how
> > > > > > does this slot fit into your schedules?
> > > > > >
> > > > > > Besides speaker talks, we could also have panel or roundtable
> > > > > discussions.
> > > > > >
> > > > > > To broadcast YuniKorn to more people, we could also find if there
> > are
> > > > > other
> > > > > > highly popular meetups in the industry and do a joint talk or
> > > > discussion.
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > Cheers,
> > > > > > Chenya
> > > > > >
> > > > > > On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu <
> > yuchaoran2...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Great, that works too. Chenya, do you want to schedule such a
> > > monthly
> > > > > > > meeting starting November? The first one can be during the week
> > > > before
> > > > > > > Thanksgiving. Once we finalize the schedule, we can think about
> > > > > speakers
> > > > > > > and topics.
> > > > > > >
> > > > > > > On Thu, Oct 14, 2021 at 9:49 PM Weiwei Yang 
> > > wrote:
> > > > > > >
> > > > > > >> I am not aware of that sort of sponsorship. We can at least
> > setup
> > > > > > virtual
> > > > > > >> meetings via Zoom.
> > > > > > >> A monthly recurring meeting might be a good start : )
> > > > > > >>
> > > > > > >> On Thu, Oct 14, 2021 at 9:27 PM Chaoran Yu <
> > > yuchaoran2...@gmail.com
> > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > I second this proposal!
> > > > > > >> >
> > > > > > >> > Instead of a one-time event, we can do a recurring meetup
> > > (monthly
> > > > > or
> > > > > > >> > bi-monthly) and invite YuniKorn developers and users to talk
> > > about
> > > > > > their
> > > > > > >> > experience and insights. A recurring event is well suited
> for
> > > > > > >> cultivating a
> > > > > > >> > community. I took a look at Meetup.com. They charge a
> monthly
> > > fee
> > > > > for
> > > > > > >> > organizing a meetup group (see attached). Does ASF have any
> > > > programs
> > > > > > >> that
> > > > > > >> > can sponsor such an effort? Or we can explore other options
> as
> > > > well.
> > > > > > >> >
> > > > > > >> > Chaoran
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > On Tue, Oct

Re: Broadcast YuniKorn to the Industry!

2021-10-22 Thread Weiwei Yang 
Great idea!


> Do we have a process that can be shared to update our website?
>

this is totally sharable, and we should definitely get it published on our
website. I think we can consolidate the current content in
https://yunikorn.apache.org/community/sessions/ , and rebuild it with the
following sections:

Coming Meetup session
 - speaker
 - abstract
 - date and time

Past sessions, conf talks
  - a list of past session recordings

And then add a section somewhere in the homepage for the "upcoming meetup".

On Fri, Oct 22, 2021 at 12:03 PM Chenya Zhang 
wrote:

> +1 need a short description from Wilfred, thanks!
>
> Meanwhile, I'm thinking about adding a new section "Meetup" under
> "Community" on our website and also adding a section on our homepage for
> the next event.
>
> Do we have a process that can be shared to update our website?
>
> Thanks,
> Chenya
>
> On Fri, Oct 22, 2021 at 11:42 AM Weiwei Yang  wrote:
>
> > ACK'd, sounds great.
> > We need to have a sharable message to adv this. @Wilfred Spiegelenburg
> >  , could you pls share a short description of the
> > session so we can put that in a message + planedDate + howToJoin and
> start
> > to spread?
> >
> > On Fri, Oct 22, 2021 at 7:17 AM Chenya Zhang <
> chenyazhangche...@gmail.com>
> > wrote:
> >
> > > Wonderful, thanks Sunil and Chaoran for the input!
> > >
> > > Our first speaker will be Wilfred sharing about features in the latest
> > > release, Gang scheduling, bin packing, node sorting improvement, etc.
> > >
> > > We will post an event from YuniKorn website, use LinkedIn meetup &
> posts
> > to
> > > attract more attendees, and YouTube for a live broadcast.
> > >
> > > If everyone agrees, we will finalize our 1st external meetup this year
> on
> > > Nov 18th 4:30 - 6:00pm PST.
> > >
> > > Look forward to more ideas from everyone, and let’s get ready &
> excited!
> > >
> > > Cheers,
> > > Chenya
> > >
> > >
> > > On Thu, Oct 21, 2021 at 11:57 PM Chaoran Yu 
> > > wrote:
> > >
> > > > Thanks Sunil for the input. Then let's do Nov 18th for the first
> event.
> > > > 4:30-6:00pm PST should be a good start. We can gauge interest and
> then
> > > > change time to cater to multiple time zones for alternating
> > occurrences.
> > > >
> > > >
> > > > On Mon, Oct 18, 2021 at 7:42 AM Sunil Govindan 
> > > wrote:
> > > >
> > > > > Thanks, Charon. Yes, I second this.
> > > > > Monthly events could be organized from Linkedin also. Meetup is not
> > > much
> > > > > used, I think.
> > > > >
> > > > > Let's start with November 18th, as you suggested. And each
> > alternative
> > > > > month, we can do one on PST morning and then during the evening.
> > > > > This will help to cover all time zones as we have folks from
> > Budapest,
> > > > > India, China, East Asia, and Australia.
> > > > >
> > > > > On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang <
> > > > chenyazhangche...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Sure, that sounds great!
> > > > > >
> > > > > > If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st
> event,
> > > how
> > > > > > does this slot fit into your schedules?
> > > > > >
> > > > > > Besides speaker talks, we could also have panel or roundtable
> > > > > discussions.
> > > > > >
> > > > > > To broadcast YuniKorn to more people, we could also find if there
> > are
> > > > > other
> > > > > > highly popular meetups in the industry and do a joint talk or
> > > > discussion.
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > Cheers,
> > > > > > Chenya
> > > > > >
> > > > > > On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu <
> > yuchaoran2...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Great, that works too. Chenya, do you want to schedule such a
> > > monthly
> > > > > > > meeting starting November? The first one can be during the week
> > > > before
> > > > > > > Thanksgiving. Once we finalize the schedule, we can think about
> > > > > speakers
> > > > > > > and topics.
> > > > > > >
> > > > > > > On Thu, Oct 14, 2021 at 9:49 PM Weiwei Yang 
> > > wrote:
> > > > > > >
> > > > > > >> I am not aware of that sort of sponsorship. We can at least
> > setup
> > > > > > virtual
> > > > > > >> meetings via Zoom.
> > > > > > >> A monthly recurring meeting might be a good start : )
> > > > > > >>
> > > > > > >> On Thu, Oct 14, 2021 at 9:27 PM Chaoran Yu <
> > > yuchaoran2...@gmail.com
> > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > I second this proposal!
> > > > > > >> >
> > > > > > >> > Instead of a one-time event, we can do a recurring meetup
> > > (monthly
> > > > > or
> > > > > > >> > bi-monthly) and invite YuniKorn developers and users to talk
> > > about
> > > > > > their
> > > > > > >> > experience and insights. A recurring event is well suited
> for
> > > > > > >> cultivating a
> > > > > > >> > community. I took a look at Meetup.com. They charge a
> monthly
> > > fee
> > > > > for
> > > > > > >> > organizing a meetup group (see attached). Does ASF have any
> > > > programs
> >

Re: Broadcast YuniKorn to the Industry!

2021-10-22 Thread Chenya Zhang 
+1 need a short description from Wilfred, thanks!

Meanwhile, I'm thinking about adding a new section "Meetup" under
"Community" on our website and also adding a section on our homepage for
the next event.

Do we have a process that can be shared to update our website?

Thanks,
Chenya

On Fri, Oct 22, 2021 at 11:42 AM Weiwei Yang  wrote:

> ACK'd, sounds great.
> We need to have a sharable message to adv this. @Wilfred Spiegelenburg
>  , could you pls share a short description of the
> session so we can put that in a message + planedDate + howToJoin and start
> to spread?
>
> On Fri, Oct 22, 2021 at 7:17 AM Chenya Zhang 
> wrote:
>
> > Wonderful, thanks Sunil and Chaoran for the input!
> >
> > Our first speaker will be Wilfred sharing about features in the latest
> > release, Gang scheduling, bin packing, node sorting improvement, etc.
> >
> > We will post an event from YuniKorn website, use LinkedIn meetup & posts
> to
> > attract more attendees, and YouTube for a live broadcast.
> >
> > If everyone agrees, we will finalize our 1st external meetup this year on
> > Nov 18th 4:30 - 6:00pm PST.
> >
> > Look forward to more ideas from everyone, and let’s get ready & excited!
> >
> > Cheers,
> > Chenya
> >
> >
> > On Thu, Oct 21, 2021 at 11:57 PM Chaoran Yu 
> > wrote:
> >
> > > Thanks Sunil for the input. Then let's do Nov 18th for the first event.
> > > 4:30-6:00pm PST should be a good start. We can gauge interest and then
> > > change time to cater to multiple time zones for alternating
> occurrences.
> > >
> > >
> > > On Mon, Oct 18, 2021 at 7:42 AM Sunil Govindan 
> > wrote:
> > >
> > > > Thanks, Charon. Yes, I second this.
> > > > Monthly events could be organized from Linkedin also. Meetup is not
> > much
> > > > used, I think.
> > > >
> > > > Let's start with November 18th, as you suggested. And each
> alternative
> > > > month, we can do one on PST morning and then during the evening.
> > > > This will help to cover all time zones as we have folks from
> Budapest,
> > > > India, China, East Asia, and Australia.
> > > >
> > > > On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang <
> > > chenyazhangche...@gmail.com>
> > > > wrote:
> > > >
> > > > > Sure, that sounds great!
> > > > >
> > > > > If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st event,
> > how
> > > > > does this slot fit into your schedules?
> > > > >
> > > > > Besides speaker talks, we could also have panel or roundtable
> > > > discussions.
> > > > >
> > > > > To broadcast YuniKorn to more people, we could also find if there
> are
> > > > other
> > > > > highly popular meetups in the industry and do a joint talk or
> > > discussion.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Cheers,
> > > > > Chenya
> > > > >
> > > > > On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu <
> yuchaoran2...@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Great, that works too. Chenya, do you want to schedule such a
> > monthly
> > > > > > meeting starting November? The first one can be during the week
> > > before
> > > > > > Thanksgiving. Once we finalize the schedule, we can think about
> > > > speakers
> > > > > > and topics.
> > > > > >
> > > > > > On Thu, Oct 14, 2021 at 9:49 PM Weiwei Yang 
> > wrote:
> > > > > >
> > > > > >> I am not aware of that sort of sponsorship. We can at least
> setup
> > > > > virtual
> > > > > >> meetings via Zoom.
> > > > > >> A monthly recurring meeting might be a good start : )
> > > > > >>
> > > > > >> On Thu, Oct 14, 2021 at 9:27 PM Chaoran Yu <
> > yuchaoran2...@gmail.com
> > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > I second this proposal!
> > > > > >> >
> > > > > >> > Instead of a one-time event, we can do a recurring meetup
> > (monthly
> > > > or
> > > > > >> > bi-monthly) and invite YuniKorn developers and users to talk
> > about
> > > > > their
> > > > > >> > experience and insights. A recurring event is well suited for
> > > > > >> cultivating a
> > > > > >> > community. I took a look at Meetup.com. They charge a monthly
> > fee
> > > > for
> > > > > >> > organizing a meetup group (see attached). Does ASF have any
> > > programs
> > > > > >> that
> > > > > >> > can sponsor such an effort? Or we can explore other options as
> > > well.
> > > > > >> >
> > > > > >> > Chaoran
> > > > > >> >
> > > > > >> >
> > > > > >> > On Tue, Oct 12, 2021 at 6:22 PM Weiwei Yang 
> > > > wrote:
> > > > > >> >
> > > > > >> >> Hi Chenya
> > > > > >> >>
> > > > > >> >> Thanks. This is a great idea, definitely +1.
> > > > > >> >> A few suggestions:
> > > > > >> >>
> > > > > >> >>- We can call for volunteers for the 1st event
> > > > > >> >>- Once we have that decided, we need to spread this to a
> > wider
> > > > > >> group of
> > > > > >> >>audiences, via email, twitter, LinkedIn, or ASF, etc
> > > > > >> >>- We need to publish the agenda & schedule of the next
> > meeting
> > > > on
> > > > > >> our
> > > > > >> >>web-site
> > > > > >> >>- We need to log the event recording onto the

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Chenya Zhang 
Great to see that we are going to have a new 1.0.0 release!

I could help Chaoran and shadow this release. Would be interested in
becoming our next release manager but happy to take a fight when it comes.
:D

Will follow up on this thread for v1.0.0.

Best,
Chenya

On Fri, Oct 22, 2021 at 11:37 AM Weiwei Yang  wrote:

> Hi Craig
>
> I think officially supporting 3 major K8s versions should be enough, but we
> need to update to 1.19, 1.20, and 1.21.
> 1.18 is EoL per https://endoflife.date/kubernetes . If we continue our
> release cadence, most likely we can move 1 major release at a time and that
> aligns with the K8s releases.
>
> On Fri, Oct 22, 2021 at 9:29 AM Craig Condit 
> wrote:
>
> > Looking forward to 1.0 release as well, and thanks Chaoran for
> > volunteering to manage the release.
> >
> > Should we also update our supported version matrix to include 1.18, 1.19,
> > 1.20, and 1.21? Updating the e2e test matrix should be a one-line change,
> > and as part of the rebuild against 1.20, I verified that 1.21 is
> functional.
> >
> > Craig
> >
> > > On Oct 22, 2021, at 2:15 AM, Weiwei Yang  wrote:
> > >
> > > Sounds great, thank you Chaoran!
> > >
> > > On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu 
> > wrote:
> > >
> > >> Hey guys,
> > >>
> > >> I volunteer to be the release manager this time, if nobody else has
> > >> volunteered already.
> > >>
> > >> The proposed timeline sounds right to be. It will allow for ample time
> > for
> > >> stabilization and verification.
> > >>
> > >> Chaoran
> > >>
> > >>
> > >> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang  wrote:
> > >>
> > >>> Hi Wilfred
> > >>>
> > >>> Thanks. Sounds good to me.
> > >>> Does anyone want to be the release manager for 1.0? The apache way
> > >>> encourages more people to get involved in the release process.
> > >>>
> > >>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> > >>> wilfr...@apache.org>
> > >>> wrote:
> > >>>
> >  Hi,
> > 
> >  We have been making big steps since our last release. Some major
> > >> changes
> >  have gone in and some are almost ready. The changes include:
> >  - rest API updates
> >  - new node storage and sorting
> >  - upgrade to a later K8s version as a build dependency
> >  - scheduler interface change
> > 
> >  Work is ongoing on generating a new set of performance figures. This
> >  includes documenting how to run our performance tests so we can
> repeat
> > >>> them
> >  when we want to.
> > 
> >  Based on all this work I would like to propose a 1.0.0 release to be
> > >>> ready
> >  for a vote by the incubator PMC by the start of December 2021. This
> > >> will
> >  give us some time to get the last fixes in and stabilise the
> release.
> > A
> >  release for us is still a multistep project:
> >  - fork and prepare the release
> >  - vote in the project
> >  - vote in the incubator PMC
> >  Looking back at the last release cycles that means we should have a
> > >> build
> >  ready for voting by 22 November on the dev list. Which would mean
> that
> > >> we
> >  fork the release at the latest in the second week of November.
> > 
> >  Please let me know if the timeline is too ambitious or not ambitious
> >  enough.
> > 
> >  Wilfred
> > 
> > >>>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> > For additional commands, e-mail: dev-h...@yunikorn.apache.org
> >
> >
>

[GitHub] [incubator-yunikorn-release] kingamarton commented on pull request #48: [YUNIKORN-885] Set healtch check as liveness probe

2021-10-22 Thread GitBox 


kingamarton commented on pull request #48:
URL: 
https://github.com/apache/incubator-yunikorn-release/pull/48#issuecomment-949879790


   > Looks good, thanks. Before merging this, @kingamarton can you pls share 
how this was tested?
   
   @yangwwei I checked if after deployment the liveness probe is turned on (on 
k9s is visible), and also I added some log messages to the core to make sure 
that the api is called periodically.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: Broadcast YuniKorn to the Industry!

2021-10-22 Thread Weiwei Yang 
ACK'd, sounds great.
We need to have a sharable message to adv this. @Wilfred Spiegelenburg
 , could you pls share a short description of the
session so we can put that in a message + planedDate + howToJoin and start
to spread?

On Fri, Oct 22, 2021 at 7:17 AM Chenya Zhang 
wrote:

> Wonderful, thanks Sunil and Chaoran for the input!
>
> Our first speaker will be Wilfred sharing about features in the latest
> release, Gang scheduling, bin packing, node sorting improvement, etc.
>
> We will post an event from YuniKorn website, use LinkedIn meetup & posts to
> attract more attendees, and YouTube for a live broadcast.
>
> If everyone agrees, we will finalize our 1st external meetup this year on
> Nov 18th 4:30 - 6:00pm PST.
>
> Look forward to more ideas from everyone, and let’s get ready & excited!
>
> Cheers,
> Chenya
>
>
> On Thu, Oct 21, 2021 at 11:57 PM Chaoran Yu 
> wrote:
>
> > Thanks Sunil for the input. Then let's do Nov 18th for the first event.
> > 4:30-6:00pm PST should be a good start. We can gauge interest and then
> > change time to cater to multiple time zones for alternating occurrences.
> >
> >
> > On Mon, Oct 18, 2021 at 7:42 AM Sunil Govindan 
> wrote:
> >
> > > Thanks, Charon. Yes, I second this.
> > > Monthly events could be organized from Linkedin also. Meetup is not
> much
> > > used, I think.
> > >
> > > Let's start with November 18th, as you suggested. And each alternative
> > > month, we can do one on PST morning and then during the evening.
> > > This will help to cover all time zones as we have folks from Budapest,
> > > India, China, East Asia, and Australia.
> > >
> > > On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang <
> > chenyazhangche...@gmail.com>
> > > wrote:
> > >
> > > > Sure, that sounds great!
> > > >
> > > > If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st event,
> how
> > > > does this slot fit into your schedules?
> > > >
> > > > Besides speaker talks, we could also have panel or roundtable
> > > discussions.
> > > >
> > > > To broadcast YuniKorn to more people, we could also find if there are
> > > other
> > > > highly popular meetups in the industry and do a joint talk or
> > discussion.
> > > >
> > > > Thoughts?
> > > >
> > > > Cheers,
> > > > Chenya
> > > >
> > > > On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu  >
> > > > wrote:
> > > >
> > > > > Great, that works too. Chenya, do you want to schedule such a
> monthly
> > > > > meeting starting November? The first one can be during the week
> > before
> > > > > Thanksgiving. Once we finalize the schedule, we can think about
> > > speakers
> > > > > and topics.
> > > > >
> > > > > On Thu, Oct 14, 2021 at 9:49 PM Weiwei Yang 
> wrote:
> > > > >
> > > > >> I am not aware of that sort of sponsorship. We can at least setup
> > > > virtual
> > > > >> meetings via Zoom.
> > > > >> A monthly recurring meeting might be a good start : )
> > > > >>
> > > > >> On Thu, Oct 14, 2021 at 9:27 PM Chaoran Yu <
> yuchaoran2...@gmail.com
> > >
> > > > >> wrote:
> > > > >>
> > > > >> > I second this proposal!
> > > > >> >
> > > > >> > Instead of a one-time event, we can do a recurring meetup
> (monthly
> > > or
> > > > >> > bi-monthly) and invite YuniKorn developers and users to talk
> about
> > > > their
> > > > >> > experience and insights. A recurring event is well suited for
> > > > >> cultivating a
> > > > >> > community. I took a look at Meetup.com. They charge a monthly
> fee
> > > for
> > > > >> > organizing a meetup group (see attached). Does ASF have any
> > programs
> > > > >> that
> > > > >> > can sponsor such an effort? Or we can explore other options as
> > well.
> > > > >> >
> > > > >> > Chaoran
> > > > >> >
> > > > >> >
> > > > >> > On Tue, Oct 12, 2021 at 6:22 PM Weiwei Yang 
> > > wrote:
> > > > >> >
> > > > >> >> Hi Chenya
> > > > >> >>
> > > > >> >> Thanks. This is a great idea, definitely +1.
> > > > >> >> A few suggestions:
> > > > >> >>
> > > > >> >>- We can call for volunteers for the 1st event
> > > > >> >>- Once we have that decided, we need to spread this to a
> wider
> > > > >> group of
> > > > >> >>audiences, via email, twitter, LinkedIn, or ASF, etc
> > > > >> >>- We need to publish the agenda & schedule of the next
> meeting
> > > on
> > > > >> our
> > > > >> >>web-site
> > > > >> >>- We need to log the event recording onto the yunikorn
> youtube
> > > > >> channel
> > > > >> >>
> > > > >> >>- Can we create a website page to track all these events?
> > > > >> >>
> > > > >> >> Let's start with calling for speakers : )
> > > > >> >>
> > > > >> >> On Tue, Oct 12, 2021 at 5:57 PM Chenya Zhang <
> > > > >> chenyazhangche...@gmail.com
> > > > >> >> >
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >> > Hi YuniKorn devs,
> > > > >> >> >
> > > > >> >> > We have achieved a lot together in the past year on major
> > > releases
> > > > >> >> > including exciting new features, important bug fixes, and
> > > multiple
> > >

[GitHub] [incubator-yunikorn-release] yangwwei commented on pull request #48: [YUNIKORN-885] Set healtch check as liveness probe

2021-10-22 Thread GitBox 


yangwwei commented on pull request #48:
URL: 
https://github.com/apache/incubator-yunikorn-release/pull/48#issuecomment-949876374


   Looks good, thanks.
   Before merging this, @kingamarton can you pls share how this was tested?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Weiwei Yang 
Hi Craig

I think officially supporting 3 major K8s versions should be enough, but we
need to update to 1.19, 1.20, and 1.21.
1.18 is EoL per https://endoflife.date/kubernetes . If we continue our
release cadence, most likely we can move 1 major release at a time and that
aligns with the K8s releases.

On Fri, Oct 22, 2021 at 9:29 AM Craig Condit  wrote:

> Looking forward to 1.0 release as well, and thanks Chaoran for
> volunteering to manage the release.
>
> Should we also update our supported version matrix to include 1.18, 1.19,
> 1.20, and 1.21? Updating the e2e test matrix should be a one-line change,
> and as part of the rebuild against 1.20, I verified that 1.21 is functional.
>
> Craig
>
> > On Oct 22, 2021, at 2:15 AM, Weiwei Yang  wrote:
> >
> > Sounds great, thank you Chaoran!
> >
> > On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu 
> wrote:
> >
> >> Hey guys,
> >>
> >> I volunteer to be the release manager this time, if nobody else has
> >> volunteered already.
> >>
> >> The proposed timeline sounds right to be. It will allow for ample time
> for
> >> stabilization and verification.
> >>
> >> Chaoran
> >>
> >>
> >> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang  wrote:
> >>
> >>> Hi Wilfred
> >>>
> >>> Thanks. Sounds good to me.
> >>> Does anyone want to be the release manager for 1.0? The apache way
> >>> encourages more people to get involved in the release process.
> >>>
> >>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> >>> wilfr...@apache.org>
> >>> wrote:
> >>>
>  Hi,
> 
>  We have been making big steps since our last release. Some major
> >> changes
>  have gone in and some are almost ready. The changes include:
>  - rest API updates
>  - new node storage and sorting
>  - upgrade to a later K8s version as a build dependency
>  - scheduler interface change
> 
>  Work is ongoing on generating a new set of performance figures. This
>  includes documenting how to run our performance tests so we can repeat
> >>> them
>  when we want to.
> 
>  Based on all this work I would like to propose a 1.0.0 release to be
> >>> ready
>  for a vote by the incubator PMC by the start of December 2021. This
> >> will
>  give us some time to get the last fixes in and stabilise the release.
> A
>  release for us is still a multistep project:
>  - fork and prepare the release
>  - vote in the project
>  - vote in the incubator PMC
>  Looking back at the last release cycles that means we should have a
> >> build
>  ready for voting by 22 November on the dev list. Which would mean that
> >> we
>  fork the release at the latest in the second week of November.
> 
>  Please let me know if the timeline is too ambitious or not ambitious
>  enough.
> 
>  Wilfred
> 
> >>>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
> For additional commands, e-mail: dev-h...@yunikorn.apache.org
>
>

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Craig Condit 
Looking forward to 1.0 release as well, and thanks Chaoran for volunteering to 
manage the release.

Should we also update our supported version matrix to include 1.18, 1.19, 1.20, 
and 1.21? Updating the e2e test matrix should be a one-line change, and as part 
of the rebuild against 1.20, I verified that 1.21 is functional.

Craig

> On Oct 22, 2021, at 2:15 AM, Weiwei Yang  wrote:
> 
> Sounds great, thank you Chaoran!
> 
> On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu  wrote:
> 
>> Hey guys,
>> 
>> I volunteer to be the release manager this time, if nobody else has
>> volunteered already.
>> 
>> The proposed timeline sounds right to be. It will allow for ample time for
>> stabilization and verification.
>> 
>> Chaoran
>> 
>> 
>> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang  wrote:
>> 
>>> Hi Wilfred
>>> 
>>> Thanks. Sounds good to me.
>>> Does anyone want to be the release manager for 1.0? The apache way
>>> encourages more people to get involved in the release process.
>>> 
>>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
>>> wilfr...@apache.org>
>>> wrote:
>>> 
 Hi,
 
 We have been making big steps since our last release. Some major
>> changes
 have gone in and some are almost ready. The changes include:
 - rest API updates
 - new node storage and sorting
 - upgrade to a later K8s version as a build dependency
 - scheduler interface change
 
 Work is ongoing on generating a new set of performance figures. This
 includes documenting how to run our performance tests so we can repeat
>>> them
 when we want to.
 
 Based on all this work I would like to propose a 1.0.0 release to be
>>> ready
 for a vote by the incubator PMC by the start of December 2021. This
>> will
 give us some time to get the last fixes in and stabilise the release. A
 release for us is still a multistep project:
 - fork and prepare the release
 - vote in the project
 - vote in the incubator PMC
 Looking back at the last release cycles that means we should have a
>> build
 ready for voting by 22 November on the dev list. Which would mean that
>> we
 fork the release at the latest in the second week of November.
 
 Please let me know if the timeline is too ambitious or not ambitious
 enough.
 
 Wilfred
 
>>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-890) Update Yunikorn docs about e2e testing

2021-10-22 Thread Peter Bacsko (Jira) 
Peter Bacsko created YUNIKORN-890:
-

 Summary: Update Yunikorn docs about e2e testing
 Key: YUNIKORN-890
 URL: https://issues.apache.org/jira/browse/YUNIKORN-890
 Project: Apache YuniKorn
  Issue Type: Improvement
  Components: documentation
Reporter: Peter Bacsko
Assignee: Peter Bacsko


As discussed with [~wilfreds] offline, it would be beneficial to update the 
Yunikorn Developer Guide about the e2e tests.

For example, if someone modifies an external interface of Yunikorn, it's highly 
advisable to run those tests to make sure that they pass.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[GitHub] [incubator-yunikorn-release] kingamarton commented on a change in pull request #48: [YUNIKORN-885] Set healtch check as liveness probe

2021-10-22 Thread GitBox 


kingamarton commented on a change in pull request #48:
URL: 
https://github.com/apache/incubator-yunikorn-release/pull/48#discussion_r734630973



##
File path: helm-charts/yunikorn/templates/deployment.yaml
##
@@ -93,6 +93,12 @@ spec:
 exec:
   command: ["/bin/sh", "/admission_util.sh", "create"]
   {{ end }}
+  livenessProbe:

Review comment:
   I moved theem to the values.yaml filee, so during installation it can be 
changed. 
   I set the threashold to 1 instead of 3, to make sure that the restart is 
triggered if the scheduler is in a bad state. I don't think this is too 
aggressive. Is better to restart it, than keeping it running in a bad state and 
maybe causing some unpredicted issues. 




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: Broadcast YuniKorn to the Industry!

2021-10-22 Thread Chenya Zhang 
Wonderful, thanks Sunil and Chaoran for the input!

Our first speaker will be Wilfred sharing about features in the latest
release, Gang scheduling, bin packing, node sorting improvement, etc.

We will post an event from YuniKorn website, use LinkedIn meetup & posts to
attract more attendees, and YouTube for a live broadcast.

If everyone agrees, we will finalize our 1st external meetup this year on
Nov 18th 4:30 - 6:00pm PST.

Look forward to more ideas from everyone, and let’s get ready & excited!

Cheers,
Chenya


On Thu, Oct 21, 2021 at 11:57 PM Chaoran Yu  wrote:

> Thanks Sunil for the input. Then let's do Nov 18th for the first event.
> 4:30-6:00pm PST should be a good start. We can gauge interest and then
> change time to cater to multiple time zones for alternating occurrences.
>
>
> On Mon, Oct 18, 2021 at 7:42 AM Sunil Govindan  wrote:
>
> > Thanks, Charon. Yes, I second this.
> > Monthly events could be organized from Linkedin also. Meetup is not much
> > used, I think.
> >
> > Let's start with November 18th, as you suggested. And each alternative
> > month, we can do one on PST morning and then during the evening.
> > This will help to cover all time zones as we have folks from Budapest,
> > India, China, East Asia, and Australia.
> >
> > On Fri, Oct 15, 2021 at 8:02 AM Chenya Zhang <
> chenyazhangche...@gmail.com>
> > wrote:
> >
> > > Sure, that sounds great!
> > >
> > > If tentatively circle Nov 18th 4:30 - 6:00pm PST for our 1st event, how
> > > does this slot fit into your schedules?
> > >
> > > Besides speaker talks, we could also have panel or roundtable
> > discussions.
> > >
> > > To broadcast YuniKorn to more people, we could also find if there are
> > other
> > > highly popular meetups in the industry and do a joint talk or
> discussion.
> > >
> > > Thoughts?
> > >
> > > Cheers,
> > > Chenya
> > >
> > > On Thu, Oct 14, 2021 at 10:03 PM Chaoran Yu 
> > > wrote:
> > >
> > > > Great, that works too. Chenya, do you want to schedule such a monthly
> > > > meeting starting November? The first one can be during the week
> before
> > > > Thanksgiving. Once we finalize the schedule, we can think about
> > speakers
> > > > and topics.
> > > >
> > > > On Thu, Oct 14, 2021 at 9:49 PM Weiwei Yang  wrote:
> > > >
> > > >> I am not aware of that sort of sponsorship. We can at least setup
> > > virtual
> > > >> meetings via Zoom.
> > > >> A monthly recurring meeting might be a good start : )
> > > >>
> > > >> On Thu, Oct 14, 2021 at 9:27 PM Chaoran Yu  >
> > > >> wrote:
> > > >>
> > > >> > I second this proposal!
> > > >> >
> > > >> > Instead of a one-time event, we can do a recurring meetup (monthly
> > or
> > > >> > bi-monthly) and invite YuniKorn developers and users to talk about
> > > their
> > > >> > experience and insights. A recurring event is well suited for
> > > >> cultivating a
> > > >> > community. I took a look at Meetup.com. They charge a monthly fee
> > for
> > > >> > organizing a meetup group (see attached). Does ASF have any
> programs
> > > >> that
> > > >> > can sponsor such an effort? Or we can explore other options as
> well.
> > > >> >
> > > >> > Chaoran
> > > >> >
> > > >> >
> > > >> > On Tue, Oct 12, 2021 at 6:22 PM Weiwei Yang 
> > wrote:
> > > >> >
> > > >> >> Hi Chenya
> > > >> >>
> > > >> >> Thanks. This is a great idea, definitely +1.
> > > >> >> A few suggestions:
> > > >> >>
> > > >> >>- We can call for volunteers for the 1st event
> > > >> >>- Once we have that decided, we need to spread this to a wider
> > > >> group of
> > > >> >>audiences, via email, twitter, LinkedIn, or ASF, etc
> > > >> >>- We need to publish the agenda & schedule of the next meeting
> > on
> > > >> our
> > > >> >>web-site
> > > >> >>- We need to log the event recording onto the yunikorn youtube
> > > >> channel
> > > >> >>
> > > >> >>- Can we create a website page to track all these events?
> > > >> >>
> > > >> >> Let's start with calling for speakers : )
> > > >> >>
> > > >> >> On Tue, Oct 12, 2021 at 5:57 PM Chenya Zhang <
> > > >> chenyazhangche...@gmail.com
> > > >> >> >
> > > >> >> wrote:
> > > >> >>
> > > >> >> > Hi YuniKorn devs,
> > > >> >> >
> > > >> >> > We have achieved a lot together in the past year on major
> > releases
> > > >> >> > including exciting new features, important bug fixes, and
> > multiple
> > > >> >> > improvements!
> > > >> >> >
> > > >> >> > It could be a wonderful time for us to further broadcast
> YuniKorn
> > > to
> > > >> the
> > > >> >> > industry and welcome more people onboard.
> > > >> >> >
> > > >> >> > What could be some interesting topics and the best event time
> for
> > > >> you?
> > > >> >> >
> > > >> >> > Some starters here:
> > > >> >> > - Apache YuniKorn Gang Scheduling and Bin Packing?
> > > >> >> > - Spark on K8s Autoscaling and Cost Efficiency?
> > > >> >> > - Flink Stream Processing with YuniKorn?
> > > >> >> > - TensorFlow Model Training with YuniKorn?

[jira] [Resolved] (YUNIKORN-543) Document state diagram generation

2021-10-22 Thread Kinga Marton (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kinga Marton resolved YUNIKORN-543.
---
Fix Version/s: 1.0.0
   Resolution: Fixed

> Document state diagram generation
> -
>
> Key: YUNIKORN-543
> URL: https://issues.apache.org/jira/browse/YUNIKORN-543
> Project: Apache YuniKorn
>  Issue Type: Improvement
>Reporter: Kinga Marton
>Assignee: Craig Condit
>Priority: Trivial
>  Labels: newbie, pull-request-available
> Fix For: 1.0.0
>
>
> Extend the documentation about how to generate a state diagram. 
> Right now we the information only in a PR:
> bq.The looplab/fsm code allows generating a graphviz file via 
> {{fsm.Visualize(state-machine)}}. This file can be converted using the 
> {{dot}} tool or other online tools into a svg or png file."
> Also it would be nice to be able to generate it through a make command



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Resolved] (YUNIKORN-888) Add documentation for k8shim state diagrams

2021-10-22 Thread Kinga Marton (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kinga Marton resolved YUNIKORN-888.
---
Fix Version/s: 1.0.0
   Resolution: Fixed

> Add documentation for k8shim state diagrams
> ---
>
> Key: YUNIKORN-888
> URL: https://issues.apache.org/jira/browse/YUNIKORN-888
> Project: Apache YuniKorn
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Craig Condit
>Assignee: Craig Condit
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>
> YUNIKORN-543 and YUNIKORN-887 are adding automation to the generation of 
> graphs for our finite state machines. We should add these to the website 
> design docs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Weiwei Yang 
Sounds great, thank you Chaoran!

On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu  wrote:

> Hey guys,
>
> I volunteer to be the release manager this time, if nobody else has
> volunteered already.
>
> The proposed timeline sounds right to be. It will allow for ample time for
> stabilization and verification.
>
> Chaoran
>
>
> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang  wrote:
>
> > Hi Wilfred
> >
> > Thanks. Sounds good to me.
> > Does anyone want to be the release manager for 1.0? The apache way
> > encourages more people to get involved in the release process.
> >
> > On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg <
> > wilfr...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > We have been making big steps since our last release. Some major
> changes
> > > have gone in and some are almost ready. The changes include:
> > > - rest API updates
> > > - new node storage and sorting
> > > - upgrade to a later K8s version as a build dependency
> > > - scheduler interface change
> > >
> > > Work is ongoing on generating a new set of performance figures. This
> > > includes documenting how to run our performance tests so we can repeat
> > them
> > > when we want to.
> > >
> > > Based on all this work I would like to propose a 1.0.0 release to be
> > ready
> > > for a vote by the incubator PMC by the start of December 2021. This
> will
> > > give us some time to get the last fixes in and stabilise the release. A
> > > release for us is still a multistep project:
> > > - fork and prepare the release
> > > - vote in the project
> > > - vote in the incubator PMC
> > > Looking back at the last release cycles that means we should have a
> build
> > > ready for voting by 22 November on the dev list. Which would mean that
> we
> > > fork the release at the latest in the second week of November.
> > >
> > > Please let me know if the timeline is too ambitious or not ambitious
> > > enough.
> > >
> > > Wilfred
> > >
> >
>

Re: [DISCUSS] release v1.0.0 planning

2021-10-22 Thread Weiwei Yang 
Hi Wilfred

Thanks. Sounds good to me.
Does anyone want to be the release manager for 1.0? The apache way
encourages more people to get involved in the release process.

On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg 
wrote:

> Hi,
>
> We have been making big steps since our last release. Some major changes
> have gone in and some are almost ready. The changes include:
> - rest API updates
> - new node storage and sorting
> - upgrade to a later K8s version as a build dependency
> - scheduler interface change
>
> Work is ongoing on generating a new set of performance figures. This
> includes documenting how to run our performance tests so we can repeat them
> when we want to.
>
> Based on all this work I would like to propose a 1.0.0 release to be ready
> for a vote by the incubator PMC by the start of December 2021. This will
> give us some time to get the last fixes in and stabilise the release. A
> release for us is still a multistep project:
> - fork and prepare the release
> - vote in the project
> - vote in the incubator PMC
> Looking back at the last release cycles that means we should have a build
> ready for voting by 22 November on the dev list. Which would mean that we
> fork the release at the latest in the second week of November.
>
> Please let me know if the timeline is too ambitious or not ambitious
> enough.
>
> Wilfred
>