Hi, The main concern that I have is that the focus will be on the time rather than the functionality. i.e. I'm not sure that there's any one explicitly looking at making sure that the unit tests and the examples run (OK, they should be one and the same, but I don't think they are yet) before a release.
I'd be quite happy to support a weekly/bi-weekly release if there was a commitment for someone to run the tests to check as part of the release, it's just that I'd prefer it if, in the case where they found an issue/test-fail, they'd not feel there was a need to get the release made regardless just because it was 2 weeks since the last one. I'd be happy enough for them to call a code-freeze 'till fixed, which might help ensure the release isn't deferred forever though! /Gwyn On Mon, 29 Nov 2004 11:11:21 +0100, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Gwyn, > > It *DOES* gain many things, among those: > * a consistent build that never fails and that we can 'release' instantly. > * it allows me (and possibly others) to use the latest and greatest without > creating a source code dependency. > * it allows others to learn the process of creating a release (when we > alternate roles), which is in the end a gain for all of us. > > I constantly see projects keeping behind releases because 'we desperately > need this feature' and postponing release after release. I really see a > problem with the current 0.9.13-alpha since the changes in the API are > considerable when compared to HEAD. So in order to have people work with the > latest api's and to be able to support them. Telling people to check out CVS > head and build their own wicket is IMO very bad, telling them they are using > an outdated jar file seems to me less intrusive. > > I don't say we should put out the big 1.0 right now, but a weekly build > should keep us on our toes. Maven helps a great deal when we update the > changes.xml document and use the sourceforge trackers consistently for new > features added. > > Martijn > > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Gwyn Evans > Verzonden: maandag 29 november 2004 10:38 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: [Wicket-develop] new release this sunday? > > > > Martijn: I'd vote against an 'automatic' release where the CVS HEAD is > available, as it doesn't seem to gain anything. > > Eelco: That persistance change sounds interesting - I'll let you know how I > get on with testing them against the problem, as I've not got anywhere > towards resolving it in other ways! > > /Gwyn > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide Read honest & candid reviews > on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Wicket-develop mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Wicket-develop mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
