On 1/30/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Hi,
Knew I'd be unpopular the moment I hit send.
no, no. we still like you. just not your decision. :)
Three quick notes.
1) don't think the changes are big. But I think the distro should be
reviewed and fixed. A bad hyperlink on the main menu, in our first
release in 3 years, looks sloppy and conveys an inaccurate impression
of the quality of our product.
review and fix away!
2) Unlike V-tools, we did not have a test build. Instead, the final
package was created with the choice "vote yes, or delay the release".
I don't like it.
no. we did have a test build and veltools did not.
test build == unreleased build to be tested then voted upon
hold on, i'm dropping this email and starting another. we have to get
our terms and release processes straight or we'll never find
consensus.
3) I'd be happy to vote +1 if we could call this Velocity 1.5rc1. But
given the historic significance of this release, I urge us to release
"Velocity 1.5" in a professional distro without obvious errors. (no
need to immediately issue Velocity 1.5.1).
best,
WILL
On 1/30/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> On 1/30/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > Reluctantly, I vote -1.
>
> :(
>
> > I tested the release. It compiled fine, ant test ran fine under JDK
> > 1.5 and 1.6, worked with Velocity Tools 1.2. But when I checked all
> > the hyperlinks, the anakia page was missing. There's an error when
> > generating the page and it was left out of the distribution [1].
>
> C'mon. Anakia's documentation is anything but hard to find. I'm all
> for getting things right, but not for holding back releases based on
> one missing doc. I'd rather you let Henning release 1.5 now and
> release 1.5.1 yourself next week.
>
> > I'm concerned about two things. I'm concerned about a prominent bad
> > link on the main menu, and I'm concerned the last minute "vote on the
> > final release" might not have uncovered additional problems. We've a
> > chance to make a major impression on the Java world with this
> > prominent release and I want this to be very smooth installation for
> > both new users and the typical existing user who wants to upgrade.
>
> We can't cower in fear of unknown bugs. Fix what you know and care
> about, then let's get this thing moving again.
>
> > My recommendation is to delay the release until there's time to fix
> > these doc issues and for more thorough testing. Mid-March seems fine.
> > For the "shallow bugs" theory to work, we need to issue a "release
> > candidate" that everyone can work with. This doesn't need to be an
> > actual release, just a binary distribution we can test. After a few
> > weeks we should be assured the details are 100% set.
>
> How about two betas and a test build? That's what we've had. This
> release has had much time to prepare. More time won't kill us, but
> let's not pretend things are ever likely to be 100% set. Trust me, if
> i cared enough, i could start combing thru the docs of almost any
> major project you like and find dozens of errors. Same goes for most
> code. Final releases will never be perfect, but the "shallow bugs"
> theory won't work if we don't get *them* out there. Far fewer people
> bother with release candidates and betas.
>
> > Incidentally, I disagree with Henning's comment that the beta2 had no
> > errors. Actually, beta2 had a serious error in the build process in
> > which "ant test" failed when run from the actual distribution. It
> > worked from the source distribution but not the released package. No
> > one found this problem for a month.
>
> And it's fixed, is it not?
>
> > I can't adequately express my admiration of Henning's efforts in the
> > last 6 months to get this out. This must be frustrating. I take
> > responsibility myself for not thinking through the implications of the
> > release process when Henning proposed a month ago we issue a release
> > at the end of January.
>
> Taking responsibility in the open source world means only one thing,
> if you ask me. Doing the work. If you're going to take
> responsibility for this by re-doing this whole process to your
> satisfaction either by repeating the 1.5 test build and vote or by
> letting 1.5 go and releasing a 1.5.1, then i won't protest. But
> please don't just sit back and critique at the last minute. That's
> not just frustrating, it's obnoxious.
>
> > However, the good news is that the recent momentum was effective. We
> > are right at the doorway to a new release with many new features. The
> > code is branched and close to perfect.
>
> it is not close to perfect, nor will it ever be, but i believe it will
> get better faster if you don't obsess about it being perfect.
>
> > Docs are set, readme is
> > present. With a little more checking (and fixing minor issues like
> > this one), we can type "ant dist" in early March and create the new
> > release.
> >
> > WILL
> >
> >
> > [1]
> > [echo]
> > [anakia] Transforming into: C:\Documents and
> > Settings\wglass\Desktop\velocity-1.5\bin\docs
> > [anakia] Input: anakia.xml
> > [anakia]
> > [anakia] Error: The end-tag for element type "example" must end with
> > a '>' delimiter.
> > [anakia] Line: 117 Column: 60
> >
> > On 1/28/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:
> > > Due to a misunderstanding in the vote procedure, we actually have to
> > > repeat the release vote, because we should vote only on really rolled
> > > releases.
> > >
> > > The candidate for the Apache Velocity 1.5 release is available from
> > > http://people.apache.org/dist/velocity/1.5/
> > >
> > > Shall we release this code base as Apache Velocity 1.5
> > >
> > > [ ] +1 Yes.
> > > [ ] 0 I still don't care.
> > > [ ] -1 No, because ________________________________.
> > >
> > > Vote period is
> > >
> > > Monday, Jan 29th 0:00 MET to Wednesday, Jan 31st 0:00 MET
> > >
> > > Best regards
> > > Henning
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Forio Business Simulations
> >
> > Will Glass-Husain
> > [EMAIL PROTECTED]
> > www.forio.com
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
--
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
---------------------------------------------------------------------
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]
