I'm a little confused by that, does the committers not fix in trunk, merge back to the appropriate branches (1.3.x) then cut tags from the branches (1.3.5, 1.3.6)?
Steve On 28/04/2009, at 8:36 AM, Martijn Dashorst wrote:
The commit was before 1.3.5 was cut, so IMO it should be already in 1.3.5.Martijn On Tue, Apr 28, 2009 at 9:31 AM, Jeremy Thomerson <[email protected]> wrote:There's a comment that says that it's actually NOT in 1.3.5 - implyingthat the fix version is incorrect. But Igor's comment seems to indicate that it WAS fixed. I don't know which is true, but whoever really wants to know should just try it and see - and then comment on the jira to make it clear. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Apr 28, 2009 at 2:26 AM, Steve Swinsburg <[email protected]> wrote:The fix version for that issue says 1.3.5 so unless people use Jiraincorrectly, it's in 1.3.5. Likewise for the previous issue that people want to hold up the 1.3.6 release for, it has a fix version of 1.3.6 so should bein 1.3.6 already. --Steve On 28/04/2009, at 6:48 AM, Douglas Ferguson wrote:So, is this fixed in 1.3.6? https://issues.apache.org/jira/browse/WICKET-847 --------------------------------------------------------------------- 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]-- 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME cryptographic signature
