FAQ
What would need to be done to make it easy to push a button and release new
dev version of M::B?

I've already added a dev tool to update $VERSION everywhere except where we
don't want it (where we're tracking shadow modules from elsewhere).

I know there is a .releaserc but it references Module::Release::KWILLIAMS.

If that's the way to go, then I'd like to have it put into devtools/lib so
Eric or other designated people can use it. (Plus we can hack on it.)
Alternatively, we could come up with a custom script to do whatever checks
are necessary, branch and tag the repo appropriately, and prepare a release
tarball for upload.

Ultimately, I think we'd benefit from a faster dev release cycle on M::B and
I think automating the hard parts of a release will be a significant step
towards making that happen.

-- David

Search Discussions

  • Eric Wilhelm at Jan 26, 2009 at 5:06 pm
    # from David Golden
    # on Monday 26 January 2009 07:34:
    I know there is a .releaserc but it references
    Module::Release::KWILLIAMS.
    There is also a ".perl_developer.yml", which drives publish_module, and
    is what I use. I always relay to my webserver with scp and then push
    the http:// link to pause. I've yet to get any input from others on
    this though.

    http://scratchcomputing.com/svn/CPDK/trunk

    --Eric
    --
    "Politics is not a bad profession. If you succeed there are many
    rewards, if you disgrace yourself you can always write a book."
    --Ronald Reagan
    ---------------------------------------------------
    http://scratchcomputing.com
    ---------------------------------------------------
  • David Golden at Jan 26, 2009 at 5:23 pm
    How far is CDPK from release to CPAN? I'd like to either stick to published
    tools or else embed everything we need into devtools/lib

    -- David

    On Mon, Jan 26, 2009 at 12:06 PM, Eric Wilhelm
    wrote:
    # from David Golden
    # on Monday 26 January 2009 07:34:
    I know there is a .releaserc but it references
    Module::Release::KWILLIAMS.
    There is also a ".perl_developer.yml", which drives publish_module, and
    is what I use. I always relay to my webserver with scp and then push
    the http:// link to pause. I've yet to get any input from others on
    this though.

    http://scratchcomputing.com/svn/CPDK/trunk

    --Eric
    --
    "Politics is not a bad profession. If you succeed there are many
    rewards, if you disgrace yourself you can always write a book."
    --Ronald Reagan
    ---------------------------------------------------
    http://scratchcomputing.com
    ---------------------------------------------------
  • Eric Wilhelm at Jan 26, 2009 at 5:37 pm
    # from David Golden
    # on Monday 26 January 2009 09:22:
    How far is CDPK from release to CPAN?  I'd like to either stick to
    published tools or else embed everything we need into devtools/lib
    As far as I'm concerned, my svn is "published". The holdup re: turning
    it on itself is only that I've yet to get any input from others on what
    sort of documentation it needs to be usable.

    http://scratchcomputing.com/svn/CPDK/trunk

    --Eric
    --
    "But as to modern architecture, let us drop it and let us take
    modernistic out and shoot it at sunrise."
    --F.L. Wright
    ---------------------------------------------------
    http://scratchcomputing.com
    ---------------------------------------------------
  • David Golden at Jan 26, 2009 at 10:37 pm

    On Mon, Jan 26, 2009 at 12:36 PM, Eric Wilhelm wrote:

    As far as I'm concerned, my svn is "published". The holdup re: turning
    it on itself is only that I've yet to get any input from others on what
    sort of documentation it needs to be usable.

    http://scratchcomputing.com/svn/CPDK/trunk
    I think it needs a cookbook, to start. And probably the main CPDK module
    needs to have 'getting started' guide, by topic (e.g. "starting a new
    distribution" and "publishing a new distribution").

    It's just not clear what the hell I do with it. Make a config file of some
    sort, right? What do I put into it? Why one thing or another? Do I have to
    hand-generate it? Or can I autogenerate a default?

    Just listing the API with so little detail isn't really that helpful. I
    think you need to give examples of usage for each one, both programmatically
    and as it would be used in the config file.

    Will it work on any distribution, even ones I didn't create with CPDK? Or
    is there something specific about the way CPDK lays out files that I need to
    know about? (E.g. Changes have version + date on line 3).

    Does it support git?

    And -- FWIW, the requirements in Build.PL seem to be missing stuff. What
    the heck is VCfs?

    -- David
  • Ron Savage at Jan 27, 2009 at 12:15 am
    Hi David
    And -- FWIW, the requirements in Build.PL seem to be missing stuff. What
    the heck is VCfs?
    CPAN is your friend!

    Search this page for VCF:

    http://search.cpan.org/~llap/Text-vCard-2.03/lib/Text/vCard/Addressbook.pm

    Hint: A vCard is a virtual business card.

    See also: http://microformats.org/

    --
    Ron Savage
    ron@savage.net.au
    http://savage.net.au/index.html
  • David Golden at Jan 27, 2009 at 3:49 am

    On Mon, Jan 26, 2009 at 7:16 PM, Ron Savage wrote:

    Hi David
    And -- FWIW, the requirements in Build.PL seem to be missing stuff. What
    the heck is VCfs?
    CPAN is your friend!

    Search this page for VCF:

    http://search.cpan.org/~llap/Text-vCard-2.03/lib/Text/vCard/Addressbook.pm<http://search.cpan.org/%7Ellap/Text-vCard-2.03/lib/Text/vCard/Addressbook.pm>
    <grin> I got a good chuckle out of that response. And I think I've
    actually used that module at some point in the past, too.

    Hopefully from Eric's reply you'll see that it was VCfs I was questioning,
    as in "use VCfs;" which from context is some sort of abstraction of a
    "Version Control File System".

    -- David
  • Ron Savage at Jan 27, 2009 at 5:46 am
    Hi David

    Hopefully from Eric's reply you'll see that it was VCfs I was
    questioning, as in "use VCfs;" which from context is some sort of
    abstraction of a "Version Control File System".
    Version Control!?

    Damn. Something else I have to learn about :-))).

    --
    Ron Savage
    ron@savage.net.au
    http://savage.net.au/index.html
  • Eric Wilhelm at Jan 27, 2009 at 12:16 am
    # from David Golden
    # on Monday 26 January 2009 14:37:
    It's just not clear what the hell I do with it. Make a config file of
    some sort, right? What do I put into it? Why one thing or another? Do
    I have to hand-generate it? Or can I autogenerate a default?
    You need to hand-edit your ~/.perl_developer.yml for setting-up your
    pause permissions and so on. Presently, the upload only supports an
    scp+http scheme.
    Will it work on any distribution,  even ones I didn't create with
    CPDK?  Or is there something specific about the way CPDK lays out
    files that I need to know about?  (E.g. Changes have version + date
    on line 3).
    The expectations might be somewhat specific in places, but you can
    certainly turn off the actions or replace them with your own ./Build
    actions. It's certainly designed to let you pick your own set of
    sanity checks, but if your sanity differs from mine, you have to write
    something to do the check.

    It does work for M::B.
    Does it support git?
    Not as written. I haven't gotten into the details of whether it would
    be better to have a cpdk-specific adaptor or try to make VCfs handle
    that.
    And -- FWIW, the requirements in Build.PL seem to be missing stuff.
    Ah. You might need to look sideways in the svn for parts of this at the
    moment.
    What the heck is VCfs?
    An svn/svk agnostic object. This might have been surpassed by something
    on the CPAN in the last couple years.

    Thanks,
    Eric
    --
    To a database person, every nail looks like a thumb.
    --Jamie Zawinski
    ---------------------------------------------------
    http://scratchcomputing.com
    ---------------------------------------------------
  • David Golden at Jan 27, 2009 at 3:54 am

    On Mon, Jan 26, 2009 at 7:15 PM, Eric Wilhelm wrote:

    And -- FWIW, the requirements in Build.PL seem to be missing stuff.
    Ah. You might need to look sideways in the svn for parts of this at the
    moment.
    I think that's an example of what concerns me. I'd like to avoid a
    situation where we have:

    .kens-release-system-rc
    .erics-release-system-rc
    .davids-release-system-rc
    etc.

    and each depends on something that is only available locally and each has
    slightly different semantics.

    --David
  • Eric Wilhelm at Jan 27, 2009 at 6:25 am
    # from David Golden
    # on Monday 26 January 2009 19:54:
    Ah.  You might need to look sideways in the svn for parts of this at
    the moment.
    I think that's an example of what concerns me.
    Well, I'm not getting anything done talking about it, but I'm not
    convinced that it will get easier to setup solely by putting it on the
    cpan. Nonetheless, I can certainly add it all to my stack of things
    which need to get polished and shipped.
    I'd like to avoid a situation where we have:

    .kens-release-system-rc
    .erics-release-system-rc
    .davids-release-system-rc
    That would be nice to avoid. If you want to try to replicate Ken's
    setup, maybe that works.

    In any case, this seems a bit of a red herring. Shipping the release
    takes me one command and less than 5 minutes. Knowing that M::B is
    ready to ship takes quite a bit longer. Setting up your machine with
    CPDK might take less time than the discussion if you tell me where you
    get stuck.

    --Eric
    --
    Turns out the optimal technique is to put it in reverse and gun it.
    --Steven Squyres (on challenges in interplanetary robot navigation)
    ---------------------------------------------------
    http://scratchcomputing.com
    ---------------------------------------------------
  • David Golden at Jan 27, 2009 at 11:36 am

    On Tue, Jan 27, 2009 at 1:24 AM, Eric Wilhelm wrote:
    Well, I'm not getting anything done talking about it, but I'm not
    convinced that it will get easier to setup solely by putting it on the
    cpan. Nonetheless, I can certainly add it all to my stack of things
    which need to get polished and shipped.
    You said the thing that was holding you up on releasing it to CPAN was
    feedback on what needs to be documented. And I gave you some. If the real
    problem is the lack of round tuits, I empathize. My list of "wish I had
    time to do X" is long too.

    That would be nice to avoid. If you want to try to replicate Ken's
    setup, maybe that works.
    Ken -- if you're reading this, could you please put
    Module::Release::KWILLIAMS in devtools/lib?

    In any case, this seems a bit of a red herring. Shipping the release
    takes me one command and less than 5 minutes. Knowing that M::B is
    ready to ship takes quite a bit longer. Setting up your machine with
    CPDK might take less time than the discussion if you tell me where you
    get stuck.
    (sigh) Yes -- and if someone *else* has the time to figure out if M::B is
    ready to ship, they don't have your one command and 5 minutes without a lot
    of yak shaving. Thus we risk a bottleneck on the dev release cycle which
    means it takes longer to get feedback on changes, releases have more
    accumulated changes in them when we do release so it's harder to isolate
    which changes cause further problems and so on. That's my point.

    I'm not critiquing your release tool as a useful tool -- apart from the
    feedback on documentation needs you asked for -- but I am arguing it would
    be good to be able to spread the work around if that can help speed up the
    release cycle.

    So "in any case" -- I've added some fixes for the
    Windows-loaded-system-virus-checker heisenbug and added some diagnostics to
    ensure_blib so we can figure out why the heck we're getting blib failures on
    a number of systems. Could you please take the 5 minutes to push out an
    alpha so we can get CPAN Testers to beat on it and get some idea what's
    behind the ensure_blib failures that we've been getting?

    Thank you,

    David
  • Ken Williams at Jan 29, 2009 at 3:52 am

    On Tue, Jan 27, 2009 at 5:35 AM, David Golden wrote:
    Ken -- if you're reading this, could you please put
    Module::Release::KWILLIAMS in devtools/lib?
    Done.

    Please note the unfortunate fact that I still have version 1.20 of
    Module::Release on my system, so it's unlikely that M::R::KWILLIAMS
    will work with the newer M::R 2.01.

    -Ken

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmodule-build @
categoriesperl
postedJan 26, '09 at 3:34p
activeJan 29, '09 at 3:52a
posts13
users5
websitecpan.org...

People

Translate

site design / logo © 2017 Grokbase