I don't think it's a problem. It's posted in the right place -- as soon as I saw this node I checked Perl News, and there it was.

I don't know about anyone else's voting habits, but I tend not to vote on news or announcements, if that's what you meant by 'self-aggrandizement'. Making "There's a new version" be a reply to the 1.0 node means only the sharp-eyed folks watching the Newest Nodes page would catch the announcement.

{NULE}
--
http://www.nule.org

My definition of newsworthy has nothing to do with it. I've already stated elsewhere that I don't believe Perl News should exist, but that's irrelevant. The point was there's already a node for this code, so in the interest of information management modifications and updates belong there. And yes the double-dipping refers to XP. Saint or not I always care about "fair".

--
I'm not belgian but I play one on TV.

I don't see the issue. In fact I don't mind it as I can hear about new modules that I normally would not have known about.

If this new version introduces something real important worth reporting on, then by all means, report it, otherwise, kindly clam up.

It's like announcing there is a new version of PAR out (New PAR on CPAN). That's what http://search.cpan.org/recent/ is for (also found in your CPAN Nodelets)

If the monks like, i'll be glad to stop by Perl News every day and write a few "There's a new version of module X on CPAN. Go get it." nodes.
Would anyone like that? Didn't think so.

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! ** The Third rule of perl club is a statement of fact: pod is sexy.

I would really like this, would you mind doing it? This way i have a much easier time finding out about new and improved modules that could potentially make my life easier. I suppose as a worst case condition i might *Gasp* have to read 3-4 more lines at the bottom of "Newest Nodes". Dear god, i'm sure the horror and chaos that would ensue from something like that would be utterly devestating to this amazing community we've established here.

If the monks like, i'll be glad to stop by Perl News every day and write a few "There's a new version of module X on CPAN. Go get it." nodes.
Would anyone like that? Didn't think so.

Or you could actually be productive and write a system that once a day checks CPAN for new module releases, lists them in a single post in Perl Announcements, and allows users to rate whether or not the given module is important enough to be listed in there.

Or you could keep bitching and mocking other's suggestions. Your call.

Yes I could, if I liked the idea. I don't.

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! ** The Third rule of perl club is a statement of fact: pod is sexy.

Hm. I'd tend to say that if you wanted to publish somthing, and make sure people can get new versions and suchlike, use CPAN, Freshmeat, sourceforge, or write a web page. Don't use a node on PM. PM is good for discussion, but terrible as a medium for releasing software.

I'd say that new versions of software should be announced on Perl News for /major/ things, things with major changes, and PM-related software. If a new major release of DBI comes out, tell us. If a new release of perl comes out, tell us. If a new version of PerlMonks comes out, tell us. Don't tell us that tinyperl 1.1 is out, with -128k of new features.

That's really not a problem, we cannot regulate everything, especially when there is absolutely no need.

it is almost impossible for anyone to notice this new revision.

Without taking a stand on the original point, I'd like to point out that this is only true for the people who peruse just the The Monastery Gates, a crowd that's unfortunately going to miss a lot of what's happening at the site. People who navigate the site using Newest Nodes or a client for the corresponding XML ticker (as I do) will most certainly notice follow-up announcements posted as replies.

Makeshifts last the longest.

I don't check here very often, so "Newest nodes" are too ephemeral for me.

Unless someone has replied to one of my nodes, how can I know the discussion has been updated?

If we had a "subscribe to this node for update notifications" feature, then I'd agree that 1.1-style notices should go in as replies to the old node, but as the site stands, I'm glad that update was a top-level node, where I'm more likely to see it.

That being said, I still ++'d your node, it seems like a reasonable point to discuss. It's a bit odd that it stands at -7 XP atm, but I understand we all have very different up/downvote criteria...
--
Mike

This irks me to no end. It seems like unnecessary self aggrandizement

Your attitude is far more harmful. In my opinion, there should be about 50 posts in Perl Announcements a day, it would add a lot more value to the site. Your suppression of information based on the warped perspective that only the very most important info should be posted does far more damage. Your attempt to maintain your precious database "integrity" is a joke.

As for reasons to allow more small announcements try: it adds awareness to to smaller projects, provides publicity for alternatives and prevents people from all using the same bloated code (e.g. CGI.pm), encourages a open discussion of the merits of any given approach, etc etc, etc.

Have you no knowledge of open development processes?

You distort my message. I spoke not of data bloat but integrity. And I never said anything about "importance". Please do not put words in my mouth. Furthermore other sites serve some of the purposes you seem to feel I was attacking, though I was not, far better eg; http://use.perl.org and http://freshmeat.net.

UPDATE: Perhaps fellow monks might better understand the message if the substituted "false hubris" for "self aggrandizement". Although I believe the latter is more accurate.

--
I'm not belgian but I play one on TV.

I saw ...

... but it really irks me

This irks me to no end

I think ...

... unnecessary self aggrandizement ...