[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Bertrand Delacretaz updated COCOON-1663:
Comment: was deleted
Release 2.1.8
-
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
[
http://issues.apache.org/jira/browse/COCOON-1663?page=comments#action_12356092
]
Bertrand Delacretaz commented on COCOON-1663:
-
To mark an issue as blocking for the 2.1.8 release, use the links function of
the blocking issue.
Release 2.1.8
Le 27 oct. 05, à 16:42, Andrew Savory a écrit :
...-1 for tomorrow: just got bitten again by this bug:
http://issues.apache.org/jira/browse/COCOON-1594
I have created http://issues.apache.org/jira/browse/COCOON-1663 to list
issues which we consider blocking for the release, and added
Le 27 oct. 05, à 16:55, Vadim Gritsenko a écrit :
IIUC that's not the Jira way to do it... Am I right? Pier? :)
It would work, though ;-)
I'm open to other suggestions for sure, if people who know jira better
want to do it then go ahead, I won't mind!
The point is: managing these things in
Le 27 oct. 05, à 20:58, Pier Fumagalli a écrit :
...I still have to think slightly about how to do release management...
Yes, and thanks for setting this up in jira!
-Bertrand
Le 27 oct. 05, à 08:35, Carsten Ziegeler a écrit :
So please cast your votes for
[ ] Release tomorrow, 27th of October
[+1 ] Release next friday, 4th of November
Things are still happening re. testing and docs, so the release should
be a better one in a week.
-Bertrand
Le 25 oct. 05, à 01:29, Torsten Curdt a écrit :
...The javaflow OJB example gives a PersistenceBrokerException Used
ConnectionManager instance could not obtain a connection...
These database issues were fixed yesterday by Sylvain (thanks!), the
demos were all trying to run hsqldb on the same
Le 25 oct. 05, à 12:14, Pier Fumagalli a écrit :
On 25 Oct 2005, at 10:08, Jeroen Reijn wrote:
- CAPTCHA validation sample is does not make sense. There is no
string shown on the right.
http://cocoon.zones.apache.org/demos/21branch/samples/blocks/forms/
captcha/
Uh... That's a 500:
HTTP
[
http://issues.apache.org/jira/browse/COCOON-1661?page=comments#action_12355954
]
Bertrand Delacretaz commented on COCOON-1661:
-
It works for me at
http://cocoon.zones.apache.org/demos/21branch/samples/blocks/portal/portal
which runs
Le 25 oct. 05, à 10:52, Carsten Ziegeler a écrit :
...Can someone please have a look at this. It seems that the db is not
running. Could it be because
we have several Cocoon versions now running and both starting the
hsqldb?..
It's probably this, I didn't do anything special to have the
Le 25 oct. 05, à 10:33, Sylvain Wallez a écrit :
...I think that, along with pinging the Ajaxian guys (which I will
do), we should rewrite our home page to make more apparent Cocoon's
unique abilities in the changing world of webapp development
+1, and it would be good to make it easy to
Le 25 oct. 05, à 08:29, Reinhard Poetz a écrit :
We have 79 closed but unresolved issues in Jira. This is a problem as
they show up in all queries (eg the project page) and gives a wrong
picture of open issues.
Is there any faster possibility to change this but to reopen every
issue, change
Le 25 oct. 05, à 11:40, Ross Gardler a écrit :
Bertrand Delacretaz wrote:
Le 25 oct. 05, à 10:33, Sylvain Wallez a écrit :
...I think that, along with pinging the Ajaxian guys (which I will
do), we should rewrite our home page to make more apparent Cocoon's
unique abilities in the changing
Le 24 oct. 05, à 06:50, Niclas Hedhman a écrit :
I would like to propose;
1. Make Apache Cocoon 3.0 into the slim down, no frills, no blocks, no
nothing, thing that has been discussed recently...
Agreed, and even start this with 2.2, IIUC as soon as mavenizaion is
finished, blocks
Le 23 oct. 05, à 21:48, Andrew Savory a écrit :
...On 23 Oct 2005, at 19:20, Daniel Fagerstrom wrote:
Just because of its importance, you agree that it is important don't
you ;) we should follow our usual and well proven development
patterns which involves community involvement.
FWIW,
Le 24 oct. 05, à 18:34, Pier Fumagalli a écrit :
...let me know your preferred Jira accounts..
Either [EMAIL PROTECTED] or [EMAIL PROTECTED], whatever's
most convenient for you.
-Bertrand
Le 24 oct. 05, à 13:14, hepabolu a écrit :
...Great idea and thanks for the work, but there are currently two
issues:
- core documentation on
http://cocoon.zones.apache.org/demos/21branch/samples/ results in an
error:
java.io.FileNotFoundException:
Le 20 oct. 05, à 10:54, Bertrand Delacretaz a écrit :
I have fixed a few things so that all htmlunit-tests pass here (JDK
1.4.2, macosx 10.3.8).
It would be cool if people could run these tests on other platforms
and report results here...
FWIW, I've received a success report off-list
Le 24 oct. 05, à 21:24, Sylvain Wallez a écrit :
..We should also make an annouce that this is the testing week and
invite people to checkout the SVN and test. Otherwise, people will
just hold their breath and wait for the release to happen.
I can do it if you want...
If you do, please
Le 22 oct. 05, à 06:37, David Crossley a écrit :
...I am just finishing off storing all our configuration
at forrest.zones.a.o into our SVN. That has made it
so much easier to collaboratively work on things and
to manage it. Also if damage ever happens then we
have reliable sources.
I will
Le 22 oct. 05, à 08:31, David Crossley a écrit :
(there are links to these on http://cocoon.zones.apache.org/)
The two new demos are down ...
502 Bad Gateway
The proxy server received an invalid response from an upstream server.
Yes, I just restarted them as the svn up hadn't worked, I
Le 21 oct. 05, à 23:31, Sylvain Wallez a écrit :
...The live demo should be available soon at
http://cocoon.zones.apache.org/demos/trunk/samples/blocks/forms/sql/
The live demos have been updated but that page gives an error, as does
Le 21 oct. 05, à 22:06, Upayavira a écrit :
...And a
robots.txt on Daisy...
I've added the following at http://cocoon.zones.apache.org/robots.txt
User-agent: *
Disallow: /*
I think that's what we want, there's nothing to index on that server,
right?
-Bertrand
Le 22 oct. 05, à 13:48, Ross Gardler a écrit :
We've pretty much cleared out all the broken links in the docs in
Daisy. There's just one page left causing a problem:
http://cocoon.zones.apache.org/daisy/legacydocs/status/plan/
documentation/review-sitemap-docs.html
This page has links
Le 21 oct. 05, à 06:09, David Crossley a écrit :
...It would have a lot easier to do this documentation
movement for the 2.2 release
Yes - I cannot help on this ATM, but it looks like a lot of energy
which might bring more results if targeted to 2.2.
-Bertrand
Le 21 oct. 05, à 14:50, Carsten Ziegeler a écrit :
Can someone update our Cocoon demo version in our cocoon zone to the
version of 2.1.x of today (or tonight)? So we will then showcase our
release candidate for next week and people might directly test against
it without installing Cocoon
Le 21 oct. 05, à 14:50, Carsten Ziegeler a écrit :
Can someone update our Cocoon demo version in our cocoon zone to the
version of 2.1.x of today (or tonight)?...
Done, and I took the opportunity to activate all three demos that were
originally planned:
1)
Le 20 oct. 05, à 09:57, David Crossley a écrit :
I have created a Daisy account (crossley). Would someone
please add me to the doc-editors group.
Done.
-Bertrand
Le 20 oct. 05, à 09:07, roy huang a écrit :
Hi,all:
1.in current svn,start cocoon in win32 and access it will generate
such exception:
Message: Configuration element FileSystem not found in SearchIndex.
FWIW, I've just tested the BRANCH_2_1_X code, svn up, full rebuild, no
local.* files,
I have fixed a few things so that all htmlunit-tests pass here (JDK
1.4.2, macosx 10.3.8).
It would be cool if people could run these tests on other platforms and
report results here.
To run them use
./build.sh htmlunit-tests
and follow the instructions.
-Bertrand
Le 20 oct. 05, à 10:47, Upayavira a écrit :
...Actually, whenever a committer asks for Karma, we should give them
doc-editor and doc-committer karma straight away. I've done that for
David...
ok - I didn't do that, as David didn't ask for it. But you're right.
-Bertrand
Le 20 oct. 05, à 10:22, Bertrand Delacretaz a écrit :
Le 20 oct. 05, à 09:07, roy huang a écrit :
Hi,all:
1.in current svn,start cocoon in win32 and access it will generate
such exception:
Message: Configuration element FileSystem not found in SearchIndex.
FWIW, I've just tested
Le 19 oct. 05, à 05:20, Antonio Gallardo a écrit :
...Closing the open bugs is like deleting this knowledge database.
Bugzilla is showing how we cares about the user reports. IMHO, the
list should be a TODO list for the community...
Note that issues don't necessarily have to stay closed, we
Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
...I was waiting for a closure on the REQ Fixing really old bugs
thread before proposing a timeline, it definitely makes sense to wait
for the cleanup to be complete
Peter's idea of doing the cleanup in Jira makes a lot of sense [1], I
Le 19 oct. 05, à 01:21, Jorg Heymans a écrit :
...I've created an archetype that sets up a working cocoon core
webapplication without any blocks...
Awesome! I don't have time to play with this right now but I can't
wait...
...PS should i put the archetype in the repository somewhere? Or
Le 19 oct. 05, à 10:31, Sylvain Wallez a écrit :
...In map:call continuation=.../, the flow engine checks if
cocoon-flow-refresh exists:..
...WDYT?
Sounds good, but maybe cocoon-continuation-refresh says more about
what the parameter means.
-Bertrand, nitpicking ;-)
Le 19 oct. 05, à 12:18, Ross Gardler a écrit :
...Are we ready to delete everything from the site repo?
Perhaps move it to site/forrest-0.7?...
But if you do this it would be published on the site, not?
Then better move it to whiteboard and delete it once the new site is up
and tested.
Le 19 oct. 05, à 19:45, Pier Fumagalli a écrit :
...There is a flag Closed for bug entry on Bugzilla, which is
settable on a per-product basis, I think that will prevent anyone to
post new bugs, but we can't put in a MOVED_TO_JIRA state (that
requires changes in the database, AFAIK), so
Le 19 oct. 05, à 19:27, Carsten Ziegeler a écrit :
Ok, I think it's safer to just vote on this as well - again the
majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
-0
b) Provide a separate docs package
Le 15 oct. 05, à 19:00, Antonio Gallardo a écrit :
...If users got the time to report the bugs, I think at least we owe
them a real bug review. Just request more info if needed.
WDYT?
I think that issues are piling up in bugzilla and we obviously don't
have the manpower to take care of
Le 16 oct. 05, à 17:17, Carsten Ziegeler a écrit :
Starting with 2.2 we want to have different release cycles etc. for
each
block so I think it's time to split up the status.xml file and create a
file for each block...
+1
-Bertrand
Le 17 oct. 05, à 12:00, Upayavira a écrit :
...2. HTML Files.
PDF can go on website. Otherwise it adds 5Mb to the download..
Same here, and I think the PDF of that release should not be
overwritten with the next release, it should stay archived. Which means
it's maybe better to put the PDF
Le 11 oct. 05, à 08:28, Bertrand Delacretaz a écrit :
...So I have the pleasure of proposing Max as our new committer!...
Congratulations Max, you are elected with
21 binding +1s
1 non-binding +1
one -0
Welcome aboard - as you already have an ASF account you should get full
commit access
Le 13 oct. 05, à 23:41, Pier Fumagalli a écrit :
...Regarding the bugs themselves, I can write a simple script closing
all moved bugs with a link to the new bug in Jira as a comment (of
course, after the data-transfer is complete)..
Sounds good, and combined with the search by bugzilla issue
After our recent discussions
(http://marc.theaimsgroup.com/?t=11289532981r=1w=2), I suggest
cleaning up our bugzilla issues, with the help of those who entered
them, as outlined below.
As this impacts our user's perception and the handling of our
all-important issues list, I'd like to
Le 14 oct. 05, à 15:46, Peter Hunsberger a écrit :
Following this thread, I wonder if if might not work well to
combine
the move to Jira with the so called bug amnesty? You'd e-mail
everyone with an open bug that it was being moved to the new system
and if they where still interested in
Le 14 oct. 05, à 16:01, Bertrand Delacretaz a écrit :
...I don't know if jira is as good as bugzilla for mass operations
(i.e. set all open issues which were entered before Sept 1st to LATER
/ P5), I'll check as soon as it is back...
I've checked - there are nice bulk operations
Le 14 oct. 05, à 18:36, Vadim Gritsenko a écrit :
... * Loose local changes to:
... mirror.html (Bertrand?)
It wasn't me, but the locally modified version was correct - I have
committed the changes.
-Bertrand
Le 14 oct. 05, à 21:59, hepabolu a écrit :
Can someone give me access to the cocoon.zones.apache.org? I thought I
had access, but none of the usual passwords work
Account helma created, in group daisy.
Also done
chmod -R g+w /home/daisy/daisy-1.4-M1
so that daisy group members can write
Le 11 oct. 05, à 12:43, Pier Fumagalli a écrit :
Ok, there we go, here's the vote...
[ ] +1 Yes please, let's move all our bugs to Jira...
+1 BUT - I'm going to start a vote about
http://wiki.apache.org/cocoon/BugzillaIssuesCleanup, to do a big
cleanup in the next two weeks, so it would
Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
...In the meantime, I'm going to set-up Jira with statuses and
workflows. And after the cleanup is done, we can move all outstanding
issues over...
Cool, thanks.
-Bertrand
Le 13 oct. 05, à 16:51, Vadim Gritsenko a écrit :
Bertrand Delacretaz wrote:
Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
...In the meantime, I'm going to set-up Jira with statuses and
workflows. And after the cleanup is done, we can move all
outstanding issues over...
Shouldn't we
Le 13 oct. 05, à 22:53, Joerg Heinicke a écrit :
...You introduce another problem with this process: Current owners got
sent a bugzilla mail about closure of their bug. If they want to
reopen it later they don't know where to do it...
There must be a way to find issues in jira later based on
Le 12 oct. 05, à 05:16, Stefano Mazzocchi a écrit :
...I think a better, leaner, cleaner javadoc would go a *LNG* way
to make things easier...
I was thinking about that recently - does anyone know a tool for
tag-based navigation of javadocs?
A better *navigation* of the javadocs, like
Le 12 oct. 05, à 08:13, David Crossley a écrit :
Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
lists
Le 12 oct. 05, à 09:32, Max Pfingsthorn a écrit :
...Can't you use the refdoc stuff for that? If it's not ready, which I
guess it isn't from the STATUS at
http://svn.apache.org/repos/asf/cocoon/gsoc/rgraham/refdoc/STATUS, I
could take it from where Robert left it...
It's not far from being
Le 11 oct. 05, à 15:36, hepabolu a écrit :
...Just had a quick look and some things came to mind:
- as Carsten pointed out, the link to all samples is very
unobtrusive...
Fixed, you cannot miss the link anymore.
- I really feel the need for a back link on each overview page or
maybe the
Le 11 oct. 05, à 10:25, hepabolu a écrit :
Bertrand Delacretaz wrote:
How about doing a bug amnesty as follows?
As already said by others, I too am not fond of a bug amnesty
...I know this means a lot of work, and takes certainly a lot more
effort than simply expire, but it really
Le 12 oct. 05, à 13:06, Torsten Curdt a écrit :
Instead of waiting for this *not* to happen
(and we know it's not going to happen) I'd say -
let's ask the people whether those old bugs still
apply...
I like the idea - how do you suggest asking?
We could add a comment to each open issue with
Le 12 oct. 05, à 14:08, hepabolu a écrit :
Bertrand Delacretaz wrote:
Le 12 oct. 05, à 13:06, Torsten Curdt a écrit :
Instead of waiting for this *not* to happen
(and we know it's not going to happen) I'd say -
let's ask the people whether those old bugs still
apply...
I like the idea - how
Le 12 oct. 05, à 14:35, Vadim Gritsenko a écrit :
Bertrand Delacretaz wrote:
Note also that the aim is to remove as many exotic blocks as
possible from 2.2 and move them to contrib, so it shouldn't be that
bad in the end.
Please, blocks are *already* removed from 2.2, they reside
Le 12 oct. 05, à 14:33, Reinhard Poetz a écrit :
...I think a build/deployment system is a must as soon as we reach the
release candidate phase of 2.2. Currently the best bet is M2. Do you
see any alternatives that could be implemented faster?...
IIUC we're currently talking of a first
Le 12 oct. 05, à 15:34, hepabolu a écrit :
...Fine by me, but in the wiki page you say something along the lines
if you don't respond, the state stays WONTFIX, which in effect means
you have to mark all bugs for WONTFIX...
Yes, using the change several bugs at once means we have to set all
Le 12 oct. 05, à 15:36, Vadim Gritsenko a écrit :
...By the time m2 is properly done, we should remove svn externals
and cut bocks loose :-) and treat them as separate projects...
Ok, fine then, let's wait for this - there's no hurry but 2.2 should
give a clear signal that we want to travel
Le 12 oct. 05, à 15:39, Bertrand Delacretaz a écrit :
Le 12 oct. 05, à 15:34, hepabolu a écrit :
...Fine by me, but in the wiki page you say something along the lines
if you don't respond, the state stays WONTFIX, which in effect
means you have to mark all bugs for WONTFIX...
Yes, using
Le 12 oct. 05, à 16:15, Pier Fumagalli a écrit :
For those of you who might not have noticed it (and who are using Mac
OS/X), the ADC http://developer.apple.com/ just posted to everyone
the J2SE 5.0 Release 3 Developer Preview 2...
Thanks for the info - I hope the install does not wipe out
Le 12 oct. 05, à 16:53, Vadim Gritsenko a écrit :
What is the primary goal - do you want simply to get rid of issues or
you want to make Cocoon better?...
My goal is to prioritize the issues, find out among these 300 those who
are worth working on. Without having to spend lonely hours on
Le 12 oct. 05, à 17:05, Joerg Heinicke a écrit :
...Don't we have the votes feature of bugzilla for prioritizing the
issues?...
We might, but an active and traceable action from the bug reporters/CC
people is more useful I think.
-Bertrand
Le 10 oct. 05, à 23:04, Agile Jack a écrit :
...Thanks to Arje and others from Hippo for a well-run event, and to
the
presenters for great content...
And big thanks to you for the recordings and quick publishing, this
adds a lot of value to the event!
-Bertrand
Le 11 oct. 05, à 00:59, Pier Fumagalli a écrit :
...So, who is against switching to Jira?...
I'm all for it, especially if you do the work ;-)
Thanks for driving this.
-Bertrand
Dear community,
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
lists.
His presentation at last week's GT has shown a high level
Le 11 oct. 05, à 09:42, hepabolu a écrit :
...Requests:
- are there more people willing to contribute articles that could fit
this series?..
I could write one on Cocoon Bricks, a modern Cocoon example
application.
(I'm thinking of removing the -cms from the name when bricks moves to
the
Le 10 oct. 05, à 23:10, Berin Loritsch a écrit :
Upayavira wrote:
...https://svn.apache.org/repos/asf/cocoon/whiteboard/
Create yourself a directory there.
Will do.
FYI there's a trick to easily include blocks from the whiteboard in the
2.2 build, you can see how it's done in
Le 11 oct. 05, à 07:31, Reinhard Poetz a écrit :
...- Cocoon 2.2 will not use OSGi but will support blocks as far as
possible:...
...- Cocoon 3.0 will use OSGi -- shielding classloader and hot
plugablillity...
...WDOT?
+1 to the plan.
Just one small nitpicking comment, we should say 3.0
Le 9 oct. 05, à 18:33, Reinhard Poetz a écrit :
...So what do others think about this roadmap?...
Would you mind re-posting this roadmap question with a more prominent
subject line?
I'm afraid people will miss it due to the more or less obscure topic
being discussed here ;-)
-Bertrand
Le 9 oct. 05, à 00:39, Antonio Gallardo a écrit :
...I though we were against providing IRC support...
I don't think we can be against someone giving answers there - but it
would be cool, when people find solutions via IRC (or any other media
), to post them on the lists or on the wiki.
Le 10 oct. 05, à 11:11, Jeremy Quinn a écrit :
...We also talked about showing-off the 'sexy' stuff up front .
eg.
samples and docs highlighting the newest and best
prominent news items on the front page pointing to new cool
stuff
etc...
Have you seen how the
Le 6 oct. 05, à 11:52, Bertrand Delacretaz a écrit :
Sandor Spruit suggests this, see
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=112858673106600w=2
done for build.sh in trunk and BRANCH_2_1_X
I haven't changed the windows build scripts as I cannot test them, if
someone can do
Le 10 oct. 05, à 12:25, Andrew Savory a écrit :
...And a big thank you to Arjé and everyone at Hippo for such superb
organisation and all the hard work you put in - it was appreciated!...
BIG +1
-Bertrand
Le 10 oct. 05, à 12:28, Carsten Ziegeler a écrit :
...I just added servlet being the default parameter for the cocoon
script. As I can't test this on unix right now, I only changed the
windows scripts...so if someone wants to have a look at it... :)
done, servlet is now the default action for
Le 10 oct. 05, à 12:11, Jorg Heymans a écrit :
I suggested logging the IRC channel a while ago...
...If we could get it to log, and we include the logs somewhere
searchable
(daisy, wiki ...) that'ld be good enough already
You'd get a *lot* of noise if you simply log, so I'm not
Le 10 oct. 05, à 13:59, Carsten Ziegeler a écrit :
...I think it's a good idea to cleanup the page. But :) it raises two
questions for me:
a) How do I get to the other samples? I don't see any link.
There should be a link to all samples at the top right.
...b) Which blocks do we feature on
Le 10 oct. 05, à 14:16, Carsten Ziegeler a écrit :
Bertrand Delacretaz wrote:
There should be a link to all samples at the top right.
Oh, right, yes it's there - I overlooked it the first time. Perhaps it
should be a little bit more prominent?
right, I'll improve it when I find some time
Le 10 oct. 05, à 16:07, hepabolu a écrit :
...while looking at Bugzilla I noticed some open bugs entered as far
back as 2002. Could someone have a look and do _something_ about it?
It's not a good sign that bugs are open thatlong...
I don't think we'll ever get there, my last count says we
Le 10 oct. 05, à 20:43, Carsten Ziegeler a écrit :
...And users will feel happy, they will say: Look, in 2.2 you can
turn off
all the reloading for production with one simple switch. Isn't this
great? :)
+1, this is a small thing and it can be reassuring for people.
-Bertrand
Le 10 oct. 05, à 20:32, Geert Josten a écrit :
How about doing a bug amnesty as follows?
Good idea. Hasn't this been done before with some of the bugs?...
some, yes, but not on a large scale, which I think we need now.
-Bertrand
Le 7 oct. 05, à 17:09, Berin Loritsch a écrit :
...As to the sample apps--I agree to a point. If you don't have the
convention to build the sample app with, how is the potential user
going to know what they are looking at? In other words what are they
going to walk away with when the look
Le 7 oct. 05, à 20:47, JD Daniels a écrit :
...Now it has occured to me, that I can't find the svn address to
check out the HEAD...
You're probably looking for http://svn.apache.org/repos/asf/cocoon/
-Bertrand
Le 8 oct. 05, à 19:43, Reinhard Poetz a écrit :
...For 2.1 I'm not sure if it's worth the effort. IMHO We should focus
on 2.2 and make it stable as soon as possible
Yes, let's make as little changes as possible to 2.1 and move on.
-Bertrand
I've just committed the changes that we started yesterday at the
Hackathon, the first page of samples now shows links to a minimum
number of samples, the rest being on a different page.
I'd appreciate it if people could give it a try, I haven't had time to
check all the samples yet.
All
We talked about that this morning with Jeremy at the GT: how about
creating a contrib directory in our repository, for stuff that we
want to stay available, without being directly tied to our releases.
This could contain:
-example apps like bricks-cms
-blocks that we'd like to remove from 2.2
Le 6 oct. 05, à 10:04, Torsten Curdt a écrit :
...Let's better have a few more developer subscribed
to users again
Yes, after this discussion I think it's good enough - and I like the
idea of filtering both lists to the same folder in my mail client, so
as not to overlook user's
Sandor Spruit suggests this, see
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=112858673106600w=2
Any objections to make this the default when ant is called from
build.sh?
If not I'll add it to the branch and trunk builds.
What the option does for ant is:
--noconfig
I'd like to put a snapshot of the bricks-cms [1] example on our
download servers, so that people can get it without requiring an SVN
client.
It is not a formal release, but I'd like to have the community's
approval before doing it.
Please cast your votes, here's my own:
+1
-Bertrand
[1]
Those of you coming to the Hackathon or GT, please add your PGP key to
http://wiki.apache.org/cocoon/CocoonGetTogetherPGP if you want to sign
keys.
We'll print that page at some point to make signing easier.
-Bertrand
Le 5 oct. 05, à 09:55, Upayavira a écrit :
So, I propose to start to release 2.2alpha 1 at 3pm CET (GMT+2).
+1
-Bertrand
Le 5 oct. 05, à 10:43, Daniel Fagerstrom a écrit :
...Please cast you votes.
Enthusiastic +1, welcome Ross!
-Bertrand
Le 4 oct. 05, à 09:21, Michael Wechner a écrit :
...one could also imagine
an OpenDocument block where the ZipSource would be part of it.
If people like it and other usecases would show up, then we could
move it to the core at some later stage.
Makes sense?..
IMHO, yes if the block includes
Le 4 oct. 05, à 10:35, Arje Cahn a écrit :
...Should we do the bugtable again at the hackaton? And is someone
willing to printout the bugreports or should I arrange that?
(Bertrand...? I know you're busy..)
I am, won't have time to do it before I leave, but if there's a printer
there we'll
Le 3 oct. 05, à 21:30, Antonio Gallardo a écrit :
...I WASTED not only my last weekend, but a lot of time keeping the
f*** java 1.3 compatibility...
I agree about the *** but anyway, THANKS Antonio for this work.
Keeping 1.3 compatibility for the 2.1.x branch has been a community
decision
401 - 500 of 1481 matches
Mail list logo
