On 23/12/2006, at 12:24 AM, Jesse McConnell wrote:
the project.id and projectGroup.id will basically disappear from
continuum, reserved strictly for the underlying store. The store can
do whatever it wants with them.
Ok, so a project(Group)? will have:
id : int
key : String
name : String
...
Hi,
A few observations on these. Does anyone else have outstanding
"todos" in this area? Would like to gatehr them up and get them
resolved to make them useful.
1) these need to be run regularly to be really useful. They aren't
part of the main build ( a good idea, since it requires a UI
On 27/12/2006, at 2:08 PM, Brett Porter wrote:
Hi,
A few observations on these. Does anyone else have outstanding
"todos" in this area? Would like to gatehr them up and get them
resolved to make them useful.
1) these need to be run regularly to be really useful. They aren&#
see below
On 27/12/2006, at 3:09 PM, Brett Porter wrote:
On 27/12/2006, at 2:08 PM, Brett Porter wrote:
Hi,
A few observations on these. Does anyone else have outstanding
"todos" in this area? Would like to gatehr them up and get them
resolved to make them useful.
1) these
Yes, it's fetch groups. The store (pre-groups) took all this into
account, however the lack of central management for some of it caused
it to be pretty error prone. Those problems were related to
Continuum's design, not anything to do with the use of JPOX (and
something that'd be encountere
But I agree perhaps another temp location is a better candidate for
setting up container installation - may be 'target' directory under
top level root?
Rahul
- Original Message ----- From: "Brett Porter" <[EMAIL PROTECTED]>
To:
Sent: Friday, December 29, 200
Great - can the patch be used as a starting point?
On 03/01/2007, at 2:27 AM, Emmanuel Venisse wrote:
Brett Porter a écrit :
Hi Jesse,
I see you took this one a couple of months ago. It looks like a
good feature - is the patch a good enough start to use for now?
It was submitted by John
like ../mymodule
Emmanuel
Brett Porter a écrit :
Great - can the patch be used as a starting point?
On 03/01/2007, at 2:27 AM, Emmanuel Venisse wrote:
Brett Porter a écrit :
Hi Jesse,
I see you took this one a couple of months ago. It looks like a
good feature - is the patch a good enough sta
I saw it yesterday too. I actually had the problem before svn kicked
in, as far as I could tell. ie, retrieving POMs might be the problem.
On 06/01/2007, at 9:30 AM, Wendy Smoak wrote:
The ASF Subversion server limits connections to 10 per IP address, and
with several ASF projects loaded up,
improve performance when working
copy is up-to-date
Emmanuel
Brett Porter a écrit :
That doesn't actually matter for the client side speed boost. I'm
running 1.4.2 on continuum now.
- Brett
On 15/01/2007, at 2:21 PM, Brian E. Fox wrote:
The svn.apache.org server is a little old too:
Ok, fair enough. I've left it on, and made it use a different local
repository.
I'd say once we release Continuum 1.1 and are happy it is stable
enough to use, we can turn this off.
On 15/01/2007, at 11:02 PM, Trygve Laugstøl wrote:
Brett Porter wrote:
so... you're s
Any objections to me moving the configuration service out of the
database (and take some of the bits out of application.xml) and
putting them in the registry? Basically the same thing I've just done
for Archiva.
Docs on the registry are here: https://svn.codehaus.org/plexus/plexus-
sandbox
Actually, it's continuum-commits. However, I already did the -allow
thing in case she was subscribed under a different address.
On 20/02/2007, at 5:44 PM, Trygve Laugstøl wrote:
your commit emails are beeing moderated.
--
Trygve
Can you do
svn propedit svn:log -r509415 --revprop
And add that to the front?
- Brett
On 20/02/2007, at 8:38 PM, [EMAIL PROTECTED] wrote:
Hi Wendy,
This is for CONTINUUM-1147
Thanks,
Deng
On 2/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: oching
Date: Mon Feb 19 18:41:
Agreed. Someone needs to:
- properly mark up the model as it was for 1.0.3 release
- add methods to continuum-data-management to utilise that and then
make any necessary transformations (c-d-m will do the basic 1-to-1
conversions)
- probably write a little CLI to fire it off.
On 24/02/2007,
I agree with an alpha-1 labelled release.
I think someone will need to flush JIRA before cutting the release
(close things that are no longer relevant, or fixed, or duplicate).
- Brett
On 24/02/2007, at 8:35 AM, Jesse McConnell wrote:
I was talking to trygve a bit on irc and it dovetailed
Why is that the 'correct' method?
In Struts 2.0, doInput has been removed in favour of input (rather,
do* replaced by * in the general case).
- Brett
On 28/02/2007, at 11:41 PM, [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Wed Feb 28 07:41:36 2007
New Revision: 512813
URL: http://svn.a
We should be able support anything people can test and document.
The best tested will probably remain the plexus app server and/or
jetty, using derby.
- Brett
On 01/03/2007, at 12:41 AM, Hilco Wijbenga wrote:
On 2/28/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
users download the war fi
war or an ear is a
little more complicated (and therefor error prone). Also, such
manual edits
cannot be easily automated.
On 2/28/07, Brett Porter <[EMAIL PROTECTED]> wrote:
We should be able support anything people can test and document.
The best tested will probably remain the plexus
On 07/03/2007, at 9:52 AM, Jesse McConnell wrote:
Ok, well the little poll thread I made seemed to be strongly in favor
of getting things pulled together to start getting alpha releases out
of continuum. So with that in mind here is a list of a few things
that we need to get in order for an al
for a
> bit of feedback. I have yet to go through the 200 or so unfiled
> issues though so that might go up a bit, I'll do that now.
>
> thoughts?
> jesse
>
>
>
> On 3/7/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> > We don't need it the migratio
On 31/03/2007, at 6:50 AM, Emmanuel Venisse wrote:
I'm ok for a timestamped version, but we can release the release
manager too, without the plugin because it isn't ready and I want
the new Maven-SCM in it.
We're not set up to have snapshots in place permanently, so I don't
think we shou
This was one of the things I was going to try and have done before
alpha-1 - I just forgot.
Erik - the problem in upgrading is the changes in private tables
between versions of jpox that we hadn't given explicit names to. We'd
probably appreciate most help in future proofing our jpox use a
things up to remove
potential DB keyword conflicts
jesse
On 4/23/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Can I be sure at least that the DB model won't change as from
alpha-1?
If so I can maybe drop completely my database and recreate my
projects.
Thanks,
Stéphane
On 4/23/07,
Thanks Erik - I'll give that a try ASAP.
On 24/04/2007, at 7:35 AM, Erik Bengtson wrote:
Quoting Brett Porter <[EMAIL PROTECTED]>:
Erik - the problem in upgrading is the changes in private tables
between versions of jpox that we hadn't given explicit names to. We'd
pro
I'm trying to find the official release, and I can only find the file
in Jesse's home directory, and no announcement. Bit lost.
Can we do these?
- put in the main repo
- put in /dist/
- put on the website
- announce to lists / blogs
Cheers,
Brett
On 02/05/2007, at 4:10 PM, Jesse McConnell wrote:
there was discussion on this on another thread on this list...but I
will reiterate here that I feel uncomfortable shoving big war files
and these alpha-1 artifacts into the main repository. No one is
programming against these things in the main
So I think I'm going to do the migration tool.
- Brett
On 24/04/2007, at 7:35 AM, Erik Bengtson wrote:
Quoting Brett Porter <[EMAIL PROTECTED]>:
Erik - the problem in upgrading is the changes in private tables
between versions of jpox that we hadn't given explicit names to. We'd
p
Did you update this particular commit with svn pe --revprop -r535724
svn:log ?
On 09/05/2007, at 7:40 PM, Maria Odea Ching wrote:
Ok, I'll take note of that
Trygve Laugstøl wrote:
[EMAIL PROTECTED] wrote:
Author: oching
Date: Sun May 6 20:34:07 2007
New Revision: 535724
URL: http://svn.a
I don't think it's possible to put it anywhere other than the webapp
META-INF location at this point, without changing the way it's
configured.
- Brett
On 20/05/2007, at 11:24 PM, Wendy Smoak wrote:
In the FAQ [1] we say to uncomment an allowedScheme element in
apps/continuum/conf/applicat
a try - I'm honestly not sure.
- Brett
On 21/05/2007, at 6:59 AM, Wendy Smoak wrote:
On 5/20/07, Brett Porter <[EMAIL PROTECTED]> wrote:
I don't think it's possible to put it anywhere other than the webapp
META-INF location at this point, without changing the way it's
Anyone else have the problem of the 5 failing tests in continuum-core
on trunk? I only get them building from the top level, and it's been
a long standing problem.
testAddMavenTwoProjectSet
(org.apache.maven.continuum.DefaultContinuumTest)
testUpdateMavenTwoProject
(org.apache.maven.con
+1.
Gave it a quick fire up on the Mac.
- Brett
On 31/05/2007, at 6:38 AM, Jesse McConnell wrote:
I would like to get alpha-2 released to the community now.
Highlights are:
revamped xml-rpc support
converted to use rebranded plexus-security, aka redback
continuum maven plugin
many bug fixes
If my memory serves, we had decided we were ready to take this step
for the applications, but not Maven itself until the toolchain
support is final.
Any objections?
- Brett
On 05/06/2007, at 2:32 AM, [EMAIL PROTECTED] wrote:
Author: brett
Date: Mon Jun 4 09:32:12 2007
New Revision: 54417
On 13/06/2007, at 5:49 AM, Jason van Zyl wrote:
On 12 Jun 07, at 11:37 AM 12 Jun 07, [EMAIL PROTECTED] wrote:
Author: brett
Date: Tue Jun 12 11:37:19 2007
New Revision: 546588
URL: http://svn.apache.org/viewvc?view=rev&rev=546588
Log:
other aspect of CORE-3297 requires a patch to OID instead
I believe you can use that configuration, but like you I never have,
just pointing it directly at :8080 from httpd.
On 01/07/2007, at 3:11 PM, Wendy Smoak wrote:
Is the Jetty Configuration section on this page up to date?
http://maven.apache.org/continuum/guides/mini/guide-
configuration.
On 03/07/2007, at 5:54 AM, Emmanuel Venisse wrote:
Jesse McConnell a écrit :
Just to capture some talk on irc today...
I think the strategy moving forward is going to be get some of jira
cleaned up a la the recent maven jira push and continuum 1.1 is going
to get wrapped up a bit for the fir
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing
to the list of projects in a group? If so, how to handle the edge
cases where extra projects are added to or removed from a group aside
from the modules?
- how do you
On 11/07/2007, at 5:51 PM, Emmanuel Venisse wrote:
Brett Porter a écrit :
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing
to the list of projects in a group? If so, how to handle
the edge cases where
Hi,
I haven't looked beyond this issue - so there may be more - but I see
CONTINUUM-761 is a new feature scheduled for 1.1-beta-2.
Shouldn't this be in beta-1, or a future version?
- Brett
Hi folks,
I'm currently doing the rounds of all the people using Continuum on
VMBuild. The set up on there ballooned despite the box being
underpowered and the installation intended to be experimental, so was
never very well maintained.
We have a new box to move vmbuild to now and with th
So, is anyone interested?
On 11/07/2007, at 11:06 PM, Brett Porter wrote:
Hi folks,
I'm currently doing the rounds of all the people using Continuum on
VMBuild. The set up on there ballooned despite the box being
underpowered and the installation intended to be experimental, so
Hi,
I took a look through future for things that could be adjusted, and
came up with the following list. I didn't want to 'just do it', since
I'm not that close to the status of the project right now, so if
someone could review these it'd be much appreciated.
to close:
CONTINUUM-933 (ace
Anyone have any thoughts on these, or should I just go ahead and make
the changes?
(Sorry Emmanuel, I know you've been offline a bit recently :)
Cheers,
Brett
On 25/07/2007, at 5:13 PM, Emmanuel Venisse wrote:
Thanks Brett, I'll review them.
Emmanuel
Brett Porter a écrit :
Hi
On 01/08/2007, at 12:01 PM, Jesse McConnell wrote:
well, 1.1 is in beta now so ideally no more features, but maybe we
just call
this a bug fix for now..
yeah, I'm looking more for a small improvement than a revolution.
Avoiding schema changes and such. I really should have said something
Hi,
I've narrowed down the problem in upgrading from alpha-2 to beta-1 to
the following model change:
buildDefinition
1.1.0+
jpox.dependent="false">
BuildDefinition
The problem here is that Continuum has no idea how to
On 02/08/2007, at 7:46 AM, Emmanuel Venisse wrote:
For a project notifier, I think we can keep what we have actually,
but for a group notifier, we can send a single mail by project group.
The mail can be sent after the build of the latest project of the
group, I don't think it will be a probl
beta-2 issues by Aug 15.
Emmanuel
Brett Porter a écrit :
Hi,
How do people feel about planning betas to fit into: Aug 15, Aug
29, Sep 12, Sep 26? (for releases, votes are the monday before)
If so, is the current beta-2 list achievable by Aug 15? Looks like
it needs to be trimmed (and we also h
Hi all,
I already posted this to the users@ list, but I thought some folk
here might be more particularly interested in what Emmanuel had to
say when we talked recently: http://www.devzuz.org/?q=node/12.
Enjoy!
Cheers,
Brett
group notifier itself. Default is off for consistency with current
behaviour.
2) add a threshold of messages, particularly for errors - don't send
a message that is identical to one sent in the last X hours.
Cheers,
Brett
On 02/08/2007, at 6:26 PM, Emmanuel Venisse wrote:
Brett Port
is this just a bad env on the zone? might be a hint that the release
stuff could have a problem with certain environments too - worth
checking.
On 15/08/2007, at 3:05 AM, [EMAIL PROTECTED] wrote:
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-
log-20070815.030002.
+1
I gave it the basic run through - added a project, some profiles,
checked the licenses. All is well.
Very nice work everyone that's done stuff. It's starting to shape up
well!
- Brett
On 15/08/2007, at 12:56 AM, Emmanuel Venisse wrote:
Hi,
Continuum 1.1-beta-2 is ready for release
it for 1.1-beta-2 but I'll try for 1.1-beta-3
Emmanuel
Brett Porter a écrit :
Did I understand the summary to be the following to improvement
requests to file?
1) for group notifiers, don't send a mail if another build is
scheduled in the group already (instead, have the results add
I see too often project's getting stuck in "error" state, and it's
quite hard to diagnose what's wrong. They don't automatically
recover, and there is no build result for the actual error (so
clicking the icon takes you to the last successful one)
Anyone have any thoughts on how we can impr
I'm also seeing where there is a "real" error, like the SVN server
not being reachable, and it not trying to build ever again.
On 16/08/2007, at 1:40 PM, Brett Porter wrote:
I see too often project's getting stuck in "error" state, and it's
quite hard t
Thanks for the heads up. One issue is that it was using an old
instance that had stalled and meant to be shut down, the other is the
problem I reported on the list yesterday about the stuck error state.
- Brett
On 17/08/2007, at 6:35 AM, Joakim Erdfelt wrote:
Looks like the Cocoon and Tusca
continuum-dev.)
we only have one issues list, and it sets the reply-to (not JIRA).
--
Wendy
On 8/16/07, Brett Porter (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://jira.codehaus.org/browse/CONTINUUM-1234?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_
Here's what I did (this is a once off thing, though we really need to
make sure changes are backwards compatible and can handle missing
metadata in the future...)
- run data-management from 1.1-beta-1 to export the build database (I
had to build this from source)
- edit the exported builds.
re work, and it might be better to schedule
that for the future and fix it via (2) for 1.1.
what do others think?
- Brett
On 16/08/2007, at 1:46 PM, Brett Porter wrote:
I'm also seeing where there is a "real" error, like the SVN server
not being reachable, and it not trying t
Hi,
I know where in feature freeze, but I'd really like this and it has a
patch :)
Anyone think it is worth considering?
- Brett
We get this occasionally on vmbuild1: https://issues.apache.org/jira/
browse/INFRA-1326
I've not yet seen it on the zone. There's nothing in the logs to report.
Anyone seen this?
Cheers,
Brett
Anyone have any thoughts on this?
On 20/08/2007, at 10:59 AM, Brett Porter wrote:
I think I understand this problem more now.
the svn errors are a transient problem - it occurs before a build
takes place, but they are recorded as a built result. So when they
succeed again, no build occurs
On 29/08/2007, at 7:48 PM, Emmanuel Venisse wrote:
2) rebuild a project that was in error state before.
I think it's the best solution for now and won't be a lot of work.
agreed... can we sneak this into the 1.1 JIRA? :D
Only the first would also address the problem of having
difficul
more information on JIRA, see: http://www.atlassian.com/
software/jira
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
Now that Continuum is self-hosting, shall we turn off the hourly
build to save some cpu cycles?
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
the actions
before safely extracting pieces).
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
a worthy thing to have in a project.
I think everything is on track here - the first focus should be on
getting 1.1 out of course, but if we keep doing what we are doing
this totally makes sense.
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
elete project(s) last in the line
- change all the group buttons to be consistent: edit group, delete
group, release group, build group
- add release project(s) to the bottom
- put build project(s), build group and add project on lines of their
own
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
up on builds that are in error as empty: http://
maven.zones.apache.org/continuum/buildResult.action?
buildId=23999&projectId=272&projectGroupId=8
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
Hi,
Note this build: http://maven.zones.apache.org/continuum/
buildResults.action?projectId=272&projectGroupId=8
It is stuck in error - but I thought this was fixed in beta-3? Could
it be because it is an error on SCM update that it isn't detected as
fixed?
- Brett
--
Bre
ldController:default- Performing
action deploy-artifact
Note that the build result had said it was going for 8, 9, 10 minutes
as it kept going, but then after finishing completely it reported the
duration as "6 min 8 sec"
Any ideas?
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blo
even if the scm
update/checkout failed
no, if the build fails in checkout/update, the build def must be
hidden in the build result.
Emmanuel
--
Olivier
2007/9/23, Brett Porter <[EMAIL PROTECTED]>:
A couple of questions/issues on this new feature:
* is this stored with the build resul
It's empty too
On 24/09/2007, at 7:30 PM, Emmanuel Venisse wrote:
Brett,
you want to hide it when it is in progress or it is empty too?
If it is empty, it's a bug but I don't want to hide it when the
build is started.
Emmanuel
Brett Porter a écrit :
also when it is in pr
out the version to use for the continuum
release? We have two choices: 1.1-beta-4 or 1.1 final.
Personnally, I'd prefer 1.1 final. I tested all parts and all seems
to be ok, I just need to test more the ANT/shell part.
I'd like to prepare the Continuum release next week.
Emmanue
I didn't keep track of the changes after this - was it fixed?
On 24/09/2007, at 6:52 PM, Emmanuel Venisse wrote:
Hmm, I'll look at it to fix it definitively
Emmanuel
Brett Porter a écrit :
Hi,
Note this build: http://maven.zones.apache.org/continuum/
buildResults.action?pro
Sorry, missed this reply:
On 26/09/2007, at 4:55 PM, Trygve Laugstøl wrote:
Brett Porter wrote:
I'm seeing this on the zone:
INFO | jvm 1| 2007/09/24 03:29:17 | 2007-09-24 03:29:17,421
[pool-1-thread-1] INFO ContinuumBuildExecutor:maven2 - Exit code: 0
then for a long interva
well represented with the following training and
presentations:
* Brett Porter and Maria Odea Ching: A Development Ecosystem with
Apache Maven, Continuum and Archiva (includes OSSummit certification)
http://www.ossummit.com/2007/program/talk/24
* Brett Porter: Apache Maven Best Practices
g the bits to convert from other 1.1
alphas - but if the data management is working ok now then it might
be a good alternative.
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
user clickthrough.
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
But what if we only want to do this for one set of projects?
Shouldn't that be a mail notifier property?
On 05/11/2007, at 11:53 PM, Emmanuel Venisse wrote:
We can set includeBuildResult to false in application.xml
Emmanuel
Brett Porter a écrit :
Hi,
Got a request for vmbuild for a pr
np :)
http://jira.codehaus.org/browse/CONTINUUM-1545
On 06/11/2007, at 12:14 AM, Emmanuel Venisse wrote:
For the moment, it's a global option, but would be good to set it
in the notifier configuration.
Can you file an issue?
Emmanuel
Brett Porter a écrit :
But what if we only want
x27;ll try to prepare the release next Friday (Nov. 16)
Before to do the release, I'll try (I'm not sure yet) to add
pagination in the build results list page to save some memory when
users call it for projects with lot of build results.
Emmanuel
--
Brett Porter - [EMAIL P
007, at 11:57 AM, Brett Porter wrote:
per the thread on [EMAIL PROTECTED] - should Continuum have it's own [EMAIL PROTECTED]
list?
[ ] +1
[ ] 0
[ ] -1
Cheers,
Brett
So, what's next?
This seems generally in favour - now might be a good time to get
started on it?
From past experience the steps would be:
- poll the current maven committers to see who is interested in
participating in the TLP
- draft a resolution with those committers as the initial PMC
-
On 30/12/2007, at 2:55 AM, Wendy Smoak wrote:
I don't want to branch all of Continuum unless we're doing a 1.1.1
release, but we could branch just the continuum-docs module.
Thoughts?
The view I've started to take is that the documentation is best tied
to the release at the time. If there's
On 30/12/2007, at 2:45 AM, [EMAIL PROTECTED] wrote:
Author: wsmoak
Date: Sat Dec 29 07:45:18 2007
New Revision: 607431
URL: http://svn.apache.org/viewvc?rev=607431&view=rev
Log:
Update redirects to latest Maven version. Add redirect for
Continuum docs.
Modified:
maven/site/trunk/src/si
done :)
On 30/12/2007, at 12:48 PM, Wendy Smoak wrote:
On Dec 29, 2007 5:08 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
On 30/12/2007, at 2:45 AM, [EMAIL PROTECTED] wrote:
Modified:
maven/site/trunk/src/site/resources/.htaccess
Should this go in Continuum's site .htaccess?
ISTR Emmanuel going through these at one point, so I expect there are
not many that remain - you could look in the xwork.xml to see the ones
that don't use redirect though.
- Brett
On 03/01/2008, at 4:42 AM, Wendy Smoak wrote:
The 'Project Groups' page automatically refreshes itself every
nominations?
I have the current committers list as:
Maria Odea Ching
Joakim Erdfelt
Olivier Lamy
Trygve Laugstol
Jesse McConnell
Brett Porter
Edwin Punzalan
Carlos Sanchez
Wendy Smoak
Rahul Thakur
Emmanuel Venisse
Kenney Westerhof
Andrew Williams
Anyone on that list that doesn't feel they should
Thanks Rahul.
I appreciate the thought, however I decline the nomination at this
time :)
On 08/01/2008, at 5:00 AM, Rahul Thakur wrote:
And the nominations are.
(~opens the envelope~)
1) Brett Porter
, and
2) Jesse McConnell
Cheers :-)
Rahul
Brett Porter wrote:
of course
:00 AM, Brett Porter wrote:
So the poll for progressing seems in favour.
Before we continue to vote on a proposal to send to the board, we
need to decide on a description for the project, the initial PMC/
committers, and a chair.
I would like to nominate Emmanuel as the chair of the project
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])
On 06/02/2008, at 1:20 PM, Napoleon Esmundo C. Ramirez wrote:
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 th
Apache wiki? Or, I guess it will have to wait for
TLP vote.
Cheers,
Rahul
Brett Porter wrote:
This looks very exciting, and agree with most of the thread that
follows. I'm just going to reply in summary - most of my thoughts
are actually non-technical :)
Regarding databases: I don't
On 13/02/2008, at 4:04 PM, Wendy Smoak wrote:
On Feb 12, 2008 10:01 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
Ok, I've created two wiki's:
...
http://cwiki.apache.org/confluence/display/CONTINUUMDEV/Index
(exported to: http://cwiki.apache.org/CONTINUUMDEV/)
This on
6:04 AM, Rahul Thakur wrote:
If everyone is happy to keep the history till date on codehaus wiki,
I can help copy stuff across to Apache wiki :-)
Rahul
Brett Porter wrote:
We can create such a wiki any time - the challenge is converting
existing content. If someone is happy to lose histo
no, permissions changes are non-destructive :)
On 13/02/2008, at 6:33 PM, Rahul Thakur wrote:
+1 as long as editing it requires a login :-)
Should I hold off the migration from Codehaus?
Rahul
On Feb 13, 2008 6:32 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
On 13/02/2008, at 4
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
--
Bret
ee to comment on it.
[1]
http://docs.codehaus.org/display/CONTINUUM/Continuum+2.0+Design+Discussion
Emmanuel
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
hairs group
already.
Cheers,
Brett
On 21/02/2008, at 8:30 AM, Emmanuel Venisse wrote:
Cool, great news.
Thanks Brett (and others)
Emmanuel
On Feb 20, 2008 9:15 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi all,
Congratulations - the board passed the resolution we submitted.
We&#
101 - 200 of 519 matches
Mail list logo
