You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by Guido García Bernardo <gg...@itdeusto.com> on 2005/07/05 13:23:45 UTC
ibatis 2.1.5 release plan
Hi,
I am facing with this bug:
http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
Is there any release plan for 2.1.5 so that I can decide whether or not
I'll need to use 2.0.9b or compile the source?
Thank you very much.
--
Guido García Bernardo - ggarciab@itdeusto.com
Tfn. +34 983 54 89 08
ITDEUSTO - Valladolid
Re: ibatis 2.1.5 release plan
Posted by Larry Meadors <la...@gmail.com>.
I think that is a great idea.
Does anyone know what apache has for doing automated builds?
It would be great to have something like cruise control doing this for us.
Larry
On 7/5/05, Sven Boden <li...@pandora.be> wrote:
>
> Not specific to the problem below. But what about providing iBATIS
> development releases, e.g. after every big round of SVN changes. Most
> other projects seem to do it.
>
> A few advantages I see:
> - It's easier to tell people: "test with the development jar files"
> than "extract the sources from SVN, compile and test"
> - Better quality of releases as more people would already test/use the
> development releases.
> - Less "pressure" to release new versions.
>
> Regards,
> Sven Boden
>
>
> On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
>
> >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
> >go!
> >
> >Cheers,
> >clinton
> >
> >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> >>
> >> Hi,
> >>
> >> I am facing with this bug:
> >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
> >>
> >> Is there any release plan for 2.1.5 so that I can decide whether or not
> >> I'll need to use 2.0.9b or compile the source?
> >>
> >> Thank you very much.
> >>
> >> --
> >> Guido García Bernardo - ggarciab@itdeusto.com
> >> Tfn. +34 983 54 89 08
> >> ITDEUSTO - Valladolid
> >>
> >>
> >>
>
>
Fwd: ibatis 2.1.5 release plan
Posted by Larry Meadors <la...@gmail.com>.
Stupid gmail - this was supposed to go to the list...
---------- Forwarded message ----------
From: Larry Meadors <la...@gmail.com>
Date: Jul 7, 2005 6:33 AM
Subject: Re: ibatis 2.1.5 release plan
To: Gilles Bayon <ib...@gmail.com>
Mark this day, you may never hear me say this again:
Yes, Windows is probably the best choice for this task.
It will take a bit longer for me to get a windows box set up and ready
to go. Will XP be OK?
Can one of you ibatis.net guys take a look at the build for it? There
are several paths coded into it that could be made into variables to
simplify the build.
Larry
On 7/6/05, Gilles Bayon <ib...@gmail.com> wrote:
> +1
> Thanks, Larry
>
> I prefer to have a Windows OS, as the main usage of iBATAIS.NET is targeted
> Windows and Sql Server.
> We could then pass the tests with MSDE ( a light and free Sql Server
> instance).
>
>
> On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
> > OK, i just bopped into the irc channel, and there are no boxen to
> > actually *do* the builds on (unless we are using gump), only to hold
> > the results.
> >
> > I have 6-8 boxes in my basement..I think one has a linux on it that i
> > can use to set up some stuff to get it going. So, do you think
> > ibatis.net will build on linux with mono and nant? If not i suppose I
> > can setup a winwoes box for you... ;-)
> >
> > Larry
> >
> > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > There's plenty of hardware for things like this. It's just a matter of
> > > spending some quality time with infrastructure, preferably by IRC [and
> > > I think everyone knows how much I adore IRC :)].
> > >
> > > * http://apache.org/dev/infra-volunteer.html
> > >
> > > Several projects have their own zone on helios now:
> > >
> > > * http://apache.org/dev/machines.html
> > >
> > > -T.
> > >
> > > On 7/6/05, Larry Meadors < larry.meadors@gmail.com> wrote:
> > > > That sounds reasonable to me. I would be more than willing to set up a
> > > > box to do the builds here if there is not one at apache to use.
> > > >
> > > > Does anyone know if there is one already?
> > > >
> > > > Larry
> > > >
> > > > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > > > All ASF projects are expected to provide automatic nightly builds.
> We
> > > > > just haven't gotten to around to that yet. The nightly builds live
> for
> > > > > seven days each, and then get recycled, so as to not eat up too much
> > > > > disk space.
> > > > >
> > > > > Any non-automatic release is generally tagged with a sequential
> > > > > version number. After someone rolls it, we vote on it's quality:
> > > > > Alpha, Beta, General Release. A release can start out as Alpha and
> > > > > work its way up to General Release as more people try it. A release
> > > > > can also be downgraded if a problem is found later.
> > > > >
> > > > > Of course, since the Subversion revision numbers are essentially
> tags,
> > > > > we could also snag any given nightly build (once we have them) and
> > > > > designate it "version #.#.#", making a note in our status file that
> > > > > version #.#.# corresponds to SVN revision ####.
> > > > >
> > > > > Later, if we ever need to branch, we can branch on a revision number
> > > > > as easily as a tag.
> > > > >
> > > > > -Ted.
> > > > >
> > > > > On 7/5/05, Sven Boden < list123@pandora.be> wrote:
> > > > > >
> > > > > > Not specific to the problem below. But what about providing iBATIS
> > > > > > development releases, e.g. after every big round of SVN changes.
> Most
> > > > > > other projects seem to do it.
> > > > > >
> > > > > > A few advantages I see:
> > > > > > - It's easier to tell people: "test with the development jar
> files"
> > > > > > than "extract the sources from SVN, compile and test"
> > > > > > - Better quality of releases as more people would already test/use
> the
> > > > > > development releases.
> > > > > > - Less "pressure" to release new versions.
> > > > > >
> > > > > > Regards,
> > > > > > Sven Boden
> > > > > >
> > > > > >
> > > > > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> > > > > >
> > > > > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll
> be good to
> > > > > > >go!
> > > > > > >
> > > > > > >Cheers,
> > > > > > >clinton
> > > > > > >
> > > > > > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > > > > > >>
> > > > > > >> Hi,
> > > > > > >>
> > > > > > >> I am facing with this bug:
> > > > > > >>
> http://issues.apache.org/jira/browse/IBATIS-152 , solved in
> 2.1.5
> > > > > > >>
> > > > > > >> Is there any release plan for 2.1.5 so that I can decide
> whether or not
> > > > > > >> I'll need to use 2.0.9b or compile the source?
> > > > > > >>
> > > > > > >> Thank you very much.
> > > > > > >>
> > > > > > >> --
> > > > > > >> Guido García Bernardo - ggarciab@itdeusto.com
> > > > > > >> Tfn. +34 983 54 89 08
> > > > > > >> ITDEUSTO - Valladolid
> > >
> >
>
>
Re: ibatis 2.1.5 release plan
Posted by Gilles Bayon <ib...@gmail.com>.
+1
Thanks, Larry
I prefer to have a Windows OS, as the main usage of
iBATAIS.NET<http://iBATAIS.NET>is targeted Windows and Sql Server.
We could then pass the tests with MSDE ( a light and free Sql Server
instance).
On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
>
> OK, i just bopped into the irc channel, and there are no boxen to
> actually *do* the builds on (unless we are using gump), only to hold
> the results.
>
> I have 6-8 boxes in my basement..I think one has a linux on it that i
> can use to set up some stuff to get it going. So, do you think
> ibatis.net <http://ibatis.net> will build on linux with mono and nant? If
> not i suppose I
> can setup a winwoes box for you... ;-)
>
> Larry
>
> On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > There's plenty of hardware for things like this. It's just a matter of
> > spending some quality time with infrastructure, preferably by IRC [and
> > I think everyone knows how much I adore IRC :)].
> >
> > * http://apache.org/dev/infra-volunteer.html
> >
> > Several projects have their own zone on helios now:
> >
> > * http://apache.org/dev/machines.html
> >
> > -T.
> >
> > On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
> > > That sounds reasonable to me. I would be more than willing to set up a
> > > box to do the builds here if there is not one at apache to use.
> > >
> > > Does anyone know if there is one already?
> > >
> > > Larry
> > >
> > > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > > All ASF projects are expected to provide automatic nightly builds.
> We
> > > > just haven't gotten to around to that yet. The nightly builds live
> for
> > > > seven days each, and then get recycled, so as to not eat up too much
> > > > disk space.
> > > >
> > > > Any non-automatic release is generally tagged with a sequential
> > > > version number. After someone rolls it, we vote on it's quality:
> > > > Alpha, Beta, General Release. A release can start out as Alpha and
> > > > work its way up to General Release as more people try it. A release
> > > > can also be downgraded if a problem is found later.
> > > >
> > > > Of course, since the Subversion revision numbers are essentially
> tags,
> > > > we could also snag any given nightly build (once we have them) and
> > > > designate it "version #.#.#", making a note in our status file that
> > > > version #.#.# corresponds to SVN revision ####.
> > > >
> > > > Later, if we ever need to branch, we can branch on a revision number
> > > > as easily as a tag.
> > > >
> > > > -Ted.
> > > >
> > > > On 7/5/05, Sven Boden <li...@pandora.be> wrote:
> > > > >
> > > > > Not specific to the problem below. But what about providing iBATIS
> > > > > development releases, e.g. after every big round of SVN changes.
> Most
> > > > > other projects seem to do it.
> > > > >
> > > > > A few advantages I see:
> > > > > - It's easier to tell people: "test with the development jar
> files"
> > > > > than "extract the sources from SVN, compile and test"
> > > > > - Better quality of releases as more people would already test/use
> the
> > > > > development releases.
> > > > > - Less "pressure" to release new versions.
> > > > >
> > > > > Regards,
> > > > > Sven Boden
> > > > >
> > > > >
> > > > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> > > > >
> > > > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll
> be good to
> > > > > >go!
> > > > > >
> > > > > >Cheers,
> > > > > >clinton
> > > > > >
> > > > > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > > > > >>
> > > > > >> Hi,
> > > > > >>
> > > > > >> I am facing with this bug:
> > > > > >> http://issues.apache.org/jira/browse/IBATIS-152, solved in
> 2.1.5
> > > > > >>
> > > > > >> Is there any release plan for 2.1.5 so that I can decide
> whether or not
> > > > > >> I'll need to use 2.0.9b or compile the source?
> > > > > >>
> > > > > >> Thank you very much.
> > > > > >>
> > > > > >> --
> > > > > >> Guido García Bernardo - ggarciab@itdeusto.com
> > > > > >> Tfn. +34 983 54 89 08
> > > > > >> ITDEUSTO - Valladolid
> >
>
Re: ibatis 2.1.5 release plan
Posted by Larry Meadors <la...@gmail.com>.
I will try to get to it this evening or later this afternoon.
On 7/6/05, Roberto R <ro...@gmail.com> wrote:
> Wow, thanks Larry!
>
> Fixing up the NAnt scripts is on my JIRA TODO list, but I haven't gotten
> around to it yet. :-(
>
> Either Linux or Windows would work, but getting it going on Windows would
> probably be faster at this point.
>
> Roberto
>
>
>
> On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
> > OK, i just bopped into the irc channel, and there are no boxen to
> > actually *do* the builds on (unless we are using gump), only to hold
> > the results.
> >
> > I have 6-8 boxes in my basement..I think one has a linux on it that i
> > can use to set up some stuff to get it going. So, do you think
> > ibatis.net will build on linux with mono and nant? If not i suppose I
> > can setup a winwoes box for you... ;-)
> >
> > Larry
> >
> > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > There's plenty of hardware for things like this. It's just a matter of
> > > spending some quality time with infrastructure, preferably by IRC [and
> > > I think everyone knows how much I adore IRC :)].
> > >
> > > * http://apache.org/dev/infra-volunteer.html
> > >
> > > Several projects have their own zone on helios now:
> > >
> > > * http://apache.org/dev/machines.html
> > >
> > > -T.
> > >
> > > On 7/6/05, Larry Meadors <larry.meadors@gmail.com > wrote:
> > > > That sounds reasonable to me. I would be more than willing to set up a
> > > > box to do the builds here if there is not one at apache to use.
> > > >
> > > > Does anyone know if there is one already?
> > > >
> > > > Larry
> > > >
> > > > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > > > All ASF projects are expected to provide automatic nightly builds.
> We
> > > > > just haven't gotten to around to that yet. The nightly builds live
> for
> > > > > seven days each, and then get recycled, so as to not eat up too much
> > > > > disk space.
> > > > >
> > > > > Any non-automatic release is generally tagged with a sequential
> > > > > version number. After someone rolls it, we vote on it's quality:
> > > > > Alpha, Beta, General Release. A release can start out as Alpha and
> > > > > work its way up to General Release as more people try it. A release
> > > > > can also be downgraded if a problem is found later.
> > > > >
> > > > > Of course, since the Subversion revision numbers are essentially
> tags,
> > > > > we could also snag any given nightly build (once we have them) and
> > > > > designate it "version #.#.#", making a note in our status file that
> > > > > version #.#.# corresponds to SVN revision ####.
> > > > >
> > > > > Later, if we ever need to branch, we can branch on a revision number
> > > > > as easily as a tag.
> > > > >
> > > > > -Ted.
> > > > >
> > > > > On 7/5/05, Sven Boden < list123@pandora.be> wrote:
> > > > > >
> > > > > > Not specific to the problem below. But what about providing iBATIS
> > > > > > development releases, e.g. after every big round of SVN changes.
> Most
> > > > > > other projects seem to do it.
> > > > > >
> > > > > > A few advantages I see:
> > > > > > - It's easier to tell people: "test with the development jar
> files"
> > > > > > than "extract the sources from SVN, compile and test"
> > > > > > - Better quality of releases as more people would already test/use
> the
> > > > > > development releases.
> > > > > > - Less "pressure" to release new versions.
> > > > > >
> > > > > > Regards,
> > > > > > Sven Boden
> > > > > >
> > > > > >
> > > > > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> > > > > >
> > > > > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll
> be good to
> > > > > > >go!
> > > > > > >
> > > > > > >Cheers,
> > > > > > >clinton
> > > > > > >
> > > > > > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > > > > > >>
> > > > > > >> Hi,
> > > > > > >>
> > > > > > >> I am facing with this bug:
> > > > > > >>
> http://issues.apache.org/jira/browse/IBATIS-152 , solved in
> 2.1.5
> > > > > > >>
> > > > > > >> Is there any release plan for 2.1.5 so that I can decide
> whether or not
> > > > > > >> I'll need to use 2.0.9b or compile the source?
> > > > > > >>
> > > > > > >> Thank you very much.
> > > > > > >>
> > > > > > >> --
> > > > > > >> Guido García Bernardo - ggarciab@itdeusto.com
> > > > > > >> Tfn. +34 983 54 89 08
> > > > > > >> ITDEUSTO - Valladolid
> > >
> >
>
>
Re: ibatis 2.1.5 release plan
Posted by Roberto R <ro...@gmail.com>.
Wow, thanks Larry!
Fixing up the NAnt scripts is on my JIRA TODO list, but I haven't gotten
around to it yet. :-(
Either Linux or Windows would work, but getting it going on Windows would
probably be faster at this point.
Roberto
On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
>
> OK, i just bopped into the irc channel, and there are no boxen to
> actually *do* the builds on (unless we are using gump), only to hold
> the results.
>
> I have 6-8 boxes in my basement..I think one has a linux on it that i
> can use to set up some stuff to get it going. So, do you think
> ibatis.net <http://ibatis.net> will build on linux with mono and nant? If
> not i suppose I
> can setup a winwoes box for you... ;-)
>
> Larry
>
> On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > There's plenty of hardware for things like this. It's just a matter of
> > spending some quality time with infrastructure, preferably by IRC [and
> > I think everyone knows how much I adore IRC :)].
> >
> > * http://apache.org/dev/infra-volunteer.html
> >
> > Several projects have their own zone on helios now:
> >
> > * http://apache.org/dev/machines.html
> >
> > -T.
> >
> > On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
> > > That sounds reasonable to me. I would be more than willing to set up a
> > > box to do the builds here if there is not one at apache to use.
> > >
> > > Does anyone know if there is one already?
> > >
> > > Larry
> > >
> > > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > > All ASF projects are expected to provide automatic nightly builds.
> We
> > > > just haven't gotten to around to that yet. The nightly builds live
> for
> > > > seven days each, and then get recycled, so as to not eat up too much
> > > > disk space.
> > > >
> > > > Any non-automatic release is generally tagged with a sequential
> > > > version number. After someone rolls it, we vote on it's quality:
> > > > Alpha, Beta, General Release. A release can start out as Alpha and
> > > > work its way up to General Release as more people try it. A release
> > > > can also be downgraded if a problem is found later.
> > > >
> > > > Of course, since the Subversion revision numbers are essentially
> tags,
> > > > we could also snag any given nightly build (once we have them) and
> > > > designate it "version #.#.#", making a note in our status file that
> > > > version #.#.# corresponds to SVN revision ####.
> > > >
> > > > Later, if we ever need to branch, we can branch on a revision number
> > > > as easily as a tag.
> > > >
> > > > -Ted.
> > > >
> > > > On 7/5/05, Sven Boden <li...@pandora.be> wrote:
> > > > >
> > > > > Not specific to the problem below. But what about providing iBATIS
> > > > > development releases, e.g. after every big round of SVN changes.
> Most
> > > > > other projects seem to do it.
> > > > >
> > > > > A few advantages I see:
> > > > > - It's easier to tell people: "test with the development jar
> files"
> > > > > than "extract the sources from SVN, compile and test"
> > > > > - Better quality of releases as more people would already test/use
> the
> > > > > development releases.
> > > > > - Less "pressure" to release new versions.
> > > > >
> > > > > Regards,
> > > > > Sven Boden
> > > > >
> > > > >
> > > > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> > > > >
> > > > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll
> be good to
> > > > > >go!
> > > > > >
> > > > > >Cheers,
> > > > > >clinton
> > > > > >
> > > > > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > > > > >>
> > > > > >> Hi,
> > > > > >>
> > > > > >> I am facing with this bug:
> > > > > >> http://issues.apache.org/jira/browse/IBATIS-152, solved in
> 2.1.5
> > > > > >>
> > > > > >> Is there any release plan for 2.1.5 so that I can decide
> whether or not
> > > > > >> I'll need to use 2.0.9b or compile the source?
> > > > > >>
> > > > > >> Thank you very much.
> > > > > >>
> > > > > >> --
> > > > > >> Guido García Bernardo - ggarciab@itdeusto.com
> > > > > >> Tfn. +34 983 54 89 08
> > > > > >> ITDEUSTO - Valladolid
> >
>
Re: ibatis 2.1.5 release plan
Posted by Larry Meadors <la...@gmail.com>.
OK, i just bopped into the irc channel, and there are no boxen to
actually *do* the builds on (unless we are using gump), only to hold
the results.
I have 6-8 boxes in my basement..I think one has a linux on it that i
can use to set up some stuff to get it going. So, do you think
ibatis.net will build on linux with mono and nant? If not i suppose I
can setup a winwoes box for you... ;-)
Larry
On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> There's plenty of hardware for things like this. It's just a matter of
> spending some quality time with infrastructure, preferably by IRC [and
> I think everyone knows how much I adore IRC :)].
>
> * http://apache.org/dev/infra-volunteer.html
>
> Several projects have their own zone on helios now:
>
> * http://apache.org/dev/machines.html
>
> -T.
>
> On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
> > That sounds reasonable to me. I would be more than willing to set up a
> > box to do the builds here if there is not one at apache to use.
> >
> > Does anyone know if there is one already?
> >
> > Larry
> >
> > On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > > All ASF projects are expected to provide automatic nightly builds. We
> > > just haven't gotten to around to that yet. The nightly builds live for
> > > seven days each, and then get recycled, so as to not eat up too much
> > > disk space.
> > >
> > > Any non-automatic release is generally tagged with a sequential
> > > version number. After someone rolls it, we vote on it's quality:
> > > Alpha, Beta, General Release. A release can start out as Alpha and
> > > work its way up to General Release as more people try it. A release
> > > can also be downgraded if a problem is found later.
> > >
> > > Of course, since the Subversion revision numbers are essentially tags,
> > > we could also snag any given nightly build (once we have them) and
> > > designate it "version #.#.#", making a note in our status file that
> > > version #.#.# corresponds to SVN revision ####.
> > >
> > > Later, if we ever need to branch, we can branch on a revision number
> > > as easily as a tag.
> > >
> > > -Ted.
> > >
> > > On 7/5/05, Sven Boden <li...@pandora.be> wrote:
> > > >
> > > > Not specific to the problem below. But what about providing iBATIS
> > > > development releases, e.g. after every big round of SVN changes. Most
> > > > other projects seem to do it.
> > > >
> > > > A few advantages I see:
> > > > - It's easier to tell people: "test with the development jar files"
> > > > than "extract the sources from SVN, compile and test"
> > > > - Better quality of releases as more people would already test/use the
> > > > development releases.
> > > > - Less "pressure" to release new versions.
> > > >
> > > > Regards,
> > > > Sven Boden
> > > >
> > > >
> > > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> > > >
> > > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
> > > > >go!
> > > > >
> > > > >Cheers,
> > > > >clinton
> > > > >
> > > > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > > > >>
> > > > >> Hi,
> > > > >>
> > > > >> I am facing with this bug:
> > > > >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
> > > > >>
> > > > >> Is there any release plan for 2.1.5 so that I can decide whether or not
> > > > >> I'll need to use 2.0.9b or compile the source?
> > > > >>
> > > > >> Thank you very much.
> > > > >>
> > > > >> --
> > > > >> Guido García Bernardo - ggarciab@itdeusto.com
> > > > >> Tfn. +34 983 54 89 08
> > > > >> ITDEUSTO - Valladolid
>
Re: ibatis 2.1.5 release plan
Posted by Ted Husted <te...@gmail.com>.
There's plenty of hardware for things like this. It's just a matter of
spending some quality time with infrastructure, preferably by IRC [and
I think everyone knows how much I adore IRC :)].
* http://apache.org/dev/infra-volunteer.html
Several projects have their own zone on helios now:
* http://apache.org/dev/machines.html
-T.
On 7/6/05, Larry Meadors <la...@gmail.com> wrote:
> That sounds reasonable to me. I would be more than willing to set up a
> box to do the builds here if there is not one at apache to use.
>
> Does anyone know if there is one already?
>
> Larry
>
> On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> > All ASF projects are expected to provide automatic nightly builds. We
> > just haven't gotten to around to that yet. The nightly builds live for
> > seven days each, and then get recycled, so as to not eat up too much
> > disk space.
> >
> > Any non-automatic release is generally tagged with a sequential
> > version number. After someone rolls it, we vote on it's quality:
> > Alpha, Beta, General Release. A release can start out as Alpha and
> > work its way up to General Release as more people try it. A release
> > can also be downgraded if a problem is found later.
> >
> > Of course, since the Subversion revision numbers are essentially tags,
> > we could also snag any given nightly build (once we have them) and
> > designate it "version #.#.#", making a note in our status file that
> > version #.#.# corresponds to SVN revision ####.
> >
> > Later, if we ever need to branch, we can branch on a revision number
> > as easily as a tag.
> >
> > -Ted.
> >
> > On 7/5/05, Sven Boden <li...@pandora.be> wrote:
> > >
> > > Not specific to the problem below. But what about providing iBATIS
> > > development releases, e.g. after every big round of SVN changes. Most
> > > other projects seem to do it.
> > >
> > > A few advantages I see:
> > > - It's easier to tell people: "test with the development jar files"
> > > than "extract the sources from SVN, compile and test"
> > > - Better quality of releases as more people would already test/use the
> > > development releases.
> > > - Less "pressure" to release new versions.
> > >
> > > Regards,
> > > Sven Boden
> > >
> > >
> > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> > >
> > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
> > > >go!
> > > >
> > > >Cheers,
> > > >clinton
> > > >
> > > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > > >>
> > > >> Hi,
> > > >>
> > > >> I am facing with this bug:
> > > >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
> > > >>
> > > >> Is there any release plan for 2.1.5 so that I can decide whether or not
> > > >> I'll need to use 2.0.9b or compile the source?
> > > >>
> > > >> Thank you very much.
> > > >>
> > > >> --
> > > >> Guido García Bernardo - ggarciab@itdeusto.com
> > > >> Tfn. +34 983 54 89 08
> > > >> ITDEUSTO - Valladolid
Re: ibatis 2.1.5 release plan
Posted by Larry Meadors <la...@gmail.com>.
That sounds reasonable to me. I would be more than willing to set up a
box to do the builds here if there is not one at apache to use.
Does anyone know if there is one already?
Larry
On 7/6/05, Ted Husted <te...@gmail.com> wrote:
> All ASF projects are expected to provide automatic nightly builds. We
> just haven't gotten to around to that yet. The nightly builds live for
> seven days each, and then get recycled, so as to not eat up too much
> disk space.
>
> Any non-automatic release is generally tagged with a sequential
> version number. After someone rolls it, we vote on it's quality:
> Alpha, Beta, General Release. A release can start out as Alpha and
> work its way up to General Release as more people try it. A release
> can also be downgraded if a problem is found later.
>
> Of course, since the Subversion revision numbers are essentially tags,
> we could also snag any given nightly build (once we have them) and
> designate it "version #.#.#", making a note in our status file that
> version #.#.# corresponds to SVN revision ####.
>
> Later, if we ever need to branch, we can branch on a revision number
> as easily as a tag.
>
> -Ted.
>
> On 7/5/05, Sven Boden <li...@pandora.be> wrote:
> >
> > Not specific to the problem below. But what about providing iBATIS
> > development releases, e.g. after every big round of SVN changes. Most
> > other projects seem to do it.
> >
> > A few advantages I see:
> > - It's easier to tell people: "test with the development jar files"
> > than "extract the sources from SVN, compile and test"
> > - Better quality of releases as more people would already test/use the
> > development releases.
> > - Less "pressure" to release new versions.
> >
> > Regards,
> > Sven Boden
> >
> >
> > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
> >
> > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
> > >go!
> > >
> > >Cheers,
> > >clinton
> > >
> > >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> > >>
> > >> Hi,
> > >>
> > >> I am facing with this bug:
> > >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
> > >>
> > >> Is there any release plan for 2.1.5 so that I can decide whether or not
> > >> I'll need to use 2.0.9b or compile the source?
> > >>
> > >> Thank you very much.
> > >>
> > >> --
> > >> Guido García Bernardo - ggarciab@itdeusto.com
> > >> Tfn. +34 983 54 89 08
> > >> ITDEUSTO - Valladolid
> > >>
> > >>
> > >>
> >
> >
>
>
> --
> HTH, Ted.
>
Re: ibatis 2.1.5 release plan
Posted by Ted Husted <te...@gmail.com>.
All ASF projects are expected to provide automatic nightly builds. We
just haven't gotten to around to that yet. The nightly builds live for
seven days each, and then get recycled, so as to not eat up too much
disk space.
Any non-automatic release is generally tagged with a sequential
version number. After someone rolls it, we vote on it's quality:
Alpha, Beta, General Release. A release can start out as Alpha and
work its way up to General Release as more people try it. A release
can also be downgraded if a problem is found later.
Of course, since the Subversion revision numbers are essentially tags,
we could also snag any given nightly build (once we have them) and
designate it "version #.#.#", making a note in our status file that
version #.#.# corresponds to SVN revision ####.
Later, if we ever need to branch, we can branch on a revision number
as easily as a tag.
-Ted.
On 7/5/05, Sven Boden <li...@pandora.be> wrote:
>
> Not specific to the problem below. But what about providing iBATIS
> development releases, e.g. after every big round of SVN changes. Most
> other projects seem to do it.
>
> A few advantages I see:
> - It's easier to tell people: "test with the development jar files"
> than "extract the sources from SVN, compile and test"
> - Better quality of releases as more people would already test/use the
> development releases.
> - Less "pressure" to release new versions.
>
> Regards,
> Sven Boden
>
>
> On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
>
> >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
> >go!
> >
> >Cheers,
> >clinton
> >
> >On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
> >>
> >> Hi,
> >>
> >> I am facing with this bug:
> >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
> >>
> >> Is there any release plan for 2.1.5 so that I can decide whether or not
> >> I'll need to use 2.0.9b or compile the source?
> >>
> >> Thank you very much.
> >>
> >> --
> >> Guido García Bernardo - ggarciab@itdeusto.com
> >> Tfn. +34 983 54 89 08
> >> ITDEUSTO - Valladolid
> >>
> >>
> >>
>
>
--
HTH, Ted.
Re: ibatis 2.1.5 release plan
Posted by Sven Boden <li...@pandora.be>.
Not specific to the problem below. But what about providing iBATIS
development releases, e.g. after every big round of SVN changes. Most
other projects seem to do it.
A few advantages I see:
- It's easier to tell people: "test with the development jar files"
than "extract the sources from SVN, compile and test"
- Better quality of releases as more people would already test/use the
development releases.
- Less "pressure" to release new versions.
Regards,
Sven Boden
On Tue, 5 Jul 2005 07:29:03 -0600, you wrote:
>As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
>go!
>
>Cheers,
>clinton
>
>On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
>>
>> Hi,
>>
>> I am facing with this bug:
>> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
>>
>> Is there any release plan for 2.1.5 so that I can decide whether or not
>> I'll need to use 2.0.9b or compile the source?
>>
>> Thank you very much.
>>
>> --
>> Guido García Bernardo - ggarciab@itdeusto.com
>> Tfn. +34 983 54 89 08
>> ITDEUSTO - Valladolid
>>
>>
>>
Re: ibatis 2.1.5 release plan
Posted by Clinton Begin <cl...@gmail.com>.
As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to
go!
Cheers,
clinton
On 7/5/05, Guido García Bernardo <gg...@itdeusto.com> wrote:
>
> Hi,
>
> I am facing with this bug:
> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5
>
> Is there any release plan for 2.1.5 so that I can decide whether or not
> I'll need to use 2.0.9b or compile the source?
>
> Thank you very much.
>
> --
> Guido García Bernardo - ggarciab@itdeusto.com
> Tfn. +34 983 54 89 08
> ITDEUSTO - Valladolid
>
>
>