Tao build release

[C.J. Adams-Collier]

23:24 < jhurliman> cj_, the last Tao release is almost a year old, yet there is
                   svn activity all the way up to today. is a new release going
                   to be planned?

Sure, we could push one of those out in the next month or so.  Let me
meet with the team and get a build verification test in place.  As
you've noticed, we don't have GA releases often, so we need to put some
infrastructure in place.  Do you know any testers we could slurp up for
a month or so for QA verification?

Cheers,

C.J.



_______________________________________________
Tao-list mailing list
Tao-list@...
http://galactus.ximian.com/mailman/listinfo/tao-list

[Terry L. Triplett-2]

Actually, the recent SVN activity is indicative of work to get the bindings updated to support .NET 2.0 (with loss of .NET 1.1 support) and various other things, like a pretty substantial reworking of Tao.OpenGL.  The reason you haven't seen a release is because there is still work going on - a release will be ready "when it's done".  The end seems to be in sight, though.

FWIW, many of the bindings have been ready for an updated release for awhile now, but have been languishing while they wait for *all* the bindings to be ready.  Discussion recently has turned toward moving to a separate "release" for each binding, since they evolve independently from each other (depending on maintainer energy, upstream activity and the like).  Tying all the bindings together into one big meta release never made much sense - there is little direct coupling between the bindings other than sharing the name "Tao".  Periodically (based on some criterion as yet unspecified) a bundled 'convenience' release would be pushed out, bundling all the bindings in one nifty package.

On 10/5/06, C.J. Adams-Collier <cjcollier@...> wrote:

23:24 < jhurliman> cj_, the last Tao release is almost a year old, yet there is
                   svn activity all the way up to today. is a new release going
                   to be planned?

Sure, we could push one of those out in the next month or so.  Let me
meet with the team and get a build verification test in place.  As
you've noticed, we don't have GA releases often, so we need to put some
infrastructure in place.  Do you know any testers we could slurp up for
a month or so for QA verification?

Cheers,

C.J.



_______________________________________________
Tao-list mailing list
Tao-list@...
http://galactus.ximian.com/mailman/listinfo/tao-list

_______________________________________________
Tao-list mailing list
Tao-list@...
http://galactus.ximian.com/mailman/listinfo/tao-list

[C.J. Adams-Collier]

Cool.  I'll take the reins on the mono release.  I like the idea of
having releases of each package separately and every now and then having
a meta release.

On Thu, 2006-05-10 at 15:12 -0400, Terry L. Triplett wrote:

> Actually, the recent SVN activity is indicative of work to get the
> bindings updated to support .NET 2.0 (with loss of .NET 1.1 support)
> and various other things, like a pretty substantial reworking of
> Tao.OpenGL.  The reason you haven't seen a release is because there is
> still work going on - a release will be ready "when it's done".  The
> end seems to be in sight, though.
>
> FWIW, many of the bindings have been ready for an updated release for
> awhile now, but have been languishing while they wait for *all* the
> bindings to be ready.  Discussion recently has turned toward moving to
> a separate "release" for each binding, since they evolve independently
> from each other (depending on maintainer energy, upstream activity and
> the like).  Tying all the bindings together into one big meta release
> never made much sense - there is little direct coupling between the
> bindings other than sharing the name "Tao".  Periodically (based on
> some criterion as yet unspecified) a bundled 'convenience' release
> would be pushed out, bundling all the bindings in one nifty package.
>
> On 10/5/06, C.J. Adams-Collier <cjcollier@...> wrote:
>         23:24 < jhurliman> cj_, the last Tao release is almost a year
>         old, yet there is
>                            svn activity all the way up to today. is a
>         new release going
>                            to be planned?
>        
>         Sure, we could push one of those out in the next month or
>         so.  Let me
>         meet with the team and get a build verification test in
>         place.  As
>         you've noticed, we don't have GA releases often, so we need to
>         put some
>         infrastructure in place.  Do you know any testers we could
>         slurp up for
>         a month or so for QA verification?
>        
>         Cheers,
>        
>         C.J.
>        
>        
>        
>         _______________________________________________
>         Tao-list mailing list
>         Tao-list@...
>         http://galactus.ximian.com/mailman/listinfo/tao-list
>        
>        
>        
>
> _______________________________________________
> Tao-list mailing list
> Tao-list@...
> http://galactus.ximian.com/mailman/listinfo/tao-list

_______________________________________________
Tao-list mailing list
Tao-list@...
http://galactus.ximian.com/mailman/listinfo/tao-list

[Terry L. Triplett-2]

Indivudual releases make much more sense from the Linux perspective, given how most distributions calculate dependencies.  Despite the cross-platform committment of Tao, the user base and (to a lesser extent) the developer base have been predominantly Windows oriented, so this never got taken into account.  On my Gentoo box, for example, I have a set of custom ebuilds for each Tao binding, each of which in turn depends on the package for the upstream native library.  This makes the dependency structure much simpler and allows someone to install only the Tao binding they are interested in rather than having to pull in the whole thing.

One thing that would be nice to do for the next release is to finish what Dave Hudson started with Tao.Sdl and flesh out each binding with a dll-mapping config for each distribution.  Things are fairly consistent between distros, but the name of the native library still varies a bit.  This way, downstream packagers for each distribution can easily reference the appropriate Tao.Assembly.dll.config file for installation.

I'm busying playing catchup on another project right now, but I'm hoping to test the latest stuff in SVN on my system.  As mentioned above, most development seems to be windows-centric, so there are some problems on Mono/Linux that need to be resolved.  I was going to start a thread on the forums detailing the issues once I had some hard data.

On 10/5/06, C.J. Adams-Collier <cjcollier@...> wrote:

Cool.  I'll take the reins on the mono release.  I like the idea of
having releases of each package separately and every now and then having
a meta release.

On Thu, 2006-05-10 at 15:12 -0400, Terry L. Triplett wrote:

> Actually, the recent SVN activity is indicative of work to get the
> bindings updated to support .NET 2.0 (with loss of .NET 1.1 support)
> and various other things, like a pretty substantial reworking of
> Tao.OpenGL.  The reason you haven't seen a release is because there is
> still work going on - a release will be ready "when it's done".  The
> end seems to be in sight, though.
>
> FWIW, many of the bindings have been ready for an updated release for
> awhile now, but have been languishing while they wait for *all* the
> bindings to be ready.  Discussion recently has turned toward moving to
> a separate "release" for each binding, since they evolve independently
> from each other (depending on maintainer energy, upstream activity and
> the like).  Tying all the bindings together into one big meta release
> never made much sense - there is little direct coupling between the
> bindings other than sharing the name "Tao".  Periodically (based on
> some criterion as yet unspecified) a bundled 'convenience' release
> would be pushed out, bundling all the bindings in one nifty package.
>
> On 10/5/06, C.J. Adams-Collier <cjcollier@...> wrote:
>         23:24 < jhurliman> cj_, the last Tao release is almost a year

>         old, yet there is

>                            svn activity all the way up to today. is a
>         new release going
>                            to be planned?
>
>         Sure, we could push one of those out in the next month or
>         so.  Let me
>         meet with the team and get a build verification test in
>         place.  As
>         you've noticed, we don't have GA releases often, so we need to
>         put some
>         infrastructure in place.  Do you know any testers we could
>         slurp up for
>         a month or so for QA verification?
>
>         Cheers,
>
>         C.J.
>
>
>
>         _______________________________________________
>         Tao-list mailing list
>         Tao-list@...
>         http://galactus.ximian.com/mailman/listinfo/tao-list
>
>
>
>
> _______________________________________________
> Tao-list mailing list
> Tao-list@...
> http://galactus.ximian.com/mailman/listinfo/tao-list

_______________________________________________
Tao-list mailing list
Tao-list@...
http://galactus.ximian.com/mailman/listinfo/tao-list

[C.J. Adams-Collier]

Concur.

The changes can be completed whenever.  I'd like to plan a release
independent of the developers' completion of their projects.  I don't
think that developers should need to keep track of when releases happen.
SVN head should always build, continuous integration builds should never
fail, and unit tests should always pass.  Provided that all of these
requisites hold true, it should be fine to make releases at pre-defined
intervals.

Cheers,

C.J.


On Thu, 2006-05-10 at 15:57 -0400, Terry L. Triplett wrote:

> Indivudual releases make much more sense from the Linux perspective,
> given how most distributions calculate dependencies.  Despite the
> cross-platform committment of Tao, the user base and (to a lesser
> extent) the developer base have been predominantly Windows oriented,
> so this never got taken into account.  On my Gentoo box, for example,
> I have a set of custom ebuilds for each Tao binding, each of which in
> turn depends on the package for the upstream native library.  This
> makes the dependency structure much simpler and allows someone to
> install only the Tao binding they are interested in rather than having
> to pull in the whole thing.
>
> One thing that would be nice to do for the next release is to finish
> what Dave Hudson started with Tao.Sdl and flesh out each binding with
> a dll-mapping config for each distribution.  Things are fairly
> consistent between distros, but the name of the native library still
> varies a bit.  This way, downstream packagers for each distribution
> can easily reference the appropriate Tao.Assembly.dll.config file for
> installation.
>
> I'm busying playing catchup on another project right now, but I'm
> hoping to test the latest stuff in SVN on my system.  As mentioned
> above, most development seems to be windows-centric, so there are some
> problems on Mono/Linux that need to be resolved.  I was going to start
> a thread on the forums detailing the issues once I had some hard
> data.
>
> On 10/5/06, C.J. Adams-Collier <cjcollier@...> wrote:
>         Cool.  I'll take the reins on the mono release.  I like the
>         idea of
>         having releases of each package separately and every now and
>         then having
>         a meta release.
>        
>         On Thu, 2006-05-10 at 15:12 -0400, Terry L. Triplett wrote:
>         > Actually, the recent SVN activity is indicative of work to
>         get the
>         > bindings updated to support .NET 2.0 (with loss of .NET 1.1
>         support)
>         > and various other things, like a pretty substantial
>         reworking of
>         > Tao.OpenGL.  The reason you haven't seen a release is
>         because there is
>         > still work going on - a release will be ready "when it's
>         done".  The
>         > end seems to be in sight, though.
>         >
>         > FWIW, many of the bindings have been ready for an updated
>         release for
>         > awhile now, but have been languishing while they wait for
>         *all* the
>         > bindings to be ready.  Discussion recently has turned toward
>         moving to
>         > a separate "release" for each binding, since they evolve
>         independently
>         > from each other (depending on maintainer energy, upstream
>         activity and
>         > the like).  Tying all the bindings together into one big
>         meta release
>         > never made much sense - there is little direct coupling
>         between the
>         > bindings other than sharing the name "Tao".  Periodically
>         (based on
>         > some criterion as yet unspecified) a bundled 'convenience'
>         release
>         > would be pushed out, bundling all the bindings in one nifty
>         package.
>         >
>         > On 10/5/06, C.J. Adams-Collier <cjcollier@...>
>         wrote:
>         >         23:24 < jhurliman> cj_, the last Tao release is
>         almost a year
>         >         old, yet there is
>         >                            svn activity all the way up to
>         today. is a
>         >         new release going
>         >                            to be planned?
>         >
>         >         Sure, we could push one of those out in the next
>         month or
>         >         so.  Let me
>         >         meet with the team and get a build verification test
>         in
>         >         place.  As
>         >         you've noticed, we don't have GA releases often, so
>         we need to
>         >         put some
>         >         infrastructure in place.  Do you know any testers we
>         could
>         >         slurp up for
>         >         a month or so for QA verification?
>         >
>         >         Cheers,
>         >
>         >         C.J.
>         >
>         >
>         >
>         >         _______________________________________________
>         >         Tao-list mailing list
>         >         Tao-list@...
>         >         http://galactus.ximian.com/mailman/listinfo/tao-list
>         >
>         >
>         >
>         >
>         > _______________________________________________
>         > Tao-list mailing list
>         > Tao-list@...
>         > http://galactus.ximian.com/mailman/listinfo/tao-list
>        
>        
>

_______________________________________________
Tao-list mailing list
Tao-list@...
http://galactus.ximian.com/mailman/listinfo/tao-list