* David Golden x...@xdg.me [2015-05-19 19:26]:
I've created devel branches for several of the dists I maintain. I'd
like to leave master for things that ship, so that, for example,
I can ship a stable release after a trial by shipping master.
I tried this in several projects, esp. including at
On 20 May 2015 at 00:55, James E Keenan jk...@verizon.net wrote:
On 05/19/2015 10:51 AM, David Golden wrote:
I have tuits today to ship my various TRIAL dists and keep an eye on them.
Ideally, I wouldn't do them all in close succession, but my tuit supply is
lumpy.
I must have missed some
2015-05-20 1:55 GMT+02:00 James E Keenan jk...@verizon.net:
On 05/19/2015 10:51 AM, David Golden wrote:
I have tuits today to ship my various TRIAL dists and keep an eye on them.
Ideally, I wouldn't do them all in close succession, but my tuit supply is
lumpy.
I must have missed some
I have tuits today to ship my various TRIAL dists and keep an eye on them.
Ideally, I wouldn't do them all in close succession, but my tuit supply is
lumpy.
* CPAN-Meta-YAML -- shipped this morning already
* Parse-CPAN-Meta
* CPAN-Meta
* CPAN-Meta-Requirements
Please keep an eye out for any
I've created devel branches for several of the dists I maintain. I'd
like to leave master for things that ship, so that, for example, I can
ship a stable release after a trial by shipping master.
Other development work can go live on devel (or topic branches) while we
wait for TRIAL releases to
On 05/19/2015 07:23 PM, David Golden wrote:
As it turns out, my tuits mostly went to shipping *NEW* trial
distributions for various reasons:
* Parse-CPAN-Meta -- fix a spurious 5.10 prereq
* CPAN-Meta -- release with changes since last release
* CPAN-Meta-Requirements -- changes to get tests
6 matches
Mail list logo
