You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by David Van Couvering <da...@vancouvering.com> on 2007/06/15 19:26:40 UTC
Daily and milestone builds (was Re: JNLP storage factory & experimental modules)
That's great, but Dan was saying these aren't advertised, and actually
*can't* be advertised, since they're not official Apache releases.
The daily builds aren't that useful if nobody knows about them.
I would like to see daily builds that can be officially advertised.
I also think that milestone builds would be a super-great thing for Derby.
I first experienced the concept of milestone builds here at NetBeans.
Every six weeks or so they take the time to cut a branch, do a week's
worth of testing and bugfixing, and release a "milestone" build of the
upcoming release. This is an experimental release that allows users
to play around with what's coming up. It also helps bring about a
discipline of ongoing bugfixing and stabilization, rather than waiting
until the end game. I think that's pretty cool, and would like to see
something like that here. I recognize that means having a release
process that is actually easy and fast to do, rather than the
Herculean Challenge it is today.
David
On 6/14/07, Henri van de Scheur - Sun Norway <He...@sun.com> wrote:
> David Van Couvering wrote:
> > On 6/13/07, Daniel John Debrunner <dj...@apache.org> wrote:
> >> David Van Couvering wrote:
> >> > +1, I agree it's just too tight for 10.3.
> >> >
> >> > I'd like your response to my proposal for the experimental directory;
> >> > right now I'm moving forward with it (for checkin to the trunk *after*
> >> > we branch for 10.3).
> >>
> >> I thought we had one already, it's called trunk. :-)
> >
> > OK, fair enough, but at some point in the release cycle the trunk
> > moves from an "experimental" place to a place that requires stability
> > and only features that we are comfortable supporting. It is not clear
> > to me when or how that transformation takes place...
> >
> >>
> >> > The one thing I want to see is making our daily builds available for
> >> > download so that people can play with our stuff (or is that already
> >> > available and I don't know about it?)
> >>
> >> Daily builds are available though not directly from the ASF, but from
> >> groups (well at least one) who chose to them available. Anyone could do
> >> this if they so desire.
> >>
> >
> >> Recently there was some effort at removing visibility to users of
> >> non-release builds from ASF infrastructure, to ensure that users were
> >> picking up official ASF releases. There seemed to be some confusion as
> >> to why but it did seem to be a mandate from the board. You may want to
> >> look in the archives for real details as I could be wrong (maybe
> >> infrastructure and derby-dev within the last 9 months?)
> >>
> >
> > Well, if the ASF doesn't want to make non-official "releases"
> > available, then I believe the ASF needs to come up with an approved
> > way of making daily or milestone builds available. Many people want
> > to experiment with new stuff but they are not going to do it if they
> > have to learn how to build it. I know we all know how to build Derby,
> > but setup is not easy and we shouldn't force that on our users who
> > want to check out our new stuff and give us feedback.
> What about the daily zip-files under
> http://dbtg.thresher.com/derby/bits/trunk/ ?
> >
> > David
> >> Dan.
> >>
>
Re: Daily and milestone builds (was Re: JNLP storage factory & experimental
modules)
Posted by Daniel John Debrunner <dj...@apache.org>.
Mike Matrigali wrote:
> Sounds good to me, but I didn't understand the apache mandate. I think
> we are pretty well set up to do this safely already with jars from the
> trunk as they are always have build numbers, and are marked as alpha
> with all the upgrade safety checking.
I don't think it's anything to do with quality or backwards
compatibility. I think it's more ensuring the code is suitable for
release from a "legal" point, has the PMC checked that everything is in
order, no code/jars in the release that shouldn't be there, etc. etc.
>
> Under the apache rules can we define a trunk milestone release, which
> is something like an alpha? Some small process is probably reasonable
> so that someone can take a look at the set of tests we already run
> and decide or not to "release" it. It would be nice to be able to
> point a user at a set of alpha jars that has a recent bug fix to allow
> them to verify it before it goes into a real release.
I think anything to fine to release from ASF if it has the required
number of PMC votes. That's what makes it an official release.
But I would encourage anyone who wants to pursue this to go back and
look at the archives when the issue of removing "daily builds et al"
from users' view was raised.
Dan.
Re: Daily and milestone builds (was Re: JNLP storage factory & experimental
modules)
Posted by Mike Matrigali <mi...@sbcglobal.net>.
Sounds good to me, but I didn't understand the apache mandate. I think
we are pretty well set up to do this safely already with jars from the
trunk as they are always have build numbers, and are marked as alpha
with all the upgrade safety checking.
Under the apache rules can we define a trunk milestone release, which
is something like an alpha? Some small process is probably reasonable
so that someone can take a look at the set of tests we already run
and decide or not to "release" it. It would be nice to be able to
point a user at a set of alpha jars that has a recent bug fix to allow
them to verify it before it goes into a real release.
David Van Couvering wrote:
> That's great, but Dan was saying these aren't advertised, and actually
> *can't* be advertised, since they're not official Apache releases.
> The daily builds aren't that useful if nobody knows about them.
>
> I would like to see daily builds that can be officially advertised.
>
> I also think that milestone builds would be a super-great thing for Derby.
>
> I first experienced the concept of milestone builds here at NetBeans.
> Every six weeks or so they take the time to cut a branch, do a week's
> worth of testing and bugfixing, and release a "milestone" build of the
> upcoming release. This is an experimental release that allows users
> to play around with what's coming up. It also helps bring about a
> discipline of ongoing bugfixing and stabilization, rather than waiting
> until the end game. I think that's pretty cool, and would like to see
> something like that here. I recognize that means having a release
> process that is actually easy and fast to do, rather than the
> Herculean Challenge it is today.
>
> David
>
>
> On 6/14/07, Henri van de Scheur - Sun Norway <He...@sun.com>
> wrote:
>> David Van Couvering wrote:
>> > On 6/13/07, Daniel John Debrunner <dj...@apache.org> wrote:
>> >> David Van Couvering wrote:
>> >> > +1, I agree it's just too tight for 10.3.
>> >> >
>> >> > I'd like your response to my proposal for the experimental
>> directory;
>> >> > right now I'm moving forward with it (for checkin to the trunk
>> *after*
>> >> > we branch for 10.3).
>> >>
>> >> I thought we had one already, it's called trunk. :-)
>> >
>> > OK, fair enough, but at some point in the release cycle the trunk
>> > moves from an "experimental" place to a place that requires stability
>> > and only features that we are comfortable supporting. It is not clear
>> > to me when or how that transformation takes place...
>> >
>> >>
>> >> > The one thing I want to see is making our daily builds available for
>> >> > download so that people can play with our stuff (or is that already
>> >> > available and I don't know about it?)
>> >>
>> >> Daily builds are available though not directly from the ASF, but from
>> >> groups (well at least one) who chose to them available. Anyone
>> could do
>> >> this if they so desire.
>> >>
>> >
>> >> Recently there was some effort at removing visibility to users of
>> >> non-release builds from ASF infrastructure, to ensure that users were
>> >> picking up official ASF releases. There seemed to be some confusion as
>> >> to why but it did seem to be a mandate from the board. You may want to
>> >> look in the archives for real details as I could be wrong (maybe
>> >> infrastructure and derby-dev within the last 9 months?)
>> >>
>> >
>> > Well, if the ASF doesn't want to make non-official "releases"
>> > available, then I believe the ASF needs to come up with an approved
>> > way of making daily or milestone builds available. Many people want
>> > to experiment with new stuff but they are not going to do it if they
>> > have to learn how to build it. I know we all know how to build Derby,
>> > but setup is not easy and we shouldn't force that on our users who
>> > want to check out our new stuff and give us feedback.
>> What about the daily zip-files under
>> http://dbtg.thresher.com/derby/bits/trunk/ ?
>> >
>> > David
>> >> Dan.
>> >>
>>
>