mysql-proxy-discuss team mailing list archive

[Kay Röpke <Kay.Roepke@xxxxxxx>]

Hi Nick!

On Feb 22, 2009, at 12:40 PM, nick loeve wrote:

> I like the idea of major and minor releases, especially if they are
> based on small incremental changes in order to make them somewhat
> timely.
> I don't think you need to have the overhead of different alpha, beta,
> RCs "subreleases". If you have daily/weekly/etc automatic tagged
> tarballs/builds then they can play a similar role, and it can be less
> confusing.

Yes, I was wondering about that, too, after I wrote the mail.
I probably can hack a snapshot system together that would publish the  
dist tarball
regularly, say every two weeks or so.

Right now I'm working to get the Launchpad branch to build on our  
internal build
system on every push to the lp:mysql-proxy tree. I haven't figured out  
what the best
way to publish results are, as the build system isn't accessible from  
the outside world
but probably that's ok for now.

Then when ramping up to a point release (0.x.y) we could do an RC  
which would
be accompanied by binary builds, the snapshots would be source only  
(output of `make dist`).

> I personally don't need the binaries, but that sounds like a good  
> idea.


Binaries are a hassle, but necessary to get wider usage. Many folks do  
not want to
set up all the dependencies themselves. (Which really is the main  
reason that binaries
are a hassle - we need to include all the dependent libraries for it  
to be useful).
This system isn't fully set up yet.

cheers,
-k
--
Kay Roepke
Software Engineer, MySQL Enterprise Tools

Sun Microsystems GmbH    Sonnenallee 1, DE-85551 Kirchheim-Heimstetten
Geschaeftsfuehrer: Thomas Schroeder, Wolfang Engels, Dr. Roland Boemer
Vorsitz d. Aufs.rat.: Martin Haering                    HRB MUC 161028