Igor Vaynberg wrote:
i think that wicket trunk has been production-ready for a really long
time without a release. i also think that the next rc build has a very
good chance of becoming wicket-1.4.0.
i say we should build the rc now. it will take about a week to become
1.4.0 if all goes well, at which point Ate should know for sure what
impact his changes will have. If his changes require a break to public
api we roll another rc, if they do not we release 1.4.0 and include
his changes in 1.4.1.
OK, I'm fine with that. AFAIK my changes won't require public api changes, but
I can't say for sure yet.
Let's role rc4 first and I'll let you know next week where I'm at and if my chances will fit in before the 1.4 release or will have to wait
until 1.4.1
Regards,
Ate
my two cents
-igor
On Wed, Apr 29, 2009 at 12:33 PM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
That's up to everyone else. I could do it on Monday. Igor, Martijn,
others - what do you think?
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Apr 29, 2009 at 2:26 PM, Ate Douma <a...@douma.nu> wrote:
Jeremy Thomerson wrote:
Okay - I'll work on building an rc4 soon. Possibly tonight. If not,
then it will probably be Friday afternoon.
If you have anything else that you want to get into 1.4 - commit it now :)
I do have some important improvements for Portlet header contributions
support!
But, I haven't had enough time to fully test them yet and probably will need
a few more minor changes before I'll be ready to commit them.
I've been too busy lately with getting Pluto and Jetspeed-2 ready for the
upcoming release that I regrettably didn't had time to pay much attention on
Wicket and this pending new rc build.
I would be great if building the rc4 could wait maybe one more week or at
least until next Monday, but I'll understand if that is considered a little
too late.
Regards,
Ate
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Apr 29, 2009 at 3:15 AM, Martijn Dashorst
<martijn.dasho...@gmail.com> wrote:
Yep (typing this at ~200mph). The idea is that rolling multiple rc3's
will make testing them difficult: which version is being tested? Maven
also doesn't like multiple non-snapshot releases with the same
version. Therefore just rolling rcX's is easier, and might get us to a
final release sooner? Version numbers are cheap.
Martijn
On Wed, Apr 29, 2009 at 8:44 AM, Igor Vaynberg <igor.vaynb...@gmail.com>
wrote:
i believe he meant to roll another release from trunk and call it rc4
:) i think if we are going to do that we might as well call it rc3.
the idea is that if there are no problems with an rc release we
promote that release to final, so it should be as bug free as
possible.
-igor
On Tue, Apr 28, 2009 at 11:08 PM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
Martijn,
I'm sorry - not entirely sure I understand what you meant when you
were talking about rc4...
Did you mean that we should rebuild rc3 from trunk so that it could
hopefully be the final?
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Apr 29, 2009 at 1:04 AM, Martijn Dashorst
<martijn.dasho...@gmail.com> wrote:
I'd suggest rolling rc4 from here. And promote that one to 1.4 final
if no npe or other trouble appears. It is a *release* candidate so we
should aim for bug free.
Martijn
On Tuesday, April 28, 2009, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
Was it something that you feel is important enough to force a rebuild
of rc3?
(my money is on no - since it was previously unreported for however
long it has been in trunk and based on the time it will take to
rebuild the release)
--
Jeremy Thomerson
http://www.wickettraining.com
On Tue, Apr 28, 2009 at 4:50 PM, Juergen Donnerstag
<juergen.donners...@gmail.com> wrote:
fixed
Juergen
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
