Release 1.4 RC1

Hi Lenya devs,

please cast your votes on a release of 1.4 release candidate
1.

The vote will be open for 72 hours.
If it passes, a code freeze will be announced.

More info: http://leny
a.apache.org/docs/release.html

-- Andreas


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Andreas Hartmann wrote:
> Hi Lenya devs,
> 
> please cast your votes on a release of 1.4 release
candidate 1.
> 
> The vote will be open for 72 hours.
> If it passes, a code freeze will be announced.

+1

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Andreas Hartmann escribió:
> Hi Lenya devs,
>
> please cast your votes on a release of 1.4 release
candidate 1.
>
> The vote will be open for 72 hours.
> If it passes, a code freeze will be announced.
>
> More info: http://leny
a.apache.org/docs/release.html
>
> -- Andreas
>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
> For additional commands, e-mail: dev-helplenya.apache.org
>   
+1

Best Regards,

Antonio Gallardo.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

On Mon, 2007-03-19 at 11:39 +0100, Andreas Hartmann wrote:
> Hi Lenya devs,
> 
> please cast your votes on a release of 1.4 release
candidate 1.
> 
> The vote will be open for 72 hours.
> If it passes, a code freeze will be announced.

+1

salu2
-- 
Thorsten Scherler                                
thorsten.at.apache.org
Open Source Java & XML                consulting,
training and solutions


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Andreas Hartmann wrote:
> Hi Lenya devs,
> 
> please cast your votes on a release of 1.4 release
candidate 1.
> 
> The vote will be open for 72 hours.
> If it passes, a code freeze will be announced.

drat. i'm all for a rc, but i still haven't merged my
branch...
i think they make the configuration a lot nicer and i'd love
to see them 
go in...

problem is:
* i think the publication.xconf should be extended to
include ac 
configuration as well, but this is not done yet.
* i'll be away until april 1st (linux audio conference, 
http://www.kgw.t
u-berlin.de/~lac2007), and i'm involved in the 
preparations, which means there'll be zero time for lenya
until it's 
over i'm afraid.
* it would not be nice to merge my branch now (although it
is functional 
afaict) and then add the ac stuff later, because both merges
would force 
users to change their configs and break stuff for the casual
upgrader...

can anyone adopt my work, move ac.xconf into
publication.xconf in a sane 
fashion and maybe merge it before the freeze occurs pretty
please?

other than that, i'm all for a freeze...

regards and sorry for bad timing on my part,

jörn


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Andreas Hartmann wrote:

>Hi Lenya devs,
>
>please cast your votes on a release of 1.4 release
candidate 1.
>
>The vote will be open for 72 hours.
>If it passes, a code freeze will be announced.
>  
>

-0 because

1) I still receive "untranslated" buttons for

http://127.0.0.1:8888/default/
authoring/?lenya.usecase=export.importExampleContent

whereas I have tested it with Firefox 1.5 and Mozilla on
Ubuntu Linux.

2)  The workflow menu has no translated text, but rather
displays:

     workflow.submit
     workflow.reject

whereas the other menus seem to be fine

3) After creating a new page, editing with Kupu and
submitting for 
review one can still edit with Kupu but not with BXE, or
Form editor, or 
whatsoever

4) In the case of the Blog publication one receives an error
screen

Cheers

Michael

>More info: http://leny
a.apache.org/docs/release.html
>
>-- Andreas
>
>
>--------------------------------------------------------
-------------
>To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
>For additional commands, e-mail: dev-helplenya.apache.org
>
>
>  
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
michael.wechnerwyona.com                        michiapache.org
+41 44 272 91 61


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Andreas Hartmann wrote:
> 
> No problem, IMO we could release an RC1 now and do an
RC2 after
> the merge.
> 
> -- Andreas

Well, I know the Lenya project is 'particular' in many ways,
but merging 
large changes to the codebase between release candidates is
very poor 
code management strategy.

I think Release Candidate means 'A version that might be
released, we 
call it candidate to better verify if anybody is happy with
it': in 
other words, after you call a RC, the changes to the code
should be 
limited to bug fixes only until the actual release happens.

Angelo.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Angelo Turetta wrote:

> Andreas Hartmann wrote:
>
>>
>> No problem, IMO we could release an RC1 now and do
an RC2 after
>> the merge.
>>
>> -- Andreas
>
>
> Well, I know the Lenya project is 'particular' in many
ways, but 
> merging large changes to the codebase between release
candidates is 
> very poor code management strategy.
>
> I think Release Candidate means 'A version that might
be released, we 
> call it candidate to better verify if anybody is happy
with it': in 
> other words, after you call a RC, the changes to the
code should be 
> limited to bug fixes only until the actual release
happens.


+1

Michael

>
> Angelo.
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
> For additional commands, e-mail: dev-helplenya.apache.org
>
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
michael.wechnerwyona.com                        michiapache.org
+41 44 272 91 61


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Andreas Hartmann wrote:
> Angelo Turetta schrieb:
>   
>> Andreas Hartmann wrote:
>>     
>>> No problem, IMO we could release an RC1 now and
do an RC2 after
>>> the merge.
>>>
>>> -- Andreas
>>>       
>> Well, I know the Lenya project is 'particular' in
many ways, but merging
>> large changes to the codebase between release
candidates is very poor
>> code management strategy.
>>
>> I think Release Candidate means 'A version that
might be released, we
>> call it candidate to better verify if anybody is
happy with it': in
>> other words, after you call a RC, the changes to
the code should be
>> limited to bug fixes only until the actual release
happens.
>>     
>
> OK, then I'd suggest we wait until the merge is
finished before
> announcing the code freeze.
>
> -- Andreas
>   

I would say freeze it now, except for the merge. Otherwise,
other 
changes may begin and not be completed after the merge. Then
we'll be 
waiting on those changes, and so on.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

>   
>> 3) After creating a new page, editing with Kupu and
submitting for
>> review one can still edit with Kupu but not with
BXE, or Form editor, or
>> whatsoever
>>     
>
> I guess this is
> http://issues.apache.org/bugzilla/show_bug.cgi?id=41765
>   

It would be a related issue. The patch I've posted doesn't
address this 
issue. It does prevent you from saving with a nasty error
message. I 
probably can figure out a patch sometime today to address
this issue as 
well.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org