On Mon, Nov 10, 2008 at 06:50:58PM -0500, Ricardo SIGNES wrote:
> * Paul Johnson <[EMAIL PROTECTED]> [2008-11-10T17:17:22]
> > I'm starting to get annoyed by the extraneous commits into the revision
> > control system. And so I'm considering the option of not having the version
> > number in the f
* Paul Johnson <[EMAIL PROTECTED]> [2008-11-10T17:17:22]
> I'm starting to get annoyed by the extraneous commits into the revision
> control system. And so I'm considering the option of not having the version
> number in the file that gets checked in, but expanding it for a release.
Using Dist::Z
On Mon, Nov 10, 2008 at 04:43:27PM -0500, Ricardo SIGNES wrote:
> * Jonas Brømsø Nielsen <[EMAIL PROTECTED]> [2008-11-10T16:15:20]
> > I like to be able to release distributions without necessarily
> > touching a code module, if changes are just documentation, tests or
> > other files. I only u
On Mon, Nov 10, 2008 at 11:43 PM, Ricardo SIGNES
<[EMAIL PROTECTED]> wrote:
> * Jonas Brømsø Nielsen <[EMAIL PROTECTED]> [2008-11-10T16:15:20]
>> I like to be able to release distributions without necessarily
>> touching a code module, if changes are just documentation, tests or
>> other files. I o
* Jonas Brømsø Nielsen <[EMAIL PROTECTED]> [2008-11-10T16:15:20]
> I like to be able to release distributions without necessarily
> touching a code module, if changes are just documentation, tests or
> other files. I only update package versions when code/functionality
> changes, so developer
Hello Module Authors,
I have received a RT ticket on my Workflow distribution.
The RT raises an issue with the distribution version number not being
equal to the one in the main package version, in my case Workflow.pm
I like to be able to release distributions without necessarily
touching