You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Alex Kotchnev <ak...@gmail.com> on 2008/08/12 22:16:18 UTC
Updating the roadmap on T5 main page
Would it be possible to update the Tapestry 5 roadmap section of the main T5
site (http://tapestry.apache.org/tapestry5/) to reflect the most recent
thinking / goals of when the project is expecting / targeting a GA release
for 5.0 ? The page says that the target is Q1 2008 which in the past. Even
if it's a date that's not very soon, it would still be much more helpful and
useful than having a date in the past. The latest board report indicates
that 5.0.14 is likely to be an RC , and the current T5 main page that the GA
release will follow "shortly thereafter".
I guess the bigger issue is that we're currently evaluating what web
framework to use in a future project, and I've strongly advocated for
tapestry 5 to be considered on par w/ the other frameworks. However, not
having any inkling of when it might be release really puts a damper on the
willingness to even try it out as a viable candidate.
Thanks,
Alex Kotchnev
Re: Updating the roadmap on T5 main page
Posted by Howard Lewis Ship <hl...@gmail.com>.
Generally, the main Tapestry 5 page is only updated with each new
release; this keeps the online documentation synched with what is
currently available. The nightly documentation is, well, nightly and
reflects what will be in the next release.
On rare occasions I've updated the Tapestry 5 home page out-of-cycle.
On Wed, Aug 13, 2008 at 11:01 AM, Alex Kotchnev <ak...@gmail.com> wrote:
> My intent was not in any way to criticize the delays or ask why they
> occurred. My main point in asking is that it would be very useful to have a
> target date for the release that's not in the past. Based on what you
> mention in your email, it seems there are another several weeks worth of
> work (e.g. the three weeks for fixing the rough edges, maybe another couple
> of weeks for unexpected issues and such). So, based on that it seems like
> end of Q3 or first part of Q4 might be a reasonable date to put on the
> roadmap.
>
> Would it be possible to update that on the T5 main page (with whatever
> target seems reasonable) ? Should I submit a defect for that ?
>
> Thanks,
>
> Alex Kotchnev
>
> On Tue, Aug 12, 2008 at 6:47 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>
>> My current priority is to stabilize Tapestry 5 for a release
>> candidate. I agree things have gone on much longer than expected, but
>> the product is much, much better than I expected it to be a year ago.
>> Things slowed down in Q3-Q4 2007 as I was working for Feature50, a
>> company with no real interest in Tapestry. From December 07 on I've
>> been working for Formos, which is completely dedicated to Tapestry.
>> I've had the opportunity to use Tapestry in anger, on real client
>> projects, and have gotten direct feedback as well from the other
>> Formos developers. This has lead to a few changes but also many
>> improvements, as I've ironed out rough edges. There have been some
>> disruptive changes (the unfortunate necessity of shifting the root
>> package name was momentarily painful), but most of the APIs and
>> components have been quite solid for at least six months.
>>
>> The remaining rough edges are some "holes" in the validation strategy,
>> especially on the client side. There's a few problems with the
>> available Ajax components. The DateField component is not localized
>> and therefore a bit on the useless side. Other than that, things are
>> looking really good. These are changes I expect to address over the
>> next three weeks.
>>
>> I've noticed that several of the other T5 developers are gearing up to
>> make some contributions (you can tell by looking at JIRA update mail
>> on the developer list). The push is on!
>>
>> On Tue, Aug 12, 2008 at 1:16 PM, Alex Kotchnev <ak...@gmail.com> wrote:
>> > Would it be possible to update the Tapestry 5 roadmap section of the main
>> T5
>> > site (http://tapestry.apache.org/tapestry5/) to reflect the most recent
>> > thinking / goals of when the project is expecting / targeting a GA
>> release
>> > for 5.0 ? The page says that the target is Q1 2008 which in the past.
>> Even
>> > if it's a date that's not very soon, it would still be much more helpful
>> and
>> > useful than having a date in the past. The latest board report indicates
>> > that 5.0.14 is likely to be an RC , and the current T5 main page that the
>> GA
>> > release will follow "shortly thereafter".
>> >
>> > I guess the bigger issue is that we're currently evaluating what web
>> > framework to use in a future project, and I've strongly advocated for
>> > tapestry 5 to be considered on par w/ the other frameworks. However, not
>> > having any inkling of when it might be release really puts a damper on
>> the
>> > willingness to even try it out as a viable candidate.
>>
>> We could have slapped a "GA" label on any release since January and
>> still had a product light years ahead of the competition. Quite a few
>> in the community have decided not to wait and have put apps into
>> production, and reaped the benefit.
>>
>> I don't think anyone wants Tapestry to be in a position of having to
>> break (or rapidly deprecate) existing APIs for a 5.1 release. I think
>> we'll see some amount of minor API changes around validation and
>> validators for 5.0.15, but most of the framework is mature, solid, and
>> tested.
>>
>> I had hoped to get the validation changes into 5.0.14, but I had my
>> attentions diverted from writing code to preparing Tapestry training
>> materials; this temporarily slowed down development. Rather than
>> increase the time gap between 5.0.13 and 5.0.14 (nearly two months),
>> the developers decided to release 5.0.14 now; it had some significant
>> bug fixes and improvements that many in the larger community were
>> anxiously awaiting.
>>
>>
>> >
>> > Thanks,
>> >
>> > Alex Kotchnev
>> >
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Updating the roadmap on T5 main page
Posted by Alex Kotchnev <ak...@gmail.com>.
My intent was not in any way to criticize the delays or ask why they
occurred. My main point in asking is that it would be very useful to have a
target date for the release that's not in the past. Based on what you
mention in your email, it seems there are another several weeks worth of
work (e.g. the three weeks for fixing the rough edges, maybe another couple
of weeks for unexpected issues and such). So, based on that it seems like
end of Q3 or first part of Q4 might be a reasonable date to put on the
roadmap.
Would it be possible to update that on the T5 main page (with whatever
target seems reasonable) ? Should I submit a defect for that ?
Thanks,
Alex Kotchnev
On Tue, Aug 12, 2008 at 6:47 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> My current priority is to stabilize Tapestry 5 for a release
> candidate. I agree things have gone on much longer than expected, but
> the product is much, much better than I expected it to be a year ago.
> Things slowed down in Q3-Q4 2007 as I was working for Feature50, a
> company with no real interest in Tapestry. From December 07 on I've
> been working for Formos, which is completely dedicated to Tapestry.
> I've had the opportunity to use Tapestry in anger, on real client
> projects, and have gotten direct feedback as well from the other
> Formos developers. This has lead to a few changes but also many
> improvements, as I've ironed out rough edges. There have been some
> disruptive changes (the unfortunate necessity of shifting the root
> package name was momentarily painful), but most of the APIs and
> components have been quite solid for at least six months.
>
> The remaining rough edges are some "holes" in the validation strategy,
> especially on the client side. There's a few problems with the
> available Ajax components. The DateField component is not localized
> and therefore a bit on the useless side. Other than that, things are
> looking really good. These are changes I expect to address over the
> next three weeks.
>
> I've noticed that several of the other T5 developers are gearing up to
> make some contributions (you can tell by looking at JIRA update mail
> on the developer list). The push is on!
>
> On Tue, Aug 12, 2008 at 1:16 PM, Alex Kotchnev <ak...@gmail.com> wrote:
> > Would it be possible to update the Tapestry 5 roadmap section of the main
> T5
> > site (http://tapestry.apache.org/tapestry5/) to reflect the most recent
> > thinking / goals of when the project is expecting / targeting a GA
> release
> > for 5.0 ? The page says that the target is Q1 2008 which in the past.
> Even
> > if it's a date that's not very soon, it would still be much more helpful
> and
> > useful than having a date in the past. The latest board report indicates
> > that 5.0.14 is likely to be an RC , and the current T5 main page that the
> GA
> > release will follow "shortly thereafter".
> >
> > I guess the bigger issue is that we're currently evaluating what web
> > framework to use in a future project, and I've strongly advocated for
> > tapestry 5 to be considered on par w/ the other frameworks. However, not
> > having any inkling of when it might be release really puts a damper on
> the
> > willingness to even try it out as a viable candidate.
>
> We could have slapped a "GA" label on any release since January and
> still had a product light years ahead of the competition. Quite a few
> in the community have decided not to wait and have put apps into
> production, and reaped the benefit.
>
> I don't think anyone wants Tapestry to be in a position of having to
> break (or rapidly deprecate) existing APIs for a 5.1 release. I think
> we'll see some amount of minor API changes around validation and
> validators for 5.0.15, but most of the framework is mature, solid, and
> tested.
>
> I had hoped to get the validation changes into 5.0.14, but I had my
> attentions diverted from writing code to preparing Tapestry training
> materials; this temporarily slowed down development. Rather than
> increase the time gap between 5.0.13 and 5.0.14 (nearly two months),
> the developers decided to release 5.0.14 now; it had some significant
> bug fixes and improvements that many in the larger community were
> anxiously awaiting.
>
>
> >
> > Thanks,
> >
> > Alex Kotchnev
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Updating the roadmap on T5 main page
Posted by Howard Lewis Ship <hl...@gmail.com>.
My current priority is to stabilize Tapestry 5 for a release
candidate. I agree things have gone on much longer than expected, but
the product is much, much better than I expected it to be a year ago.
Things slowed down in Q3-Q4 2007 as I was working for Feature50, a
company with no real interest in Tapestry. From December 07 on I've
been working for Formos, which is completely dedicated to Tapestry.
I've had the opportunity to use Tapestry in anger, on real client
projects, and have gotten direct feedback as well from the other
Formos developers. This has lead to a few changes but also many
improvements, as I've ironed out rough edges. There have been some
disruptive changes (the unfortunate necessity of shifting the root
package name was momentarily painful), but most of the APIs and
components have been quite solid for at least six months.
The remaining rough edges are some "holes" in the validation strategy,
especially on the client side. There's a few problems with the
available Ajax components. The DateField component is not localized
and therefore a bit on the useless side. Other than that, things are
looking really good. These are changes I expect to address over the
next three weeks.
I've noticed that several of the other T5 developers are gearing up to
make some contributions (you can tell by looking at JIRA update mail
on the developer list). The push is on!
On Tue, Aug 12, 2008 at 1:16 PM, Alex Kotchnev <ak...@gmail.com> wrote:
> Would it be possible to update the Tapestry 5 roadmap section of the main T5
> site (http://tapestry.apache.org/tapestry5/) to reflect the most recent
> thinking / goals of when the project is expecting / targeting a GA release
> for 5.0 ? The page says that the target is Q1 2008 which in the past. Even
> if it's a date that's not very soon, it would still be much more helpful and
> useful than having a date in the past. The latest board report indicates
> that 5.0.14 is likely to be an RC , and the current T5 main page that the GA
> release will follow "shortly thereafter".
>
> I guess the bigger issue is that we're currently evaluating what web
> framework to use in a future project, and I've strongly advocated for
> tapestry 5 to be considered on par w/ the other frameworks. However, not
> having any inkling of when it might be release really puts a damper on the
> willingness to even try it out as a viable candidate.
We could have slapped a "GA" label on any release since January and
still had a product light years ahead of the competition. Quite a few
in the community have decided not to wait and have put apps into
production, and reaped the benefit.
I don't think anyone wants Tapestry to be in a position of having to
break (or rapidly deprecate) existing APIs for a 5.1 release. I think
we'll see some amount of minor API changes around validation and
validators for 5.0.15, but most of the framework is mature, solid, and
tested.
I had hoped to get the validation changes into 5.0.14, but I had my
attentions diverted from writing code to preparing Tapestry training
materials; this temporarily slowed down development. Rather than
increase the time gap between 5.0.13 and 5.0.14 (nearly two months),
the developers decided to release 5.0.14 now; it had some significant
bug fixes and improvements that many in the larger community were
anxiously awaiting.
>
> Thanks,
>
> Alex Kotchnev
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org