[Padre-dev] Releasing regular 'developer' releases.
devel.chm.01 at gmail.com
Mon Sep 26 07:39:53 PDT 2011
The PDL project uses CPAN developers releases for
two main reasons:
(1) allow for CPAN Testers reports for added platforms
(2) allow non-developer users access to the latest features
Using CPAN Testers allows for regression and build testing
on platforms that we do not currently have active developers
using. This make possible broad, cross-platform portability
with some ability to verify progress.
The second point is to make up-to-date PDL releases available
for non-developer users (or for developers to don't have time to
keep up with or install the latest and greatest git/svn or other
infrastructure). For this to work, PDL must be capable of
being installed via CPAN. This can be an issue with some
components because of tricky dependencies that must be
installed to support PDL. The developers releases also allows
us to work through any stability and backwards compatibility
problems before an official release.
My experience with Padre is that it is still in a great deal
of flux so I'm not sure if developers releases would be
useful. It does have the advantage that someone installing
PDL via CPAN gets the latest, *stable* version and not
the developers release without special syntax. That would
allow you to have a semi-stable release as you currently
do and then the "this is going to break x, y, and z" ones
could be developers releases.
On Mon, Sep 26, 2011 at 4:32 AM, Peter Lavender <plaven at internode.on.net> wrote:
> Hi Everyone,
> I caught mention of doing developer releases for Padre:
> I know Ahmad uses this a lot, we saw it plenty with the Wx::Scintilla
> development process.
> What do people think of doing this with Padre itself?
> I'm happy to do this, but I do have a concern or two about the perception of
> Padre itself, the main one being, do we risk damaging its profile if a
> number of releases hit CPAN that aren't so stable, or cause people a lot of
> Many of the big changes we wait on before a release generally come down to
> which API is being worked on and how long it takes to get it back to stable
> enough for a release.
> I can see why currently doing a developer release or two does make it simple
> enough for people to install from CPAN, but then for most developers it's
> not that hard to svn checkout and make the project, but of course anything
> that lowers the barriers for a wider audience is always a good thing to get
> early feedback.
> So basically I guess I can see both arguments here, so for my part, I don't
> care, I'll happily roll out a a few developer releases before a "major"
> stable release to see things like the diff work that Ahmad has added to
> The big thing though is picking a natural 'stable enough' point to branch
> and release while other parts are being worked on.
> Padre-dev mailing list
> Padre-dev at perlide.org
More information about the Padre-dev