Hi Everyone,

Now that all recent commits happened over the past few days have been
cherry-picked, tagging and go mod dependency changes would happen over the
next couple of hours. Please don't commit any more changes into branch 1.2.

Thanks,
Mani

On Thu, Jan 19, 2023 at 9:15 PM Manikandan R <[email protected]> wrote:

> Hi Everyone,
>
> Update:
>
> I've moved some jiras to the next release, and put in comments on some
> jiras. So, please take a look at the jiras you have assigned and let me
> know what you think.
>
> I've created branches in all 4 repos as well.
>
> Thanks,
> Mani
>
> On Mon, Jan 16, 2023 at 7:51 PM Manikandan R <[email protected]> wrote:
>
>> Hi Everyone,
>>
>> I would like to start the discussion for Release 1.2.0.
>>
>> Planned major features:
>>
>> YUNIKORN-984 <https://issues.apache.org/jira/browse/YUNIKORN-984>
>> [Umbrella] User quota tracking
>> YUNIKORN-1196 <https://issues.apache.org/jira/browse/YUNIKORN-1196>
>> Upgrade K8s build dependency Y
>> YUNIKORN-1275 <https://issues.apache.org/jira/browse/YUNIKORN-1275>
>> Support arbitrary resources in namespace annotation
>> YUNIKORN-1306 <https://issues.apache.org/jira/browse/YUNIKORN-1306>
>> [Umbrella] Enhanced user and group handling
>> YUNIKORN-1 <https://issues.apache.org/jira/browse/YUNIKORN-1> Support
>> app/task priority aware scheduling
>>
>> In addition, minor enhancements and bug fixes has been covered as part of
>> this release.
>>
>> There are some open items with target version 1.2.0:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20YUNIKORN%20AND%20%22Target%20Version%22%20%3D%201.2.
>> 0%20ORDER%20BY%20status%20ASC
>>
>> Please have a look at this list and decide whether it's feasible to
>> complete them before code freeze. If not, then retarget the tickets
>> accordingly.
>>
>> Branching should be done before 20th Jan.
>>
>> Code freeze date:  25th Jan
>> RC release date: 1st Feb
>>
>> Based on the voting process, we can tentatively plan for release Yunikorn
>> 1.2.0 around 1st week of February.
>>
>> Please share your thoughts.
>>
>> Thanks,
>> Mani
>>
>

Reply via email to