You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Hugo Trippaers <hu...@trippaers.nl> on 2014/01/17 17:41:11 UTC
Revert "update packages list before getting jre 7"
Hey guys,
I just reverted commit fa6536152a17dfd03b6eb10b2a1e0868fc9e134c
The branch 4.3 is a release branch, not a playground. We are inches away from a release, this means that nothing goes into the branch without being expressly permitted by the release manager. This case is even worse as the change wasn’t even made in master, the leading branch.
Just a general reminder about the process.
1. Create a ticket for your bug (if its not a bug, its not going to be in 4.3 anyway)
2. Make your changes in master
3. Test them on master
4. Send mail to dev list to ask permission from the release manager to back port to 4.3 and include the test result
Please stick to this game plan, so we can have a speedy release of 4.3.
Cheers,
Hugo
Re: Revert "update packages list before getting jre 7"
Posted by Abhinandan Prateek <Ab...@citrix.com>.
Sure, good learning will follow the steps.
On 17/01/14 10:35 pm, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>Thanks Abhi,
>
>Can you raise the bug and apply them on master? Maybe it’s also good to
>write to the list which this upgrade is required. There is a thread on
>upgrading to java 7 that might be interesting to refer to.
>
>Cheers,
>
>Hugo
>
>
>On 17 jan. 2014, at 17:58, Abhinandan Prateek
><Ab...@citrix.com> wrote:
>
>> I have reverted another related one
>> fc2e7ec70a1cc48a10a168ec3df607b49a7bcdf6, that was updating the jre to
>> version 7.
>>
>> -abhi
>>
>> On 17/01/14 10:11 pm, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>>
>>> Hey guys,
>>>
>>> I just reverted commit fa6536152a17dfd03b6eb10b2a1e0868fc9e134c
>>>
>>> The branch 4.3 is a release branch, not a playground. We are inches
>>>away
>>> from a release, this means that nothing goes into the branch without
>>> being expressly permitted by the release manager. This case is even
>>>worse
>>> as the change wasn¹t even made in master, the leading branch.
>>>
>>> Just a general reminder about the process.
>>>
>>> 1. Create a ticket for your bug (if its not a bug, its not going to be
>>>in
>>> 4.3 anyway)
>>> 2. Make your changes in master
>>> 3. Test them on master
>>> 4. Send mail to dev list to ask permission from the release manager to
>>> back port to 4.3 and include the test result
>>>
>>> Please stick to this game plan, so we can have a speedy release of 4.3.
>>>
>>>
>>> Cheers,
>>>
>>> Hugo
>>
>
Re: Revert "update packages list before getting jre 7"
Posted by Hugo Trippaers <hu...@trippaers.nl>.
Thanks Abhi,
Can you raise the bug and apply them on master? Maybe it’s also good to write to the list which this upgrade is required. There is a thread on upgrading to java 7 that might be interesting to refer to.
Cheers,
Hugo
On 17 jan. 2014, at 17:58, Abhinandan Prateek <Ab...@citrix.com> wrote:
> I have reverted another related one
> fc2e7ec70a1cc48a10a168ec3df607b49a7bcdf6, that was updating the jre to
> version 7.
>
> -abhi
>
> On 17/01/14 10:11 pm, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>
>> Hey guys,
>>
>> I just reverted commit fa6536152a17dfd03b6eb10b2a1e0868fc9e134c
>>
>> The branch 4.3 is a release branch, not a playground. We are inches away
>> from a release, this means that nothing goes into the branch without
>> being expressly permitted by the release manager. This case is even worse
>> as the change wasn¹t even made in master, the leading branch.
>>
>> Just a general reminder about the process.
>>
>> 1. Create a ticket for your bug (if its not a bug, its not going to be in
>> 4.3 anyway)
>> 2. Make your changes in master
>> 3. Test them on master
>> 4. Send mail to dev list to ask permission from the release manager to
>> back port to 4.3 and include the test result
>>
>> Please stick to this game plan, so we can have a speedy release of 4.3.
>>
>>
>> Cheers,
>>
>> Hugo
>
Re: Revert "update packages list before getting jre 7"
Posted by Abhinandan Prateek <Ab...@citrix.com>.
I have reverted another related one
fc2e7ec70a1cc48a10a168ec3df607b49a7bcdf6, that was updating the jre to
version 7.
-abhi
On 17/01/14 10:11 pm, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>Hey guys,
>
>I just reverted commit fa6536152a17dfd03b6eb10b2a1e0868fc9e134c
>
>The branch 4.3 is a release branch, not a playground. We are inches away
>from a release, this means that nothing goes into the branch without
>being expressly permitted by the release manager. This case is even worse
>as the change wasn¹t even made in master, the leading branch.
>
>Just a general reminder about the process.
>
>1. Create a ticket for your bug (if its not a bug, its not going to be in
>4.3 anyway)
>2. Make your changes in master
>3. Test them on master
>4. Send mail to dev list to ask permission from the release manager to
>back port to 4.3 and include the test result
>
>Please stick to this game plan, so we can have a speedy release of 4.3.
>
>
>Cheers,
>
>Hugo