Re: [Dev] Are there build break notifications are not sent to any mailing list?

2014-07-27 Thread Shevan Goonetilleke
Thanks Maheshika.

@All - you should start getting build break notifications if there are any
failures after the Jenkins run. Please make sure that any failures are your
highest priority for the day and get them resolved ASAP. Please speak to
Maheshika if you think you are not getting notifications and get it
resolved.


On Fri, Jul 25, 2014 at 9:50 AM, Maheshika Goonetilleke 
wrote:

> Hi Shevan
>
> I added team members to the relevant build notifications. As discussed,
> shared repos are configured to trigger notifications to buil...@wso2.org.
>
>
> On Wed, Jul 23, 2014 at 11:42 AM, Shevan Goonetilleke 
> wrote:
>
>> Based on the discussion we had on the Infra thread we will use the
>> builder@ mail list for build failure notifications but need to make sure
>> that everyone subscribes to this list.
>>
>> @Maheshika, can we include the people from the relevant product teams in
>> the mails relates to a particular jenkins project? (in addition to
>> buil...@wso2.org)?
>>
>> A build failure notification should become highest priority for people
>> relevant to that product/component.
>>
>>
>> On Wed, Jul 23, 2014 at 10:52 AM, Sagara Gunathunga 
>> wrote:
>>
>>>
>>> Hi Maheshika,
>>>
>>> Any update on this ?
>>>
>>> Thanks !
>>>
>>>
>>> On Tue, Jul 22, 2014 at 2:43 PM, Afkham Azeez  wrote:
>>>
>>>> $subject?
>>>>
>>>> Why did all the build breaks go unnoticed for so long?
>>>>
>>>> --
>>>> *Afkham Azeez*
>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>> * <http://www.apache.org/>*
>>>> *email: **az...@wso2.com* 
>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>> *twitter: **http://twitter.com/afkham_azeez*
>>>> <http://twitter.com/afkham_azeez>
>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>>
>>>> *Lean . Enterprise . Middleware*
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>>> V.P Apache Web Services;http://ws.apache.org/
>>> Linkedin; http://www.linkedin.com/in/ssagara
>>> Blog ;  http://ssagara.blogspot.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Shevan Goonetilleke
>> Director of Engineering
>> WSO2, Inc.
>> lean.enterprise.middleware
>> m: +94777340680
>> w: http://wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
>
> *WSO2 Inc*
> *email   : mahesh...@wso2.com  *
> *mobile : +94 773 596707 <%2B94%20773%20596707>*
> *www: :http://wso2.com <http://wso2.com/> *lean . enterprise . middleware
>
>
>
>
>


-- 
Shevan Goonetilleke
Director of Engineering
WSO2, Inc.
lean.enterprise.middleware
m: +94777340680
w: http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Are there build break notifications are not sent to any mailing list?

2014-07-22 Thread Shevan Goonetilleke
Based on the discussion we had on the Infra thread we will use the builder@
mail list for build failure notifications but need to make sure that
everyone subscribes to this list.

@Maheshika, can we include the people from the relevant product teams in
the mails relates to a particular jenkins project? (in addition to
buil...@wso2.org)?

A build failure notification should become highest priority for people
relevant to that product/component.


On Wed, Jul 23, 2014 at 10:52 AM, Sagara Gunathunga  wrote:

>
> Hi Maheshika,
>
> Any update on this ?
>
> Thanks !
>
>
> On Tue, Jul 22, 2014 at 2:43 PM, Afkham Azeez  wrote:
>
>> $subject?
>>
>> Why did all the build breaks go unnoticed for so long?
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>*
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* <http://blog.afkham.org>
>> *twitter: **http://twitter.com/afkham_azeez*
>> <http://twitter.com/afkham_azeez>
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> <http://lk.linkedin.com/in/afkhamazeez>*
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Shevan Goonetilleke
Director of Engineering
WSO2, Inc.
lean.enterprise.middleware
m: +94777340680
w: http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Stabilise APIM features on GitHub

2014-06-10 Thread Shevan Goonetilleke
Thanks for the update Ruwan. Pls keep the Git Migration checklist updated
with progress.


On Tue, Jun 10, 2014 at 2:56 PM, Ruwan Yatawara  wrote:

> Hi All,
>
> I've been working on $subject since yesterday, and thought of dropping an
> update. We have already moved the APIM components/features and half way
> through the product (to the latest 1.7.0 revisions).
>
> We need to create a separate repo for "product-am" to store the product
> artifacts and as we move along, all the identity features will also need to
> be updated for a AM pack to be fully functional.
>
> In addition, I've also added the "ganalytics" component to the
> carbon-analytics section, and am in the process of including the "forum"
> components/features to carbon-apimgt.
>
> I shall continue updating this thread on the progress of this activity.
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://thoughts.ruwan-ace.com/
> www: :http://wso2.com
>



-- 
Shevan Goonetilleke
Director of Engineering
WSO2, Inc.
lean.enterprise.middleware
m: +94777340680
w: http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] Proposed code repository restructuring & move to GitHub

2014-01-20 Thread Shevan Goonetilleke
>>> the product itself. AppFactory components are a good example.
>>>>>>>>>
>>>>>>>>> Products will also have their own GitHub repos. We will have
>>>>>>>>> separate GitHub repos for platform integration tests. Products such 
>>>>>>>>> as API
>>>>>>>>> Manager may opt to have the API Management feature in the product 
>>>>>>>>> itself.
>>>>>>>>> We would have a separate P2-repo GitHub repo which would build & 
>>>>>>>>> deploy the
>>>>>>>>> compatible set of P2 features.
>>>>>>>>>
>>>>>>>>> We will have Bamboo plans at multiple levels; components,
>>>>>>>>> products, platform, p2-repo and so on.
>>>>>>>>>
>>>>>>>>> We will not change any package structures at this time. We would
>>>>>>>>> defer that to Carbon 5 (if necessary). We will get rid of the chunk 
>>>>>>>>> based
>>>>>>>>> release model. Continuous delivery is our ultimate aim & for that to
>>>>>>>>> happen, we have to release a compatible set of features. We are going 
>>>>>>>>> to
>>>>>>>>> rely heavily on automation, automated builds & deploys to Maven. The
>>>>>>>>> developers will do the majority of the QA (just like the Apache 
>>>>>>>>> Stratos
>>>>>>>>> team is doing now).
>>>>>>>>>
>>>>>>>>> We will use the Maven release plugin to create releases & upload
>>>>>>>>> them to the Maven repo.
>>>>>>>>>
>>>>>>>>> *Implications to WSO2 code developers*
>>>>>>>>> 1. Life becomes easier because you don't have to spend a lot of
>>>>>>>>> time building unrelated stuff
>>>>>>>>> 2. General development would happen in the main branch.
>>>>>>>>> 3. Close to a release, branches would be cut.
>>>>>>>>> 4. Once release branches are cut, fixes would be done in the main
>>>>>>>>> branch, and pull requests would be sent to the branch & merged in. 
>>>>>>>>> This
>>>>>>>>> will be easy because we no longer have the trunk & branch structure 
>>>>>>>>> being
>>>>>>>>> different.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *Implications to users*
>>>>>>>>> Users will not see any difference in the components & features
>>>>>>>>> because we are not changing packages or binary structure. In fact, we 
>>>>>>>>> would
>>>>>>>>> have a P2 repo with compatible features which all work together.
>>>>>>>>>
>>>>>>>>> Senaka, Isuruwan & Harshana have already started working on a PoC.
>>>>>>>>>
>>>>>>>>> Thoughts welcome. Those who were in these discussions, please add
>>>>>>>>> anything I may have missed.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Afkham Azeez*
>>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>>>> * <http://www.apache.org/>*
>>>>>>>>> *email: **az...@wso2.com* 
>>>>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>>>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>>>>>> *twitter: 
>>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>>>>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>>>>>>>
>>>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Architecture mailing list
>>>>>>>>> architect...@wso2.org
>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> *Eranda Sooriyabandara*Senior Software Engineer;
>>>>>>>> Integration Technologies Team;
>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>>  Lean . Enterprise . Middleware
>>>>>>>>
>>>>>>>> E-mail: eranda AT wso2.com
>>>>>>>> Mobile: +94 716 472 816
>>>>>>>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>>>>>>>> Blog: http://emsooriyabandara.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Afkham Azeez*
>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>> * <http://www.apache.org/>*
>>>>>>> *email: **az...@wso2.com* 
>>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>>>> *twitter: 
>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>>>>>
>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Senaka Fernando*
>>>>>> Senior Technical Lead; WSO2 Inc.; http://wso2.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> * Member; Apache Software Foundation; http://apache.org
>>>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P:
>>>>>> +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>>>>>
>>>>>>
>>>>>> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In:
>>>>>> http://linkedin.com/in/senakafernando
>>>>>> <http://linkedin.com/in/senakafernando>*
>>>>>> Lean . Enterprise . Middleware
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Jayasoma,
>>>>> Architect,
>>>>>
>>>>> WSO2, Inc. (http://wso2.com)
>>>>> email: same...@wso2.com
>>>>> blog: http://sameera.adahas.org
>>>>> twitter: https://twitter.com/sameerajayasoma
>>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>>>> Mobile: 0094776364456
>>>>>
>>>>>
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> S.Uthaiyashankar
>>>> VP Engineering
>>>> WSO2 Inc.
>>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>>
>>>> Phone: +94 714897591
>>>>
>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>*
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* <http://blog.afkham.org>
>> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> <http://lk.linkedin.com/in/afkhamazeez>*
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
>
>
> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando*
> Senior Technical Lead; WSO2 Inc.; http://wso2.com
>
>
>
> * Member; Apache Software Foundation; http://apache.org
> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1
> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>
>
> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In:
> http://linkedin.com/in/senakafernando
> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
>



-- 
Shevan Goonetilleke
Director of Engineering
WSO2, Inc.
lean.enterprise.middleware
m: +94777340680
w: http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev