I was thinking of adding a page to the wiki entitled Developer Workflow,
this can contain the diagram that Jun Aoki started, plus our
guideline/expectations for release candidate branches.
For the release candidate, all Jiras must have a Fix-Version of 1.7.0;
whereas Jiras for the trunk branch
With Jun's help, we have a created a build for branch-1.7.0 on b.a.o.
https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-branch-1.7.0/
This build is currently disabled. Once we get the green signal from
Alejandro with regards to the completion of the branch creation for 1.7.0,
I'll enable
The release candidate branch-1.7.0 is ready.
git pull
git branch --remote
Thanks,
Alejandro Fernandez
On Fri, Oct 3, 2014 at 1:46 PM, Chandrasekhar Gopal cgo...@pivotal.io
wrote:
With Jun's help, we have a created a build for branch-1.7.0 on b.a.o.
Enabled the Jenkins Job on b.a.o for branch-1.7.0. Manually triggered
the first build.
https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-branch-1.7.0/1/consoleFull
I noticed that the following test failed for Ambari-Server. Looking to see
if this issue has already been reported.
This issue has already been reported by Jun.
https://issues.apache.org/jira/browse/AMBARI-7622
So we are good in terms of having consistent results for the builds off
trunk and branch-1.7.0.
On Fri, Oct 3, 2014 at 4:47 PM, Chandrasekhar Gopal cgo...@pivotal.io
wrote:
Enabled the Jenkins Job
Great. Thanks Chandra!
Yusaku
On Fri, Oct 3, 2014 at 4:47 PM, Chandrasekhar Gopal cgo...@pivotal.io
wrote:
Enabled the Jenkins Job on b.a.o for branch-1.7.0. Manually triggered
the first build.
https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-branch-1.7.0/1/consoleFull
I
Friendly reminder that we will make the Ambari 1.7.0 branch on Friday at 2
pm Pacific Time. After the cut-off, we will require all bug fixes to first
be committed to trunk, ensure that nothing breaks, and then integrate it
into the release branch.
All bug fixes meant for the release branch must
Alejandro,
Had a quick question with regards to the criteria/specifics for bug-fixes
making it to the 1.7.0 branch. Do we need to add a label (such as GA
Blocker) to the JIRA tickets? Or do they need to have a certain level of
Severity?
Thanks !
Chandra
On Thu, Oct 2, 2014 at 11:25 AM,
I propose using the severity field.
All Jiras with a severity of blocker or critical should make it into
1.7.0, and I will send periodic emails with the state of the release (#
blockers, # critical, # major, etc.)
It is up to the developers to contact me if they want to bring up the
discussion of
Is the definition of Blocker/Critical etc. standard - if not can you host
it in Ambari wiki.
Also, I assume the Fix Version/s should include 1.7.0.
This brings up another question -
What is the Fix Version for JIRAs that are not targeted for 1.7.0 - is it
empty or we have a version number for
+1 for setting up a 1.7.0 release build on builds.apache.org.
Yusaku
On Mon, Sep 29, 2014 at 8:12 PM, Judes Sarmiento jsarmie...@pivotal.io
wrote:
That will help a lot!
On Monday, September 29, 2014, Roman Shaposhnik ro...@shaposhnik.org
wrote:
On Mon, Sep 29, 2014 at 5:26 PM,
Alejandro,
Upon creation of the RC branch for the 1.7.0 release, I'd like to suggest
that we also create a release build for this branch on b.a.o.
I can create a JIRA and help with creation of the release builds.
Please let me know your thoughts.
Thanks,
Chandra
On Mon, Sep 29, 2014 at 1:35
On Mon, Sep 29, 2014 at 5:26 PM, Chandrasekhar Gopal cgo...@pivotal.io wrote:
Alejandro,
Upon creation of the RC branch for the 1.7.0 release, I'd like to suggest
that we also create a release build for this branch on b.a.o.
Huge +1 to that!
Thanks,
Roman.
That will help a lot!
On Monday, September 29, 2014, Roman Shaposhnik ro...@shaposhnik.org
wrote:
On Mon, Sep 29, 2014 at 5:26 PM, Chandrasekhar Gopal cgo...@pivotal.io
javascript:; wrote:
Alejandro,
Upon creation of the RC branch for the 1.7.0 release, I'd like to suggest
that we also
14 matches
Mail list logo
