On Tuesday 11 October 2011 22:11:15 Buddy Burden wrote:
> Guys,
>
> So, I found a bug in a CPAN module that hadn't been updated in some
> time. After I submitted a bug in RT, I checked the author's other
> modules and his RT tickets: no activity in years. So I sent the
> author an email, and said, hey, if you don't want to mess with this
> module any more, I'd be happy to take it over for you. And, voila,
> I'm now the proud(?) maintainer of Data::Random.
>
> So I need to create a repo for the code, and it would be nice to start
> with the previous versions, right?
Out of interest, did you try asking the original author whether he has a repo
knocking around he'd be willing to share with you, so you can maintain
history?
If not, you could probably cherry-pick commits from gitpan to your new repo to
get the previous releases there.
I'm not entirely sure that would be worth the effort, though; there's only 4
prior releases, and the real value in having the history in version control is
commit messages with explanations of decisions made and stuff, which you won't
have if you just have the snapshots of releases from gitpan.
Personally, I think I'd just import the current version into your new repo,
with a commit message making it clear that this is the current state of the
module and that you're taking over maintainership, then go from there. (and
that previous versions are of course available from backpan or gitpan, for
anyone who is interested)
Cheers
Dave P
--
David Precious ("bigpresh")
http://www.preshweb.co.uk/
"Programming is like sex. One mistake and you have to support
it for the rest of your life". (Michael Sinz)
