You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Will Stevens <wi...@gmail.com> on 2016/05/27 22:34:46 UTC
Master is frozen for the 4.9 release
Hey All,
I think I have done what I can do at this point. I am sorry if you have a
PR that you wanted to get in that didn't make it. I pushed my deadline for
the freeze a bit because I had a lot of PRs that were close and I was able
to get a bunch of them in.
I plan to wait about a week before I cut the first RC to give people a
chance to test master and get me the details of their testing. This will
reduce the number of RCs we will need to have in order to get this release
out the door.
Please start testing master and let me know if you run into any issues.
There are a couple periodic issues that show up in my CI environments, so I
will probably spend some time to see if I can get those sorted out before I
cut the first release.
I plan to create a Github PR that will never be merged where I can post CI
results against master for this release so we can troubleshoot anything we
find. This approach is mainly because my workflow with `upr` lets me post
results easily and include the logs for the run.
Cheers,
Will
Re: Master is frozen for the 4.9 release
Posted by Daan Hoogland <da...@gmail.com>.
reads like a plan, Will. :+1:
On Sat, May 28, 2016 at 12:34 AM, Will Stevens <wi...@gmail.com>
wrote:
> Hey All,
> I think I have done what I can do at this point. I am sorry if you have a
> PR that you wanted to get in that didn't make it. I pushed my deadline for
> the freeze a bit because I had a lot of PRs that were close and I was able
> to get a bunch of them in.
>
> I plan to wait about a week before I cut the first RC to give people a
> chance to test master and get me the details of their testing. This will
> reduce the number of RCs we will need to have in order to get this release
> out the door.
>
> Please start testing master and let me know if you run into any issues.
> There are a couple periodic issues that show up in my CI environments, so I
> will probably spend some time to see if I can get those sorted out before I
> cut the first release.
>
> I plan to create a Github PR that will never be merged where I can post CI
> results against master for this release so we can troubleshoot anything we
> find. This approach is mainly because my workflow with `upr` lets me post
> results easily and include the logs for the run.
>
> Cheers,
>
> Will
>
--
Daan
Re: Master is frozen for the 4.9 release
Posted by Daan Hoogland <da...@gmail.com>.
Will, I have tested a few PRs against 4.9 and see no strange stuff except
for a mail from Chiradeep [1]. I would mark this a blokker. I will look at
it today to see if we can simply solve this (by cnaming aptget.eu to
something like download.cloudstack.org?) and if I can do it in a day submit
the PR.
Did this pass the round table at ccc Montreal?
[1] http://markmail.org/message/25a627ahmwihzteb
On Mon, Jun 6, 2016 at 11:05 PM, Will Stevens <ws...@cloudops.com> wrote:
> Great, thanks for the feedback Mike.
>
> Has anyone else done testing yet?
>
> Thanks,
>
> Will
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Mon, Jun 6, 2016 at 5:04 PM, Tutkowski, Mike <Mike.Tutkowski@netapp.com
> >
> wrote:
>
> > Hi Will,
> >
> > I just wanted to send out a quick note that I have run a bunch of my
> > integration tests against 4.9 and they all came back successful.
> >
> > From my point of view, I'm ready for RC1.
> >
> > Thanks!
> > Mike
> > ________________________________________
> > From: Will Stevens <wi...@gmail.com>
> > Sent: Friday, May 27, 2016 4:34 PM
> > To: dev@cloudstack.apache.org
> > Subject: Master is frozen for the 4.9 release
> >
> > Hey All,
> > I think I have done what I can do at this point. I am sorry if you have
> a
> > PR that you wanted to get in that didn't make it. I pushed my deadline
> for
> > the freeze a bit because I had a lot of PRs that were close and I was
> able
> > to get a bunch of them in.
> >
> > I plan to wait about a week before I cut the first RC to give people a
> > chance to test master and get me the details of their testing. This will
> > reduce the number of RCs we will need to have in order to get this
> release
> > out the door.
> >
> > Please start testing master and let me know if you run into any issues.
> > There are a couple periodic issues that show up in my CI environments,
> so I
> > will probably spend some time to see if I can get those sorted out
> before I
> > cut the first release.
> >
> > I plan to create a Github PR that will never be merged where I can post
> CI
> > results against master for this release so we can troubleshoot anything
> we
> > find. This approach is mainly because my workflow with `upr` lets me
> post
> > results easily and include the logs for the run.
> >
> > Cheers,
> >
> > Will
> >
>
--
Daan
Re: Master is frozen for the 4.9 release
Posted by Will Stevens <ws...@cloudops.com>.
Great, thanks for the feedback Mike.
Has anyone else done testing yet?
Thanks,
Will
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Mon, Jun 6, 2016 at 5:04 PM, Tutkowski, Mike <Mi...@netapp.com>
wrote:
> Hi Will,
>
> I just wanted to send out a quick note that I have run a bunch of my
> integration tests against 4.9 and they all came back successful.
>
> From my point of view, I'm ready for RC1.
>
> Thanks!
> Mike
> ________________________________________
> From: Will Stevens <wi...@gmail.com>
> Sent: Friday, May 27, 2016 4:34 PM
> To: dev@cloudstack.apache.org
> Subject: Master is frozen for the 4.9 release
>
> Hey All,
> I think I have done what I can do at this point. I am sorry if you have a
> PR that you wanted to get in that didn't make it. I pushed my deadline for
> the freeze a bit because I had a lot of PRs that were close and I was able
> to get a bunch of them in.
>
> I plan to wait about a week before I cut the first RC to give people a
> chance to test master and get me the details of their testing. This will
> reduce the number of RCs we will need to have in order to get this release
> out the door.
>
> Please start testing master and let me know if you run into any issues.
> There are a couple periodic issues that show up in my CI environments, so I
> will probably spend some time to see if I can get those sorted out before I
> cut the first release.
>
> I plan to create a Github PR that will never be merged where I can post CI
> results against master for this release so we can troubleshoot anything we
> find. This approach is mainly because my workflow with `upr` lets me post
> results easily and include the logs for the run.
>
> Cheers,
>
> Will
>
Re: Master is frozen for the 4.9 release
Posted by "Tutkowski, Mike" <Mi...@netapp.com>.
Hi Will,
I just wanted to send out a quick note that I have run a bunch of my integration tests against 4.9 and they all came back successful.
From my point of view, I'm ready for RC1.
Thanks!
Mike
________________________________________
From: Will Stevens <wi...@gmail.com>
Sent: Friday, May 27, 2016 4:34 PM
To: dev@cloudstack.apache.org
Subject: Master is frozen for the 4.9 release
Hey All,
I think I have done what I can do at this point. I am sorry if you have a
PR that you wanted to get in that didn't make it. I pushed my deadline for
the freeze a bit because I had a lot of PRs that were close and I was able
to get a bunch of them in.
I plan to wait about a week before I cut the first RC to give people a
chance to test master and get me the details of their testing. This will
reduce the number of RCs we will need to have in order to get this release
out the door.
Please start testing master and let me know if you run into any issues.
There are a couple periodic issues that show up in my CI environments, so I
will probably spend some time to see if I can get those sorted out before I
cut the first release.
I plan to create a Github PR that will never be merged where I can post CI
results against master for this release so we can troubleshoot anything we
find. This approach is mainly because my workflow with `upr` lets me post
results easily and include the logs for the run.
Cheers,
Will
Re: Master is frozen for the 4.9 release
Posted by Wido den Hollander <wi...@widodh.nl>.
> Op 8 juni 2016 om 3:01 schreef Will Stevens <wi...@gmail.com>:
>
>
> Yes. I agree. I need to get some commitment from someone to test it though.
> I need to figure out how to test it once it gets in. Any takers for
> validating this works after it goes in?
We tested it as it's running in production. In the PR ( https://github.com/apache/cloudstack/pull/1547 ) you can see that Daan als did tests which came out positive.
A additional pair of eyes on this one would be great so that it makes it in to 4.9
Wido
> On Jun 7, 2016 8:54 PM, "ilya" <il...@gmail.com> wrote:
>
> Sounds like a bug fix to me.. Bug fixes should be allowed in my opinion.
>
> On 6/7/16 4:07 AM, Wido den Hollander wrote:
> >> Op 28 mei 2016 om 0:34 schreef Will Stevens <wi...@gmail.com>:
> >>
> >>
> >> Hey All,
> >> I think I have done what I can do at this point. I am sorry if you have
> a
> >> PR that you wanted to get in that didn't make it. I pushed my deadline
> for
> >> the freeze a bit because I had a lot of PRs that were close and I was
> able
> >> to get a bunch of them in.
> >>
> >> I plan to wait about a week before I cut the first RC to give people a
> >> chance to test master and get me the details of their testing. This will
> >> reduce the number of RCs we will need to have in order to get this
> release
> >> out the door.
> >>
> >> Please start testing master and let me know if you run into any issues.
> >> There are a couple periodic issues that show up in my CI environments,
> so I
> >> will probably spend some time to see if I can get those sorted out
> before I
> >> cut the first release.
> >>
> >> I plan to create a Github PR that will never be merged where I can post
> CI
> >> results against master for this release so we can troubleshoot anything
> we
> >> find. This approach is mainly because my workflow with `upr` lets me
> post
> >> results easily and include the logs for the run.
> >>
> >
> > I would like to get some attention for this PR:
> https://github.com/apache/cloudstack/pull/1547
> >
> > Currently in Basic Networking multiple ranges per VLAN/POD is broken, the
> VR doesn't take the additional IP addresses.
> >
> > That PR fixes that (and is running in production at us), but this has
> been broken since 4.7
> >
> > I would like 4.9 to have this fixed as it's a known issue right now. Can
> we do that?
> >
> > Wido
> >
> >> Cheers,
> >>
> >> Will
Re: Master is frozen for the 4.9 release
Posted by Will Stevens <wi...@gmail.com>.
Yes. I agree. I need to get some commitment from someone to test it though.
I need to figure out how to test it once it gets in. Any takers for
validating this works after it goes in?
On Jun 7, 2016 8:54 PM, "ilya" <il...@gmail.com> wrote:
Sounds like a bug fix to me.. Bug fixes should be allowed in my opinion.
On 6/7/16 4:07 AM, Wido den Hollander wrote:
>> Op 28 mei 2016 om 0:34 schreef Will Stevens <wi...@gmail.com>:
>>
>>
>> Hey All,
>> I think I have done what I can do at this point. I am sorry if you have
a
>> PR that you wanted to get in that didn't make it. I pushed my deadline
for
>> the freeze a bit because I had a lot of PRs that were close and I was
able
>> to get a bunch of them in.
>>
>> I plan to wait about a week before I cut the first RC to give people a
>> chance to test master and get me the details of their testing. This will
>> reduce the number of RCs we will need to have in order to get this
release
>> out the door.
>>
>> Please start testing master and let me know if you run into any issues.
>> There are a couple periodic issues that show up in my CI environments,
so I
>> will probably spend some time to see if I can get those sorted out
before I
>> cut the first release.
>>
>> I plan to create a Github PR that will never be merged where I can post
CI
>> results against master for this release so we can troubleshoot anything
we
>> find. This approach is mainly because my workflow with `upr` lets me
post
>> results easily and include the logs for the run.
>>
>
> I would like to get some attention for this PR:
https://github.com/apache/cloudstack/pull/1547
>
> Currently in Basic Networking multiple ranges per VLAN/POD is broken, the
VR doesn't take the additional IP addresses.
>
> That PR fixes that (and is running in production at us), but this has
been broken since 4.7
>
> I would like 4.9 to have this fixed as it's a known issue right now. Can
we do that?
>
> Wido
>
>> Cheers,
>>
>> Will
Re: Master is frozen for the 4.9 release
Posted by ilya <il...@gmail.com>.
Sounds like a bug fix to me.. Bug fixes should be allowed in my opinion.
On 6/7/16 4:07 AM, Wido den Hollander wrote:
>> Op 28 mei 2016 om 0:34 schreef Will Stevens <wi...@gmail.com>:
>>
>>
>> Hey All,
>> I think I have done what I can do at this point. I am sorry if you have a
>> PR that you wanted to get in that didn't make it. I pushed my deadline for
>> the freeze a bit because I had a lot of PRs that were close and I was able
>> to get a bunch of them in.
>>
>> I plan to wait about a week before I cut the first RC to give people a
>> chance to test master and get me the details of their testing. This will
>> reduce the number of RCs we will need to have in order to get this release
>> out the door.
>>
>> Please start testing master and let me know if you run into any issues.
>> There are a couple periodic issues that show up in my CI environments, so I
>> will probably spend some time to see if I can get those sorted out before I
>> cut the first release.
>>
>> I plan to create a Github PR that will never be merged where I can post CI
>> results against master for this release so we can troubleshoot anything we
>> find. This approach is mainly because my workflow with `upr` lets me post
>> results easily and include the logs for the run.
>>
>
> I would like to get some attention for this PR: https://github.com/apache/cloudstack/pull/1547
>
> Currently in Basic Networking multiple ranges per VLAN/POD is broken, the VR doesn't take the additional IP addresses.
>
> That PR fixes that (and is running in production at us), but this has been broken since 4.7
>
> I would like 4.9 to have this fixed as it's a known issue right now. Can we do that?
>
> Wido
>
>> Cheers,
>>
>> Will
Re: Master is frozen for the 4.9 release
Posted by Wido den Hollander <wi...@widodh.nl>.
> Op 28 mei 2016 om 0:34 schreef Will Stevens <wi...@gmail.com>:
>
>
> Hey All,
> I think I have done what I can do at this point. I am sorry if you have a
> PR that you wanted to get in that didn't make it. I pushed my deadline for
> the freeze a bit because I had a lot of PRs that were close and I was able
> to get a bunch of them in.
>
> I plan to wait about a week before I cut the first RC to give people a
> chance to test master and get me the details of their testing. This will
> reduce the number of RCs we will need to have in order to get this release
> out the door.
>
> Please start testing master and let me know if you run into any issues.
> There are a couple periodic issues that show up in my CI environments, so I
> will probably spend some time to see if I can get those sorted out before I
> cut the first release.
>
> I plan to create a Github PR that will never be merged where I can post CI
> results against master for this release so we can troubleshoot anything we
> find. This approach is mainly because my workflow with `upr` lets me post
> results easily and include the logs for the run.
>
I would like to get some attention for this PR: https://github.com/apache/cloudstack/pull/1547
Currently in Basic Networking multiple ranges per VLAN/POD is broken, the VR doesn't take the additional IP addresses.
That PR fixes that (and is running in production at us), but this has been broken since 4.7
I would like 4.9 to have this fixed as it's a known issue right now. Can we do that?
Wido
> Cheers,
>
> Will