Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[ ] +1 Do it
[ ] -1 No not yet, because...
2. Release commons-skin 1
+1 from me for both
Dennis Lundberg wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[ ] +1 Do it
[ ] -1 No not yet, because...
2. R
+1 for both!
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1/+1 :)
Dennis Lundberg wrote:
> I have laid the finishing touches to commons-skin and feel that it is
> ready for prime time. Therefor I would like to propose two votes:
>
>
> 1. Promote commons-skin from commons sandbox to commons proper.
>
> [ ] +1 Do it
> [ ] -1 No not yet, because...
>
Oliver Heger wrote:
Just one question: I noticed that the links to the Cobertura report open
an empty site for some components (did not check all). Is there a
problem? (I am asking because I had some trouble when playing with the
maven 2 cobertura plug-in a while ago.)
There are 2 things that c
Martin van den Bemt wrote:
+1 to both, assuming the project documentation on the main site has nothing to
do with the skin,
since I think we don't want that menu on the main site.
The skin is only about looks. It couldn't care less about the content ;)
I'll start a thread about menus, links a
Just one question: I noticed that the links to the Cobertura report open
an empty site for some components (did not check all). Is there a
problem? (I am asking because I had some trouble when playing with the
maven 2 cobertura plug-in a while ago.)
Otherwise I am +1 for both.
Oliver
Dennis Lund
+1 to both
Oleg
On Sat, 2007-01-13 at 02:16 +0100, Dennis Lundberg wrote:
> I have laid the finishing touches to commons-skin and feel that it is
> ready for prime time. Therefor I would like to propose two votes:
>
>
> 1. Promote commons-skin from commons sandbox to commons proper.
>
> [x] +
+1 to both, assuming the project documentation on the main site has nothing to
do with the skin,
since I think we don't want that menu on the main site.
Mvgr,
Martin
Dennis Lundberg wrote:
> I have laid the finishing touches to commons-skin and feel that it is
> ready for prime time. Therefor I
On Sat, 2007-01-13 at 02:16 +0100, Dennis Lundberg wrote:
> I have laid the finishing touches to commons-skin and feel that it is
> ready for prime time. Therefor I would like to propose two votes:
>
>
> 1. Promote commons-skin from commons sandbox to commons proper.
+1
>
> 2. Release commons
On 1/12/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[ ] +1 Do it
[ ] -1 No not yet, because
+1 to both promoting and releasing commons skin.
Niall
On 1/13/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to
I have laid the finishing touches to commons-skin and feel that it is
ready for prime time. Therefor I would like to propose two votes:
1. Promote commons-skin from commons sandbox to commons proper.
[ ] +1 Do it
[ ] -1 No not yet, because...
2. Release commons-skin 1.0 based on revision 495
13 matches
Mail list logo
