JIRA changed

[Henri Yandell]

In case anyone wonders, I've changed the JIRA frontpage - the idea
being to use less space and yet still retain the old functions.
Opinions are gratefully received.

It's as a test bed for the bigger task of reducing the enormity that
is the main ASF JIRA front page :)

If you use a custom dashboard, then I recommend checking out the
Release Status portlet. I love it, but putting one for each project on
the Struts JIRA frontpage would be just a little too much I think.

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Rolling Struts 1.3.9 end of April

[Paul Benedict]

I plan on rolling 1.3.9 at the end of the month. Very few bugs have been 
trickling in, which is pretty good considering all the changes since 
1.3.5. If anything else in need of minor fixing exists, please take the 
next 2 weeks to do so.


Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[s1] Porting to 1.3 Branch

[Niall Pemberton]

We seem to be getting in a habit of making changes to the 1.3 Branch
and leaving them out of the trunk. Personally I think this is a bad
idea for two reasons:

1) they may get forgotten - and we release a change in 1.3 thats then
is effectively revereted when 1.4 comes out.

2) theres always the danger that someone comes along and makes larger
changes that make porting more difficult

I also think this is the wrong way round - we should be applying
changes to the trunk and then back-porting them to the 1.3 branch (if
required). For me the most up to date copy should if possible be the
trunk and its better to apply and test changes there first.

Niall

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [s1] Porting to 1.3 Branch

[Henri Yandell]

I thought we were doing 1.3.9, then merging 1.3.9 onto the 1.4 trunk?

Hen

On 4/16/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:

We seem to be getting in a habit of making changes to the 1.3 Branch
and leaving them out of the trunk. Personally I think this is a bad
idea for two reasons:

1) they may get forgotten - and we release a change in 1.3 thats then
is effectively revereted when 1.4 comes out.

2) theres always the danger that someone comes along and makes larger
changes that make porting more difficult

I also think this is the wrong way round - we should be applying
changes to the trunk and then back-porting them to the 1.3 branch (if
required). For me the most up to date copy should if possible be the
trunk and its better to apply and test changes there first.

Niall

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [s1] Porting to 1.3 Branch

[Niall Pemberton]

On 4/17/07, Henri Yandell <[EMAIL PROTECTED]> wrote:

I thought we were doing 1.3.9, then merging 1.3.9 onto the 1.4 trunk?


Maybe so - but still a bad idea IMO.

Niall


Hen

On 4/16/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> We seem to be getting in a habit of making changes to the 1.3 Branch
> and leaving them out of the trunk. Personally I think this is a bad
> idea for two reasons:
>
> 1) they may get forgotten - and we release a change in 1.3 thats then
> is effectively revereted when 1.4 comes out.
>
> 2) theres always the danger that someone comes along and makes larger
> changes that make porting more difficult
>
> I also think this is the wrong way round - we should be applying
> changes to the trunk and then back-porting them to the 1.3 branch (if
> required). For me the most up to date copy should if possible be the
> trunk and its better to apply and test changes there first.
>
> Niall


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Roller] Fwd: struts1 -> struts2 migration

[Ted Husted]

FYI.

-- Forwarded message --
From: Allen Gilliland <[EMAIL PROTECTED]>
Date: Apr 13, 2007 5:36 PM
Subject: struts1 -> struts2 migration
To: [EMAIL PROTECTED]


we talked about this in the 4.0 planning discussions and i believe that
everyone was in agreement that starting with Roller 4.0 we would be
moving to jdk 1.5 and introducing struts2 as the next generation
framework to replace our current struts1 stuff.  since i am planning to
do a reasonable amount of work which requires modifying or adding things
to our authoring forms i'd really like to do them in struts2 so that my
work isn't going to be wasted, so that means it's time to at least start
the migration and get to a point where we start developing new pages and
forms in struts2.

i've started looking into this and playing around with it a little bit
and if anyone else is interested in this then i would love to get some
help.  so far i've just done some reading on the topic and noting down a
general strategy so if anyone has experience with this and wants to
help, please let me know.

right now i think my initial goal is to get the app configured so that
struts1 and struts2 actions and forms can run side by side, and then i
want to migrate a small set of the existing actions to detail the process.

-- Allen


--
HTH, Ted 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: JIRA changed

[Musachy Barroso]

Would it be easy to add a link to 'Open And Assigned' to the panel on the
right? I know it is in the filters dropdown, but that additional
0.1second in a zillion years would add up to something :)

musachy

On 4/16/07, Henri Yandell <[EMAIL PROTECTED]> wrote:


In case anyone wonders, I've changed the JIRA frontpage - the idea
being to use less space and yet still retain the old functions.
Opinions are gratefully received.

It's as a test bed for the bigger task of reducing the enormity that
is the main ASF JIRA front page :)

If you use a custom dashboard, then I recommend checking out the
Release Status portlet. I love it, but putting one for each project on
the Struts JIRA frontpage would be just a little too much I think.

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

tooltips testing

[Musachy Barroso]

The UI Tags example in showcase is set up to use the new javascript
tooltips, I tested it on Ubuntu/Firefox, Windows XP/IE6 and Windows
XP/Opera. If anybody is using other OS/Browser combination and could test
it, it would be good to know. Just hover the mouse over the information icon
to see if it is working :)

thanks
musachy
--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: JIRA changed

[Henri Yandell]

What's 'Open And Assigned'? It doesn't show in my filters, is it your
private filter?

Try clicking on the red part of the Assigned percentage bar on the
right hand side. That goes to issues assigned to you that need doing.

Hen

On 4/16/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:

Would it be easy to add a link to 'Open And Assigned' to the panel on the
right? I know it is in the filters dropdown, but that additional
0.1second in a zillion years would add up to something :)

musachy

On 4/16/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
>
> In case anyone wonders, I've changed the JIRA frontpage - the idea
> being to use less space and yet still retain the old functions.
> Opinions are gratefully received.
>
> It's as a test bed for the bigger task of reducing the enormity that
> is the main ASF JIRA front page :)
>
> If you use a custom dashboard, then I recommend checking out the
> Release Status portlet. I love it, but putting one for each project on
> the Struts JIRA frontpage would be just a little too much I think.
>
> Hen
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
"Hey you! Would you help me to carry the stone?" Pink Floyd



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]