You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Daan Hoogland <da...@gmail.com> on 2020/11/17 18:48:30 UTC
[DISCUSS][RELEASE] 4.15 merges and milestone
Devs, we have 11 open PRs in milestone 4.15 and 2 in 4.14.1. Not all of
them are urgent (lots of severity:minor actually) and some are
enhancements. Can we agree to move all of those to 4.14.2, 4.15.1 or 4.16?
if not please give them some love urgently. We are slacking traditionally
and personally I'd like us to break with that tradition sooner rather than
later. As far as I can see we have a good set of functionality to support
for the next 18 months.
I had some off-line discussion with our RM and want to propose that we cut
an RC start of the weekend. I'll ping people on PRs as well, but want to
open this for any concern with the content of the release we might have. So
any issue that might be wrongly labelled, bring it up here please and be
quick about it.
hope you all agree,
--
Daan
Re: [DISCUSS][RELEASE] 4.15 merges and milestone
Posted by Gabriel Bräscher <ga...@gmail.com>.
That's awesome!
Things are looking good for a RC1. Do we have any due time for it?
Em qui., 3 de dez. de 2020 às 11:14, Daan Hoogland <da...@gmail.com>
escreveu:
> Hello again,
>
> I have just merged the last critical item for 4.14 and 4.15. All other PRs
> are (or should be) moved to future milestones.
> I think we are ready for releases. thoughts anyone?
>
> On Mon, Nov 23, 2020 at 2:45 PM Daan Hoogland <da...@gmail.com>
> wrote:
>
> > as of now there are one PR marked as critical for 4.14.1 and one for
> 4.15.
> > I propose moving the rest to future milestones 4.14.2, 4.15.1 or 4.16
> > depending on whether these are bugs or enhancements. This is about the
> > final call on Blockers and critical issues!
> >
> > any thoughts anybody?
> >
> >
> > On Tue, Nov 17, 2020 at 7:48 PM Daan Hoogland <da...@gmail.com>
> > wrote:
> >
> >> Devs, we have 11 open PRs in milestone 4.15 and 2 in 4.14.1. Not all of
> >> them are urgent (lots of severity:minor actually) and some are
> >> enhancements. Can we agree to move all of those to 4.14.2, 4.15.1 or
> 4.16?
> >> if not please give them some love urgently. We are slacking
> traditionally
> >> and personally I'd like us to break with that tradition sooner rather
> than
> >> later. As far as I can see we have a good set of functionality to
> support
> >> for the next 18 months.
> >> I had some off-line discussion with our RM and want to propose that we
> >> cut an RC start of the weekend. I'll ping people on PRs as well, but
> want
> >> to open this for any concern with the content of the release we might
> have.
> >> So any issue that might be wrongly labelled, bring it up here please
> and be
> >> quick about it.
> >>
> >> hope you all agree,
> >> --
> >> Daan
> >>
> >
> >
> > --
> > Daan
> >
>
>
> --
> Daan
>
Re: [DISCUSS][RELEASE] 4.15 merges and milestone
Posted by Daan Hoogland <da...@gmail.com>.
all, there are milestones for 4.13.2, 4.14.2 and 4.15.1. If you are not
prepared to champion a new issue being a BLOCKER use one of those future
milestones please.
I am trying to get closure for the current discussions. The last critical
is about to get merged. The only discussion left is about template type
changes , please involve yourself.
I plan to take the rest of the release trajectum on me and want to create
an RC as soon as I can but it won't be today.
regards,
On Thu, Dec 3, 2020 at 3:38 PM Simon Weller <sw...@ena.com.invalid> wrote:
> Hi Daan,
>
> Thanks for all the hard work on this.
> I don't believe there are any other outstanding items from what I can see.
> Looks like we're ready!
>
> -Si
>
> ________________________________
> From: Daan Hoogland <da...@gmail.com>
> Sent: Thursday, December 3, 2020 8:14 AM
> To: dev <de...@cloudstack.apache.org>
> Subject: Re: [DISCUSS][RELEASE] 4.15 merges and milestone
>
> Hello again,
>
> I have just merged the last critical item for 4.14 and 4.15. All other PRs
> are (or should be) moved to future milestones.
> I think we are ready for releases. thoughts anyone?
>
> On Mon, Nov 23, 2020 at 2:45 PM Daan Hoogland <da...@gmail.com>
> wrote:
>
> > as of now there are one PR marked as critical for 4.14.1 and one for
> 4.15.
> > I propose moving the rest to future milestones 4.14.2, 4.15.1 or 4.16
> > depending on whether these are bugs or enhancements. This is about the
> > final call on Blockers and critical issues!
> >
> > any thoughts anybody?
> >
> >
> > On Tue, Nov 17, 2020 at 7:48 PM Daan Hoogland <da...@gmail.com>
> > wrote:
> >
> >> Devs, we have 11 open PRs in milestone 4.15 and 2 in 4.14.1. Not all of
> >> them are urgent (lots of severity:minor actually) and some are
> >> enhancements. Can we agree to move all of those to 4.14.2, 4.15.1 or
> 4.16?
> >> if not please give them some love urgently. We are slacking
> traditionally
> >> and personally I'd like us to break with that tradition sooner rather
> than
> >> later. As far as I can see we have a good set of functionality to
> support
> >> for the next 18 months.
> >> I had some off-line discussion with our RM and want to propose that we
> >> cut an RC start of the weekend. I'll ping people on PRs as well, but
> want
> >> to open this for any concern with the content of the release we might
> have.
> >> So any issue that might be wrongly labelled, bring it up here please
> and be
> >> quick about it.
> >>
> >> hope you all agree,
> >> --
> >> Daan
> >>
> >
> >
> > --
> > Daan
> >
>
>
> --
> Daan
>
--
Daan
Re: [DISCUSS][RELEASE] 4.15 merges and milestone
Posted by Simon Weller <sw...@ena.com.INVALID>.
Hi Daan,
Thanks for all the hard work on this.
I don't believe there are any other outstanding items from what I can see. Looks like we're ready!
-Si
________________________________
From: Daan Hoogland <da...@gmail.com>
Sent: Thursday, December 3, 2020 8:14 AM
To: dev <de...@cloudstack.apache.org>
Subject: Re: [DISCUSS][RELEASE] 4.15 merges and milestone
Hello again,
I have just merged the last critical item for 4.14 and 4.15. All other PRs
are (or should be) moved to future milestones.
I think we are ready for releases. thoughts anyone?
On Mon, Nov 23, 2020 at 2:45 PM Daan Hoogland <da...@gmail.com>
wrote:
> as of now there are one PR marked as critical for 4.14.1 and one for 4.15.
> I propose moving the rest to future milestones 4.14.2, 4.15.1 or 4.16
> depending on whether these are bugs or enhancements. This is about the
> final call on Blockers and critical issues!
>
> any thoughts anybody?
>
>
> On Tue, Nov 17, 2020 at 7:48 PM Daan Hoogland <da...@gmail.com>
> wrote:
>
>> Devs, we have 11 open PRs in milestone 4.15 and 2 in 4.14.1. Not all of
>> them are urgent (lots of severity:minor actually) and some are
>> enhancements. Can we agree to move all of those to 4.14.2, 4.15.1 or 4.16?
>> if not please give them some love urgently. We are slacking traditionally
>> and personally I'd like us to break with that tradition sooner rather than
>> later. As far as I can see we have a good set of functionality to support
>> for the next 18 months.
>> I had some off-line discussion with our RM and want to propose that we
>> cut an RC start of the weekend. I'll ping people on PRs as well, but want
>> to open this for any concern with the content of the release we might have.
>> So any issue that might be wrongly labelled, bring it up here please and be
>> quick about it.
>>
>> hope you all agree,
>> --
>> Daan
>>
>
>
> --
> Daan
>
--
Daan
Re: [DISCUSS][RELEASE] 4.15 merges and milestone
Posted by Daan Hoogland <da...@gmail.com>.
Hello again,
I have just merged the last critical item for 4.14 and 4.15. All other PRs
are (or should be) moved to future milestones.
I think we are ready for releases. thoughts anyone?
On Mon, Nov 23, 2020 at 2:45 PM Daan Hoogland <da...@gmail.com>
wrote:
> as of now there are one PR marked as critical for 4.14.1 and one for 4.15.
> I propose moving the rest to future milestones 4.14.2, 4.15.1 or 4.16
> depending on whether these are bugs or enhancements. This is about the
> final call on Blockers and critical issues!
>
> any thoughts anybody?
>
>
> On Tue, Nov 17, 2020 at 7:48 PM Daan Hoogland <da...@gmail.com>
> wrote:
>
>> Devs, we have 11 open PRs in milestone 4.15 and 2 in 4.14.1. Not all of
>> them are urgent (lots of severity:minor actually) and some are
>> enhancements. Can we agree to move all of those to 4.14.2, 4.15.1 or 4.16?
>> if not please give them some love urgently. We are slacking traditionally
>> and personally I'd like us to break with that tradition sooner rather than
>> later. As far as I can see we have a good set of functionality to support
>> for the next 18 months.
>> I had some off-line discussion with our RM and want to propose that we
>> cut an RC start of the weekend. I'll ping people on PRs as well, but want
>> to open this for any concern with the content of the release we might have.
>> So any issue that might be wrongly labelled, bring it up here please and be
>> quick about it.
>>
>> hope you all agree,
>> --
>> Daan
>>
>
>
> --
> Daan
>
--
Daan
Re: [DISCUSS][RELEASE] 4.15 merges and milestone
Posted by Daan Hoogland <da...@gmail.com>.
as of now there are one PR marked as critical for 4.14.1 and one for 4.15.
I propose moving the rest to future milestones 4.14.2, 4.15.1 or 4.16
depending on whether these are bugs or enhancements. This is about the
final call on Blockers and critical issues!
any thoughts anybody?
On Tue, Nov 17, 2020 at 7:48 PM Daan Hoogland <da...@gmail.com>
wrote:
> Devs, we have 11 open PRs in milestone 4.15 and 2 in 4.14.1. Not all of
> them are urgent (lots of severity:minor actually) and some are
> enhancements. Can we agree to move all of those to 4.14.2, 4.15.1 or 4.16?
> if not please give them some love urgently. We are slacking traditionally
> and personally I'd like us to break with that tradition sooner rather than
> later. As far as I can see we have a good set of functionality to support
> for the next 18 months.
> I had some off-line discussion with our RM and want to propose that we cut
> an RC start of the weekend. I'll ping people on PRs as well, but want to
> open this for any concern with the content of the release we might have. So
> any issue that might be wrongly labelled, bring it up here please and be
> quick about it.
>
> hope you all agree,
> --
> Daan
>
--
Daan