Releasing 2.0 from RC4?

Hi Lenya devs,

can we release 2.0 from RC4?

Or is someone still testing so that we should wait another
couple of 
days? If yes, how long?

-- Andreas



-- 
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


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

Hi Lenya devs

Am 11.12.2007 um 10:27 schrieb Andreas Hartmann:
>
>
> can we release 2.0 from RC4?
>
> Or is someone still testing so that we should wait
another couple of  
> days? If yes, how long?


Mmh - the image replacement bug is still worrying me a bit -
is there  
a practicable workaround, you know; right now the only was
to recover  
seems to be: choose a different url (not very user friendly
because  
existing image references will break)?

A customer of ours just encountered that problem (and
thought it was  
his fault...).


Jürgen


null-oder-eins GmbH Zürich
web & graphic design

www.null-oder-eins.ch

ragallerapache.org
Skype: callto://ragaller




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

Hi Andreas

Am 11.12.2007 um 15:47 schrieb Andreas Hartmann:

> Hi Jürgen,
>
> Jürgen Ragaller schrieb:
>
> [...]
>
>>> can we release 2.0 from RC4?
>>>
>>> Or is someone still testing so that we should
wait another couple  
>>> of days? If yes, how long?
>> Mmh - the image replacement bug is still worrying
me a bit - is  
>> there a practicable workaround, you know; right now
the only was to  
>> recover seems to be: choose a different url (not
very user friendly  
>> because existing image references will break)?
>
> do you consider this a blocker/critical bug?
>

Mmmh - sort of.

But I'm really in a clinch between not wanting to hinder
(again) a  
much awaited lenya 2.0 release and this bug (and yes I'll
open several  
bottles of champaign when lenya 2.0 sees daylight) - The
result for an  
author is very confusing; she/he sees the new picture in a
bad shape  
and hacks on (going back to the image editing step). That's
at least  
what just happend in our case.

>
> If you use a separate authoring server, you can set the
involved  
> pipelines in the svg module to noncaching, this should
help.
>

Unfortunatly we can't; at least not now (money + time). It's
one  
machine to handle all the action.
Do you consider it too performance consuming to set the
piplines to  
noncaching for all areas?

What's your judgement about the severity of that bug?


Thanks again!


Jürgen



null-oder-eins GmbH Zürich
web & graphic design

www.null-oder-eins.ch

ragallerapache.org
Skype: callto://ragaller




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

Hi Andreas

Am 11.12.2007 um 15:53 schrieb Andreas Hartmann:

> Jürgen Ragaller schrieb:
>> Hi Lenya devs
>> Am 11.12.2007 um 10:27 schrieb Andreas Hartmann:
>>>
>>>
>>> can we release 2.0 from RC4?
>>>
>>> Or is someone still testing so that we should
wait another couple  
>>> of days? If yes, how long?
>> Mmh - the image replacement bug is still worrying
me a bit - is  
>> there a practicable workaround, you know; right now
the only was to  
>> recover seems to be: choose a different url (not
very user friendly  
>> because existing image references will break)?
>
> BTW, actually the references shouldn't break because
all images are  
> referenced by UUIDs - at least if they are inserted
using the  
> standard Lenya usecases. Statically exported pages have
to be  
> updated, though.

I thought the uuids are transformed to links of the sort:

name.jpg?lenya.module=svg&height=297&width=348
and then the svn-module is called from the browser to
deliver the image.

When a user deletes the buggy image and uploads a new one
with the  
same url the same svg pipeline is called again with the same
cached  
(still an assumption) image?


Jürgen (sorry I have a meeting but will be back later).




null-oder-eins GmbH Zürich
web & graphic design

www.null-oder-eins.ch

ragallerapache.org
Skype: callto://ragaller




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

Jürgen Ragaller wrote:
> Hi Andreas
>
> Am 11.12.2007 um 15:53 schrieb Andreas Hartmann:
>
>> Jürgen Ragaller schrieb:
>>> Hi Lenya devs
>>> Am 11.12.2007 um 10:27 schrieb Andreas
Hartmann:
>>>>
>>>>
>>>> can we release 2.0 from RC4?
>>>>
>>>> Or is someone still testing so that we
should wait another couple 
>>>> of days? If yes, how long?
>>> Mmh - the image replacement bug is still
worrying me a bit - is 
>>> there a practicable workaround, you know; right
now the only was to 
>>> recover seems to be: choose a different url
(not very user friendly 
>>> because existing image references will break)?
>>
>> BTW, actually the references shouldn't break
because all images are 
>> referenced by UUIDs - at least if they are inserted
using the 
>> standard Lenya usecases. Statically exported pages
have to be 
>> updated, though.
>
> I thought the uuids are transformed to links of the
sort:
>
> name.jpg?lenya.module=svg&height=297&width=348
> and then the svn-module is called from the browser to
deliver the image.
>
> When a user deletes the buggy image and uploads a new
one with the 
> same url the same svg pipeline is called again with the
same cached 
> (still an assumption) image?

If the user upload and replaces the old image, the uuid will
remain the 
same. If they then rename the image to something different,
the caching 
system will see it as something new. Since image references
are stored 
in the documents as uuids, they won't be lost. Some (Yahoo
for instance) 
would argue that images should never change and have a long
cache life 
associated with them. They argue that if you need a new
image, give it a 
new name. Smart browsers and caches will store the image and
save on 
your load.

I wonder what sort of lifetime the images have in the svg
cache?

Richard

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

Andreas Hartmann wrote:
> Hi Lenya devs,
>
> can we release 2.0 from RC4?
>
> Or is someone still testing so that we should wait
another couple of 
> days? If yes, how long?
>
> -- Andreas
>
>
>
I have concerns about bug 43990: OneForm editor doesn't use

lenya-document: syntax when inserting images

Published pages would still include references to the
authoring side of 
things instead of live. We could put in the documentation
that a rewrite 
rule is required to do the translation for affected editors.
But even 
then, I don't know how that would react with the various
proxying 
configurations.

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

Andreas Hartmann wrote:
> Richard Frovarp schrieb:
>> Andreas Hartmann wrote:
>>> Hi Lenya devs,
>>>
>>> can we release 2.0 from RC4?
>>>
>>> Or is someone still testing so that we should
wait another couple of 
>>> days? If yes, how long?
>>>
>>> -- Andreas
>>>
>>>
>>>
>> I have concerns about bug 43990: OneForm editor
doesn't use 
>> lenya-document: syntax when inserting images
>>
>> Published pages would still include references to
the authoring side 
>> of things instead of live. We could put in the
documentation that a 
>> rewrite rule is required to do the translation for
affected editors. 
>> But even then, I don't know how that would react
with the various 
>> proxying configurations.
>
> Apart from the bug, IMO we can never avoid that people
copy & paste 
> image or link URLs from the Browser URL box into the
OneForm editor or 
> other editors. We should provide functionality or
documentation how to 
> handle this situation.
>
> From my POV we can release RC4 as 2.0 and release 2.0.1
with the fix 
> and some more testing in January.
>
> -- Andreas
>
>
>
Yeah, we will always have that problem. I've found a related
issue to 
this. I'm trying to figure out how I can replicate the
issue. 75% of the 
inserted images (from FCK) aren't being translated to UUIDs
when saving. 
Yet to fix the problem, I just save the page. I'm getting
feedback from 
our trainers on how their sessions operate, to find out what
my users 
are doing differently from me. Once I know how to replicate,
I'll do 
testing against RC4 / trunk and if it still exists, open a
bug.

My fix around the issue, has been to use mod_rewrite to
rewrite 
/authoring/ to /live/ on the live side. So it certainly is
an issue that 
documentation can get around for the moment.

Richard

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

Am 12.12.2007 um 10:37 schrieb Andreas Hartmann:

> Thorsten Scherler schrieb:
>> On Wed, 2007-12-12 at 00:07 +0100, Andreas Hartmann
wrote:
>
> [...]
>
>>> From my POV we can release RC4 as 2.0 and
release 2.0.1 with the  
>>> fix and some more testing in January.
>> I as well would like to see a release (better today
then tomorrow).
>> The current situation reminds me on a spanish
saying: "Good is the  
>> enemy
>> of perfect." Let us have a good release (which
IMO we have with  
>> RC4) and
>> strive for enhancements in upcoming subrelease
(which we hopefully  
>> on a
>> regular basis again).
>
> I totally agree. Release early, release often.

+1 from me
>
>

null-oder-eins GmbH Zürich
web & graphic design

www.null-oder-eins.ch

ragallerapache.org
Skype: callto://ragaller




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

On Wed, 2007-12-12 at 10:36 -0600, Richard Frovarp wrote:
> Thorsten Scherler wrote:
> >
> >
> > I as well would like to see a release (better
today then tomorrow).
> >
> > The current situation reminds me on a spanish
saying: "Good is the enemy
> > of perfect." Let us have a good release
(which IMO we have with RC4) and
> > strive for enhancements in upcoming subrelease
(which we hopefully on a
> > regular basis again).
> >
> > salu2
> >
> >   
> -1 for RC4 release. 42385 is a blocker from my testing.
See my newest 
> comment on the problem.

I do not want to enter in any discussion right now, but IMO
SVG is not
essential for Lenya, meaning one can perfectly work with the
cms if not
using svg images. How many percentage of our user will run
into 42385
before we will do another release?

The problem I see ATM is that since months we are trying to
release and
with every RC we find new stuff that we do not like. I have
the feeling
this will never end. We will always find bugs - meaning we
will never
release.

That is as well the main reason why we have never released
2.0 aka 1.4
till now.

This cannot go on like this! We need a release!

just my 2 cents.

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


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

Thorsten Scherler wrote:
> On Wed, 2007-12-12 at 10:36 -0600, Richard Frovarp
wrote:
>   
>> Thorsten Scherler wrote:
>>     
>>> I as well would like to see a release (better
today then tomorrow).
>>>
>>> The current situation reminds me on a spanish
saying: "Good is the enemy
>>> of perfect." Let us have a good release
(which IMO we have with RC4) and
>>> strive for enhancements in upcoming subrelease
(which we hopefully on a
>>> regular basis again).
>>>
>>> salu2
>>>
>>>   
>>>       
>> -1 for RC4 release. 42385 is a blocker from my
testing. See my newest 
>> comment on the problem.
>>     
>
> I do not want to enter in any discussion right now, but
IMO SVG is not
> essential for Lenya, meaning one can perfectly work
with the cms if not
> using svg images. How many percentage of our user will
run into 42385
> before we will do another release?
>   
Everyone who uses BitFlux. Everyone who uses OneForm. Looks
like Kupu is 
clean. Since BXE and OneForm (and FCKeditor and possibly
TinyMCE) all 
rewrite the image URL to use the SVG module. The SVG module
only returns 
one image, just scaled to different sizes. Therefore it is
essential for 
Lenya, as most of our users don't use Kupu. And the Kupu
thing might 
just be that I haven't figured out how to scale an image in
that editor yet.

We do need a release, but we need one that allows for more
than one 
image per Lenya instance.

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