ok - my idea was that we'd be going for something like this:

- every version deploys to its own folder, i.e. /tapestry5.1
/tapestry5.0, e.t.c.
upon release + there's no separate 5.0.11 vs 5.0.12 folders
- snapshots deploy every now and then (from CI machines) to similar
folders, i.e. /tapestry5.2-dev
- the landing page along with news, e.t.c. is kept separate (and in fact doesn't
even need to be created from maven + it'd be cool if it could have
some "social" features)... it doesn't have to mention older versions
right up front & it can link to content from the latest stable release

That's why i thought current structure (with tapestry-site separate)
is better...

Now, the proposed reorganization doesn't sound like it's improving on anything -
perhaps the only thing that gets easier is linking pages since they're
all in the same
project but that hasn't been a problem before...

That being said, i will not object to the change - i just don't get it - yet !

On Thu, Mar 25, 2010 at 18:55, Howard Lewis Ship <[email protected]> wrote:
> On Thu, Mar 25, 2010 at 9:45 AM, Andreas Andreou <[email protected]> wrote:
>> i dont really get it... what is the practical difference with what exists 
>> now?
>>
>> Also, wouldn't this cause problems when the current trunk becomes
>> an "older release"?
>
> It's a bit of an issue, you need to move the necessary files and
> directories to a new sub-folder.  Further, if you do a follow-up
> release, such as 5.1.0.6, you need to update the deployed site
> directory as well.
>
>
>>
>> On Thu, Mar 25, 2010 at 18:27, Thiago H. de Paula Figueiredo
>> <[email protected]> wrote:
>>> On Thu, 25 Mar 2010 13:23:19 -0300, Howard Lewis Ship <[email protected]>
>>> wrote:
>>>
>>>> This has gone around before but I expect to take this up pretty soon.
>>>>
>>>> Basically, we'll be getting rid of tapestry-site.
>>>>
>>>> It's content will be merged into tapestry-project, and
>>>> tapestry-project's documentation will take over the landing page,
>>>> http://tapestry.apache.org.
>>>>
>>>> Older releases will be under that: i.e.,
>>>> http://tapestry.apache.org/tapestry4 or
>>>> http://tapestry.apache.org/tapestry5.1
>>>>
>>>> The site content be updated out-of-release cycle, to put up important
>>>> documentation or news.
>>>>
>>>> Any objections?
>>>
>>> Go ahead!
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
>>> instructor
>>> Owner, software architect and developer, Ars Machina Tecnologia da
>>> Informação Ltda.
>>> Coordenador e professor da Especialização em Engenharia de Software com
>>> Ênfase em Java da Faculdade Pitágoras
>>> Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
>>> Sócio, Ars Machina Tecnologia da Informação Ltda.
>>> http://www.arsmachina.com.br
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>>
>>
>> --
>> Andreas Andreou - [email protected] - http://blog.andyhot.gr
>> Tapestry / Tacos developer
>> Open Source / JEE Consulting
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Andreas Andreou - [email protected] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to