Re: Apache Continuum is now an Apache top level project

[Napoleon Esmundo C. Ramirez]

Yay!  Congrats!

Cheers!
Nap

On Thu, Feb 21, 2008 at 9:07 AM, Maria Odea Ching [EMAIL PROTECTED] wrote:

 Yay! Congrats everyone! :-)

 -Deng

 On Thu, Feb 21, 2008 at 4:15 AM, Brett Porter [EMAIL PROTECTED] wrote:

  Hi all,
 
  Congratulations - the board passed the resolution we submitted.
 
  We'll have some work to do to get set up over the next month, but
  other than that it's business as usual. Certainly shouldn't interrupt
  the planning for the next release :)
 
  Cheers,
  Brett
 
  --
  Brett Porter
  [EMAIL PROTECTED]
  http://blogs.exist.com/bporter/
 
 

Re: [Discussion] Continuum 2.0 Roadmap

[Napoleon Esmundo C. Ramirez]

Just some thoughts,

I strongly agree to the proposed technology changes, particularly in the
database, as it will definitely improve the storage performance.  In line
with the objectives to make Continuum a slick CI server, I think the design
changes is a good move as well.  In my opinion, having plugins will provide
a platform for flexibility and a workflow-type of approach in managing the
builds.

My proposed features would be the following:
1.  Aside from the improvement in the UI, I think a visual representation of
statistics would be nice.  Graphs of the success rates, charts of project
health, etc.  I think Bamboo has it as telemetry.
2.  Distributed builds, this has been started before but it was never used.
I think this would be a strong point in using Continuum if it were
available.  Hudson has it, iirc.  I think implementing it as a plugin would
provide more control to it.

Again, just my thoughts.

Cheers!
Nap

On Feb 6, 2008 8:12 AM, Carlos Sanchez [EMAIL PROTECTED] wrote:

 Some comments

 Database vs xml: definitely database. Throwing away the db access api
 (JDO/JPA/...) now that it's already there doesnt make much sense.
 Maybe there are implementations that use xml for storage and that's
 where you'd need to look if you want file storage

 Spring vs Guice vs Plexus: Spring for sure. Big community, lots of
 users, documentation, support,... Specially if you want to add JMX
 support (can be done really easily just with annotations using
 reflection), and thinking in OSGi in the future I'm sure it will be
 really easy to integrate Spring and OSGi if it is not already. I'd
 start softly, just migrating thing that would require adding features
 to plexus, and move from there.

 I agree with Brett on having 1.2, 1.3,... it's good to have a list of
 what you want to do for 2.0 but as it gets done it should be released
 in minor versions.

 On Jan 29, 2008 2:34 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote:
  Hi
 
  I started a document [1] with my ideas about Continuum 2.
  As you can see in this doc, I want to add lot of things in the next
 version.
 
  Feel free to comment on it.
 
 
  [1]
 
 http://docs.codehaus.org/display/CONTINUUM/Continuum+2.0+Design+Discussion
 
  Emmanuel
 



 --
 I could give you my word as a Spaniard.
 No good. I've known too many Spaniards.
 -- The Princess Bride

Re: [vote] Request Graduation to a TLP

[Napoleon Esmundo C. Ramirez]

+1

On Feb 6, 2008 10:06 AM, Henry Isidro [EMAIL PROTECTED] wrote:

 This is great news +1

 On Feb 6, 2008 10:00 AM, Maria Odea Ching [EMAIL PROTECTED] wrote:
  +1
 
  -Deng
 
  On Feb 6, 2008 7:06 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote:
 
 
   Hi,
  
   Below is the current proposal for the Continuum TLP.
   Please vote on whether to make this proposal a formal request to the
 Maven
   PMC to apply for graduation.
  
   [ ] +1
   [ ] 0
   [ ] -1
  
   Cheers,
   Emmanuel
  
  
   Establish the Apache Continuum Project
  
   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the Foundation's
   purpose to establish a Project Management Committee charged with
   the creation and maintenance of open-source software related to
   the domain of continuous integration.
  
   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Continuum PMC, be and
   hereby is established pursuant to Bylaws of the Foundation; and
   be it further
  
   RESOLVED, that the Apache Continuum PMC be and hereby is
   responsible for the creation and maintenance of software related
   to the domain of continuous integration based on software licensed
   to the Foundation; and be it further
  
   RESOLVED, that the office of Vice President, Apache Continuum be
   and hereby is created, the person holding such office to serve
   at the direction of the Board of Directors as the chair of the
   Apache Continuum PMC, and to have primary responsibility for
   management of the projects within the scope of responsibility of
   the Apache Continuum PMC; and be it further
  
   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Continuum PMC:
  
   - Maria Odea Ching ([EMAIL PROTECTED])
   - Joakim Erdfelt ([EMAIL PROTECTED])
   - Olivier Lamy ([EMAIL PROTECTED])
   - Trygve Laugstol ([EMAIL PROTECTED])
   - Jesse McConnell ([EMAIL PROTECTED])
   - Brett Porter ([EMAIL PROTECTED])
   - Edwin Punzalan ([EMAIL PROTECTED])
   - Carlos Sanchez ([EMAIL PROTECTED])
   - Wendy Smoak ([EMAIL PROTECTED])
   - Rahul Thakur ([EMAIL PROTECTED])
   - Emmanuel Venisse ([EMAIL PROTECTED])
   - Kenney Westerhof ([EMAIL PROTECTED])
   - Andrew Williams ([EMAIL PROTECTED])
  
  
   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Emmanuel Venisse be
   appointed to the office of Vice President, Apache Continuum, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until death,
   resignation, retirement, removal or disqualification, or until a
   successor is appointed; and be it further
  
   RESOLVED, that the initial Apache Continuum PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Continuum Project; and be it further
  
   RESOLVED, that the initial Apache Continuum PMC be and hereby is
   tasked with the migration and rationalization of the Apache
   Maven PMC Continuum subproject; and be it further
  
   RESOLVED, that all responsibility pertaining to the Maven Continuum
   sub-project and encumbered upon the Apache Maven PMC
   are hereafter discharged.