release situation

gang,

we need to figure out what we want to do about the failed
1.2.5 release, 
and further 1.4 / trunk releases.

clearly the lack of interest within a useful time frame for
1.2.5 is 
worrying. after all, this community has not had a release in
about 18 
months.

i see a couple possible scenarios:

a) we try again with 1.2.5
b) we retire the 1.2 branch
c) we release a new 1.4 release (a1 was the last one)

i think we should do a, followed by b and c.

other ideas, comments?

-gregor


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

Gregor J. Rothfuss escribió:
> ok, lets try again:
>
> http://people.apach
e.org/~gregor/
>
> has the exact same tarballs from last time.
Thank you, Gregor. I am not sure if I understand the last
sentence of 
your mail. Just to be sure: Did you build with a newer
subversion 
snapshot? I am asking, because there are some changes in the
last 2 
months or so.

Best Regards,

Antonio Gallardo.


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

Gregor J. Rothfuss escribió:
> no. exact the same means exactly that: they are the
same.

Recently were closed some interesting bugs, which makes
sense to add to 
the release:

1. File and image upload not working in Bitflux [1]
2. "Checkin" menu item leads to exception [2]
3. Adding document-type parameter and template matcher for
neutron protocol.


Best Regards,

Antonio Gallardo.


[1] http://issues.apache.org/bugzilla/show_bug.cgi?id=39360
[2] http://issues.apache.org/bugzilla/show_bug.cgi?id=41296

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

Antonio Gallardo wrote:

> Gregor J. Rothfuss escribió:
>
>> no. exact the same means exactly that: they are the
same.
>
>
> Recently were closed some interesting bugs, which makes
sense to add 
> to the release:
>
> 1. File and image upload not working in Bitflux [1]
> 2. "Checkin" menu item leads to exception
[2]
> 3. Adding document-type parameter and template matcher
for neutron 
> protocol.


+1

Also as Thorsten mentioned we should make the build and
lenya scripts 
executable. I guess this can be done within the ant target
during zip 
resp. tgz by using file permissions resp. mode.

Cheers

Michi

>
>
> Best Regards,
>
> Antonio Gallardo.
>
>
> [1] http://issues.apache.org/bugzilla/show_bug.cgi?id=39360
> [2] http://issues.apache.org/bugzilla/show_bug.cgi?id=41296
>
>
------------------------------------------------------------
---------
> 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

Michael Wechner wrote:
> Antonio Gallardo wrote:
> 
>> Gregor J. Rothfuss escribió:
>>
>>> no. exact the same means exactly that: they are
the same.
>>
>>
>> Recently were closed some interesting bugs, which
makes sense to add 
>> to the release:
>>
>> 1. File and image upload not working in Bitflux
[1]
>> 2. "Checkin" menu item leads to exception
[2]
>> 3. Adding document-type parameter and template
matcher for neutron 
>> protocol.
> 
> 
> +1
> 
> Also as Thorsten mentioned we should make the build and
lenya scripts 
> executable. I guess this can be done within the ant
target during zip 
> resp. tgz by using file permissions resp. mode.

ok, i fixed the permissions. we are at 2 votes, need one
more for this 
to pass.

-gregor

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

Gregor J. Rothfuss wrote:
> Michael Wechner wrote:
>> Antonio Gallardo wrote:
>>
>>> Gregor J. Rothfuss escribió:
>>>
>>>> no. exact the same means exactly that: they
are the same.
>>>
>>>
>>> Recently were closed some interesting bugs,
which makes sense to add 
>>> to the release:
>>>
>>> 1. File and image upload not working in Bitflux
[1]
>>> 2. "Checkin" menu item leads to
exception [2]
>>> 3. Adding document-type parameter and template
matcher for neutron 
>>> protocol.
>>
>>
>> +1
>>
>> Also as Thorsten mentioned we should make the build
and lenya scripts 
>> executable. I guess this can be done within the ant
target during zip 
>> resp. tgz by using file permissions resp. mode.
> 
> ok, i fixed the permissions. we are at 2 votes, need
one more for this 
> to pass.

the tarball compiles and runs fine here. i did some *very*
basic testing 
as well. dunno if i get a vote on this, but if so, i'm +1.


-- 
jörn nettingsmeier

home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621

if you are a free (as in "free speech") software
developer
and you happen to be travelling near my home, drop me a
line
and come round for a free (as in "free beer")
beer. :-D

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

Gregor J. Rothfuss wrote:
> Andreas Hartmann wrote:
>> Andreas Hartmann schrieb:
>>> Gregor J. Rothfuss schrieb:
>>>> gang,
>>>>
>>>> we need to figure out what we want to do
about the failed 1.2.5
>>>> release,
>>>> and further 1.4 / trunk releases.
>>>>
>>>> clearly the lack of interest within a
useful time frame for 1.2.5 is
>>>> worrying. after all, this community has not
had a release in about 18
>>>> months.
>>>>
>>>> i see a couple possible scenarios:
>>>>
>>>> a) we try again with 1.2.5
>>> +1, but I have to admit that I don't have the
time for testing this
>>> branch.
>>
>> I tested the basic functionality now.
>>
>> +1 to vote again for a release.
> 
> ok, lets try again:
> 
> http://people.apach
e.org/~gregor/
> 
> has the exact same tarballs from last time.

I did test the most important feature. I found one important
bug:

If I change the proxy settings in publication.xconf the urls
are
corectlly rewritten in the content area but not the menu
i.e. if i use
the following proxy entry:

<proxy area="live" ssl="false"
url="http://id
lnxjaf.unizh.ch/default"/>

I end up with a link like:
ht
tp://idlnxjaf.unizh.ch/default/tutorial/abc.html
in the content area but the link in the menu entry looks
like:
http://localhost:8080/lenya/default/live/tutorial/abc.
html

Can somebody confirm this? If yes that should be fixed imo
before a
1.2.5 relaease.

Jann


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

Jann Forrer wrote:
> Gregor J. Rothfuss wrote:
>> Andreas Hartmann wrote:
>>> Andreas Hartmann schrieb:
>>>> Gregor J. Rothfuss schrieb:
>>>>> gang,
>>>>>
>>>>> we need to figure out what we want to
do about the failed 1.2.5
>>>>> release,
>>>>> and further 1.4 / trunk releases.
>>>>>
>>>>> clearly the lack of interest within a
useful time frame for 1.2.5 is
>>>>> worrying. after all, this community has
not had a release in about 18
>>>>> months.
>>>>>
>>>>> i see a couple possible scenarios:
>>>>>
>>>>> a) we try again with 1.2.5
>>>> +1, but I have to admit that I don't have
the time for testing this
>>>> branch.
>>> I tested the basic functionality now.
>>>
>>> +1 to vote again for a release.
>> ok, lets try again:
>>
>> http://people.apach
e.org/~gregor/
>>
>> has the exact same tarballs from last time.
> 
> I did test the most important feature. I found one
important bug:
> 
> If I change the proxy settings in publication.xconf the
urls are
> corectlly rewritten in the content area but not the
menu i.e. if i use
> the following proxy entry:
> 
> <proxy area="live" ssl="false"
url="http://id
lnxjaf.unizh.ch/default"/>
> 
> I end up with a link like:
> ht
tp://idlnxjaf.unizh.ch/default/tutorial/abc.html
> in the content area but the link in the menu entry
looks like:
> http://localhost:8080/lenya/default/live/tutorial/abc.
html
> 
> Can somebody confirm this? If yes that should be fixed
imo before a
> 1.2.5 relaease.
> 

I found the problem. The parameter root is defined in
navigation.xmap
and refined in sitetree2nav.xsl. Changing  sitetree2nav.xsl
as follows
fixes this problem:

Index: sitetree2nav.xsl
============================================================
=======
--- sitetree2nav.xsl    (revision 501784)
+++ sitetree2nav.xsl    (working copy)
 -28,11
+28,11 
     >

 <xsl:param name="url"/>
+<xsl:param name="root"/>
 <xsl:param name="chosenlanguage"/>
 <xsl:param name="defaultlanguage"/>

 <xsl:variable
name="path-to-context"><xsl:call-template
name="create-path-to-context"/></xsl:variabl
e>
-<xsl:variable name="root"
select="$path-to-context"/>

 <xsl:template
name="create-path-to-context">
   <xsl:param name="local-url"
select="$url"/>

Shall I check that fix in and gregor includes it in his
tarball for
lenya-1.2.5?

Jann


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

Jann Forrer wrote:

>Jann Forrer wrote:
>  
>
>>Gregor J. Rothfuss wrote:
>>    
>>
>>>Andreas Hartmann wrote:
>>>      
>>>
>>>>Andreas Hartmann schrieb:
>>>>        
>>>>
>>>>>Gregor J. Rothfuss schrieb:
>>>>>          
>>>>>
>>>>>>gang,
>>>>>>
>>>>>>we need to figure out what we want
to do about the failed 1.2.5
>>>>>>release,
>>>>>>and further 1.4 / trunk releases.
>>>>>>
>>>>>>clearly the lack of interest within
a useful time frame for 1.2.5 is
>>>>>>worrying. after all, this community
has not had a release in about 18
>>>>>>months.
>>>>>>
>>>>>>i see a couple possible scenarios:
>>>>>>
>>>>>>a) we try again with 1.2.5
>>>>>>            
>>>>>>
>>>>>+1, but I have to admit that I don't
have the time for testing this
>>>>>branch.
>>>>>          
>>>>>
>>>>I tested the basic functionality now.
>>>>
>>>>+1 to vote again for a release.
>>>>        
>>>>
>>>ok, lets try again:
>>>
>>>http://people.apach
e.org/~gregor/
>>>
>>>has the exact same tarballs from last time.
>>>      
>>>
>>I did test the most important feature. I found one
important bug:
>>
>>If I change the proxy settings in publication.xconf
the urls are
>>corectlly rewritten in the content area but not the
menu i.e. if i use
>>the following proxy entry:
>>
>><proxy area="live"
ssl="false" url="http://id
lnxjaf.unizh.ch/default"/>
>>
>>I end up with a link like:
>>ht
tp://idlnxjaf.unizh.ch/default/tutorial/abc.html
>>in the content area but the link in the menu entry
looks like:
>>http://localhost:8080/lenya/default/live/tutorial/abc.
html
>>
>>Can somebody confirm this? If yes that should be
fixed imo before a
>>1.2.5 relaease.
>>
>>    
>>
>
>I found the problem. The parameter root is defined in
navigation.xmap
>and refined in sitetree2nav.xsl. Changing 
sitetree2nav.xsl as follows
>fixes this problem:
>
>Index: sitetree2nav.xsl
>========================================================
===========
>--- sitetree2nav.xsl    (revision 501784)
>+++ sitetree2nav.xsl    (working copy)
> -28,11 +28,11 
>     >
>
> <xsl:param name="url"/>
>+<xsl:param name="root"/>
> <xsl:param name="chosenlanguage"/>
> <xsl:param name="defaultlanguage"/>
>
> <xsl:variable
name="path-to-context"><xsl:call-template
>name="create-path-to-context"/></xsl:var
iable>
>-<xsl:variable name="root"
select="$path-to-context"/>
>
> <xsl:template
name="create-path-to-context">
>   <xsl:param name="local-url"
select="$url"/>
>
>Shall I check that fix in and gregor includes it in his
tarball for
>lenya-1.2.5?
>  
>

+1 for checking in the patch into SVN, but I think Gregor
should make a 
new tarball from
the most recent version of the 1.2.x branch with a clearly
defined 
revision number which the tarball is based on.

Cheers

Michael

>Jann
>
>
>--------------------------------------------------------
-------------
>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

Michael Wechner wrote:

> +1 for checking in the patch into SVN, but I think
Gregor should make a 
> new tarball from
> the most recent version of the 1.2.x branch with a
clearly defined 
> revision number which the tarball is based on.

ok. i will roll a fresh 1.2.5 from latest 1.2 svn later

at least now we have enough testers 



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