This is a pretty unsatisfactory solution. Why don't the T5.4 JIRA issues simply show which beta they've been released into?
On 10 Aug 2014, at 6:58 pm, Basile Chandesris <ba...@free.fr> wrote: > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git&a=search&h=HEAD&st=commit&s=TAP5-2329 > -> 2014-05-27 > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git&a=search&h=HEAD&st=commit&s=zone+ > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=0119f9a890c8becb80fa1d5f36c1ab1f4ec8660c > Thu, 7 Aug 2014 -> 5.4-beta-16 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=90766995f59048cb7f7d4cf042a21a9d728583db > Sun, 20 Jul 2014 -> 5.4-beta-15 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=ded30cceeca17469c7081255756599703bd6cd40 > Thu, 17 Jul 2014 -> 5.4-beta-14 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=57171a34a8fcbaf8fe25749096a00b262ab4c871 > Mon, 23 Jun 2014 -> 5.4-beta-13 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=6ee341ae2578d0a455a6deccb392a0f352c6f624 > Fri, 20 Jun 2014 -> 5.4-beta-12 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=4780b04b5c2bdebbd3f4f96691e3f15727b5cb09 > > Tue, 17 Jun 2014 -> 5.4-beta-11 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=326786c8b739e8b093794710d20a7a28631813da > Tue, 3 Jun 2014 -> 5.4-beta-10 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=d49ddd604f4387b8d0c0f42ccee75191967a6fa1 > Tue, 3 Jun 2014 -> 5.4-beta-9 is available > > https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=2650b107c194a06cfc855b1526d8fa06012ec2c0 > Mon, 2 Jun 2014 -> 5.4-beta-8 is available > > http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=search_page&node=2375124&query=vote&sort=date > > http://www.apache.org/dev/release.html > > > Le 09/08/14 23:14, Muhammad Gelbana a écrit : >> But even if I can submit a context value, how can I know the which zone to >> update ? (i.e. what is zone's id ?) >> >> I mentioned that zones and select components are repeated in a loop. >> >> *---------------------* >> *Muhammad Gelbana* >> http://www.linkedin.com/in/mgelbana >> >> >> On Sat, Aug 9, 2014 at 4:59 PM, Muhammad Gelbana <m.gelb...@gmail.com> >> wrote: >> >>> I can't figure out the version having this fix ! >>> >>> I can only see that 5.4-beta-6 was announced on tapestry.apache.org few >>> days before Thiago committed the fox on GIT but I cannot figure out the >>> exact version having this fix and I don't know how the developers organize >>> their brnaches >>> >>> *---------------------* >>> *Muhammad Gelbana* >>> http://www.linkedin.com/in/mgelbana >>> >>> >>> On Sat, Aug 9, 2014 at 4:11 PM, Lance Java <lance.j...@googlemail.com> >>> wrote: >>> >>>> Here's the jira >>>> >>>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/TAP5-2301 >>>> >>>> Looks like you're in luck... Thiago has implemented it! >>>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
