Re: release button in project group page.
I think this is because the release plugin is being called at the parent pom once to also release all its modules whereas builds are being called at each project in the project group. On Sun, Mar 2, 2008 at 3:23 AM, Benoit Decherf [EMAIL PROTECTED] wrote: Hi, The release button of the project group page only works if all projects in the group have the same parent and the parent is in the group. Why doesn't it make a release of all projects in the group ? I think that it should work as the build all projects button. Benoit.
Re: Apache Continuum is now an Apache top level project
\o/ On Wed, Feb 20, 2008 at 12:15 PM, 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: [vote] Request Graduation to a TLP
Definitely, +1 Congratulations! On Feb 5, 2008 3:06 PM, 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.
Re: [Discussion] Continuum 2.0 Roadmap
I can only agree on the pointers given in the wiki. However, I'd like to reiterate the low significance of database portability in a CI server. I think speed matters but not really portability. Andy seems to be willing to help solve the database problems Continuum is experiencing. Just my 2 cents, though. ^_^ 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
Re: further feedback on white site
I've updated the white site with brett's suggestions and a few of my suggested modifications... please don't hesitate to comment. ^_^ Brett Porter wrote: I was looking at the white site, and had some additional feedback: http://people.apache.org/~epunzalan/continuum-white-site/releaseFinish.html Here, It isn't appropriate to list multiple builds, as only one build was performed. However, there are actually a series of steps as part of this release - so maybe its better to list them out? Especially if one fails and terminates the process. ie: (/) check for modifications (/) modify poms (x) perform test build - show failure output. For the first one, you might see it fails and show the files that have modifications, etc. (this is unlikely on continuum, so is of less importance). http://people.apache.org/~epunzalan/continuum-white-site/releaseProject.html We need to sort out how perform works. Having to enter everything is a bit tedious if you've just done a prepare. To save DB trickery, how about this: we keep a list of prepared releases in memory and remove them when they are performed. That way this page could have a radio for Perform release prepared this session with a dropdown of those releases, and one for Perform release from previous SCM tag. Both go to the same screen, but the first prepopulates everything. Same feedback for release finish (here we probably just want the build output). Also think about having that build in progress page in the middle using webwork's action in a background. Worth adding that screen in the white site, and just have a link on there that says I'm impatient, check again now :) Overall, looking nice! - Brett
Re: Release Management for Maven/Continuum
I'll be updating the white-site... Please see my inline comments below Brett Porter wrote: Feedback: - I'd rather Release be equivalent to build now (ie, we might need an icon for it), so added to the right-hand tasks per project, and added to the individual project page as a button. - I don't think this should operate on a group. It doesn't necessarily equate to a multi-module project, so instead I'd just go project by project. If they hit the parent then they get to release a bunch at once, as is the case in maven Above is what we've talked about in IRC and its fine with me. Makes things simpler, too. - I like the summary page that lists out all the defaults, however instead of an edit link, how about making the whole thing a form with defaults that gets submitted? The summary page shows only a few of the release parameters. So the Edit link is there to direct the user to the more detailed release configuration page. But since we'll be releasing projects one at a time, I guess I can incorporate what you mean into the new white-site. - I don't think we should have checkboxes on which modules to release, as that doesn't really correspond to what we have now, and likewise the from parent checkbox wouldn't be relevant I get what you mean, so ok. - there will be more elements to configure - we should get them into the interface now I'll try to put them all in the next white-site - on prepare finished, it should look like the build result page. We are only building one thing if you agree with the above - likewise for perform - as Jason said, prep and perform should be separate. I'm not sure of the best way to do this - perhaps hitting the release button presents the following options: * prepare release from current code * perform release from (list of previously prepared releases that haven't been performed) * perform release from SCM tag ok, so this means continuum should remember prepared releases. Should there be a separate release working directory for this? Because a prepared release may get lost after a scheduled build. snip
