You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2008/03/05 05:22:30 UTC
5.0.11 release soon?
I'm thinking that I'd like to create a 5.0.11 release this weekend,
for a monday vote. I'm hoping that 5.0.12 can follow on pretty soon
and be a "release candidate". Thoughts?
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: 5.0.11 release soon?
Posted by Ted Steen <te...@gmail.com>.
Because of https://issues.apache.org/jira/browse/TAPESTRY-2238 a big part of
the AJAX+form support is broken and these things worked before the latest
FormInjector committs.
As a committer I should stop whining and fix it, but I thnk it's too close
to the parts Howard are working on right now.
2008/3/5, Howard Lewis Ship <hl...@gmail.com>:
>
> I'm thinking that I'd like to create a 5.0.11 release this weekend,
> for a monday vote. I'm hoping that 5.0.12 can follow on pretty soon
> and be a "release candidate". Thoughts?
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
/ted
Re: 5.0.11 release soon?
Posted by Dan Adams <da...@ifactory.com>.
There are at least 2 tickets that I'm trying to get in before the release:
TAPESTRY-2244 <https://issues.apache.org/jira/browse/TAPESTRY-2244> Add
@Once annotiation for caching method values
<https://issues.apache.org/jira/browse/TAPESTRY-2244>
TAPESTRY-1653 <https://issues.apache.org/jira/browse/TAPESTRY-1653>
Provide automatic ValueEncoders and PrimaryKeyEncoders for Hibernate
entities <https://issues.apache.org/jira/browse/TAPESTRY-1653>
The second one is in progress and almost done. After that I'm going to
go through the list and pick out some others.
Kevin Menard wrote:
> I agree that we should have a 5.0.11 release soon. A lot has changed and
> really needs to be vetted before the final 5.0 release.
>
> While the final 5.0 release is something I'm sure you're dying to get out
> the door, I do want to make sure that we're giving users everything they
> need and that they're not holding out for 5.1 or later. I'm thinking it
> might be worthwhile to pick 3 - 5 of the highest voted for issues and
> implement those, otherwise stick to bugfixes.
>
> FWIW, I'm thinking of the JavaScript packing and versioning as something a
> lot of people were clamoring about and may be worth re-evaluting its 5.1
> status. Of course, if it's not highly voted for, it can stay for 5.1.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: 5.0.11 release soon?
Posted by Chris Lewis <bu...@gmail.com>.
I'll second the concern about people holding out. In fact just yesterday
in the IRC channel someone said they were doing exactly that. On the
other hand I 'm a believer in the release early + often mantra, but for
me having a stable (read 'unchanging') api is sufficient for now as the
core seems quite stable.
Anyway, I quite like the idea of picking a few of the highest issues and
making them part of the last leg. I can't say I agree with choosing the
JS library issue as one of them, but that's because I'm inarguably
biased to prototype.
chris
Kevin Menard wrote:
> I agree that we should have a 5.0.11 release soon. A lot has changed and
> really needs to be vetted before the final 5.0 release.
>
> While the final 5.0 release is something I'm sure you're dying to get out
> the door, I do want to make sure that we're giving users everything they
> need and that they're not holding out for 5.1 or later. I'm thinking it
> might be worthwhile to pick 3 - 5 of the highest voted for issues and
> implement those, otherwise stick to bugfixes.
>
> FWIW, I'm thinking of the JavaScript packing and versioning as something a
> lot of people were clamoring about and may be worth re-evaluting its 5.1
> status. Of course, if it's not highly voted for, it can stay for 5.1.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: 5.0.11 release soon?
Posted by Kevin Menard <km...@servprise.com>.
I agree that we should have a 5.0.11 release soon. A lot has changed and
really needs to be vetted before the final 5.0 release.
While the final 5.0 release is something I'm sure you're dying to get out
the door, I do want to make sure that we're giving users everything they
need and that they're not holding out for 5.1 or later. I'm thinking it
might be worthwhile to pick 3 - 5 of the highest voted for issues and
implement those, otherwise stick to bugfixes.
FWIW, I'm thinking of the JavaScript packing and versioning as something a
lot of people were clamoring about and may be worth re-evaluting its 5.1
status. Of course, if it's not highly voted for, it can stay for 5.1.
--
Kevin
On 3/4/08 11:22 PM, "Howard Lewis Ship" <hl...@gmail.com> wrote:
> I'm thinking that I'd like to create a 5.0.11 release this weekend,
> for a monday vote. I'm hoping that 5.0.12 can follow on pretty soon
> and be a "release candidate". Thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org