Please find status update as of today.
1.) We have completed moving following projects into GitHub and Jenkins
server periodically deploy SNAPSHOT artifacts into Nexus snapshot repo too.
1. WSO2-Axiom
2. WSO2-Axis2
3. WSO2-WSS4J
4. Carbon4-Kernel
5. Carbon-deployment
6. Carbon-utils
2.) Next
Dear Saagara,
does it mean that from now the GitHub repos would be the master ?
(and the people can start forking and creating pull requests)
What's the status for WSO2 ESB (aka Apache Synapse) ?
Thank you in advance for your feedback.
Luca.
On 11 Feb 2014, at 13:07, Sagara Gunathunga
Sounds good :-)
Thanks for the feedback.
Luca.
On 11 Feb 2014, at 14:43, Sagara Gunathunga sag...@wso2.com wrote:
On Tue, Feb 11, 2014 at 7:15 PM, Luca Milanesio luca.milane...@gmail.com
wrote:
Dear Saagara,
does it mean that from now the GitHub repos would be the master ?
(and the
On Tue, Feb 11, 2014 at 7:15 PM, Luca Milanesio luca.milane...@gmail.comwrote:
Dear Saagara,
does it mean that from now the GitHub repos would be the master ?
(and the people can start forking and creating pull requests)
Hi Luca,
Yes now anyone can start forking and welcome to send pull
On Tue, Feb 11, 2014 at 7:15 PM, Luca Milanesio luca.milane...@gmail.comwrote:
Dear Saagara,
does it mean that from now the GitHub repos would be the master ?
(and the people can start forking and creating pull requests)
Yes, you would fork the dev repos, and then send pull requests, which
On Mon, Feb 3, 2014 at 10:18 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Mon, Feb 3, 2014 at 10:14 PM, Eranda Sooriyabandara era...@wso2.comwrote:
Hi Sagara,
I have committed the changed carbon4-kernel changed with the new SNAPSHOT
versions. I built it and it was a success for me.
On Tue, Feb 4, 2014 at 6:10 AM, Afkham Azeez az...@wso2.com wrote:
If Jenkins is simpler, I am +1 to move to Jenkins from Bamboo. Also, for
the thin slice to be considered complete, we need to test the team-wise
repo, and testing pull requests to main repo from team repo.
Some of the custom
We have completed moving following kernel dependencies into GitHub and
setup Jenkins jobs for each project so that each job run periodically and
push SNAPSHOT artifacts into Nexus snapshot repository. You can view
Jenkins dashboard from here [1] and Nexus snapshot repository from here[2]
with
Hi Sagara,
I have committed the changed carbon4-kernel changed with the new SNAPSHOT
versions. I built it and it was a success for me.
@Maheshika,
Shall we trigger a build and check the status?
thanks
Eranda
On Mon, Feb 3, 2014 at 10:07 PM, Sagara Gunathunga sag...@wso2.com wrote:
We have
Hi Sagara,
On Mon, Feb 3, 2014 at 10:07 PM, Sagara Gunathunga sag...@wso2.com wrote:
We have completed moving following kernel dependencies into GitHub and
setup Jenkins jobs for each project so that each job run periodically and
push SNAPSHOT artifacts into Nexus snapshot repository. You
On Mon, Feb 3, 2014 at 10:14 PM, Eranda Sooriyabandara era...@wso2.comwrote:
Hi Sagara,
I have committed the changed carbon4-kernel changed with the new SNAPSHOT
versions. I built it and it was a success for me.
Great, will check.
@Maheshika,
Shall we trigger a build and check the
If Jenkins is simpler, I am +1 to move to Jenkins from Bamboo. Also, for
the thin slice to be considered complete, we need to test the
team-wise repo, and
testing pull requests to main repo from team repo.
Azeez
On Mon, Feb 3, 2014 at 10:18 PM, Sagara Gunathunga sag...@wso2.com wrote:
On
12 matches
Mail list logo
