Andy,
I'm with you for another alpha release asap for the T4.13 users. And I agree
on not having the portlet functionality in beta 1 if it's too difficult or
too much work right now. It seems to me that the point of beta's is that the
given functionality is as bugfree as possible. Release candidates are
complete versions with (nearly) all functionality.
<off topic, probably unfunded comments>
I must admit that the sequential-numbering-problem looks grim. It's one of
the points that when I read it in Howards book I tought "hmm that nasty". I
havn't looked into the problem and the code though so I can be totally wrong
here. Maybe we should have partial sequences like "document.form.textfield1"
instead of "23". Another possibility would be directed rewind trough direct
naming, any explicity named components must be able to (partially) reind on
their own.
</off topic, probably unfunded comments>
Dennis
----- Original Message -----
From: "Andreas Andreou" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, December 09, 2005 4:05 PM
Subject: Re: [Tacos-devel] beta-1 release :(
hmm...
i'm +1 for a release asap.
AFAIK, the current bugs / problems are those 2 mentioned
in the previous emails + the portlet support.
Portlet support will have to wait ( but I'm currently talking a look at it
and perhaps Jesse is too) for a later beta, and even if we don't resolve
the other bugs by monday, I think a release should be made (perhaps,
it should have been named alpha-7 ).
Remember that we still don't have a release that works with
Tapestry-4-beta-13 and on. A new user will have to grab the source
and compile if he wants to try tacos right now.
Andy
Jesse Kuhnert wrote:
Really? Maybe you are right. That sounds like good advice. I don't want
user
expectations to cause discontent. Thank you for the suggestion, I think
I'll
follow it. (At least for one more release)
jesse
On 12/9/05, Dennis Fleurbaaij <[EMAIL PROTECTED]> wrote:
Jesse,
In my own experience with open source projects (
http://core-lan-org.sourceforge.net & http://helpcore.sourceforge.net)
and
"weird stuff going on in beta's" I've always opted not to release.
Release
early and release often does only apply if "release is working" ;-)
Otherwise just keep it in alpha just a bit longer until it's fixed, saves
a
LOT of trouble.
An besides in open source, nearly everyone expects beta's to be as good
as
final releases, so why release now if you get get it fixed?
Kind regards,
Dennis Fleurbaaij
----- Original Message -----
*From:* Jesse Kuhnert <[EMAIL PROTECTED]>
*To:* [email protected]
*Sent:* Friday, December 09, 2005 3:23 PM
*Subject:* [Tacos-devel] beta-1 release :(
So since it seems like there's so much questionable stuff going on, and
because it's friday I would have to say that a release isn't happening
until
Monday.
Let's say that between now and then though that no new features of any
kind are added, just bug fixes and documentation updates.
Sound reasonable? I'm releasing beta-1 on Monday whether it's ready or
not, there's always beta-2 ;)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
