Bruno Borges wrote:
I'm just wondering if isn't a good idea to have Wicket been supported under 1.4 until Sun drops it. :)
Question is, how? In a corporate environment, if you have two branches that need maintaining, you just employ twice as many developers (simplistic, I know...)
In open source, people follow their own urges - so what gets done is what they need. If I need a feature in 1.5, I'll add it in 1.5. If it requires 20 minutes to backport it to 1.4, which I don't need, maybe I'll do it. If it requires a day, how can I justify to my employer my spending a day on code I won't need?
So, in the end, if you want to see Wicket continue to support 1.4 (that is for versions beyond Wicket 1.3) and see situations where that is not happening, then volunteer to fix it. That way it is more likely to actually happen, because you have that urge.
Regards, Upayavira
