roman at kennke.org
Fri Mar 14 11:40:46 PDT 2008
> Once the initial flurry of pushes for the jcheck configuration file that
> was needed in each and every repository blew past (sorry about that),
> we've seen 61 pushes of actual code into the various JDK 7 development
Yeah, that is very nice. Finally we can see what is going on.
> The forests were initially configured to send push-notification messages
> to the primary -dev mailing lists of the appropriate Group(s). This
> seemed like a reasonable starting point, on the assumption that if a
> Group has Members who regularly push code into a JDK 7 forest then
> they'll want to (and arguably should) be aware of every push into that
> Some have expressed the concern, privately, that this results in people
> receiving too many messages in which they're not actually interested.
> There are (at least) a couple of ways to deal with this:
> - People can filter the incoming messages (look for the X-Hg-URL
> header, which points back to the repository for which the
> notification was generated); or
> - We could create an additional list for each forest and arrange to
> send Mercurial notifications to those lists only. People could
> then subscribe to those lists, or subscribe to the appropriate
> per-repository RSS feeds (broken at the moment, but to be fixed
> soon), or live in peaceful ignorance.
> So, what do people think? Should we create separate per-forest lists for
> Mercurial notifications, do nothing, or do something else?
I think it is important to be able to see every commit. I'm not sure if
the commit messages should go to the -dev mailinglists though. I for one
would subscribe to the RSS feeds published by the repositories, that is
perfect for me. I would rather not create more mailinglists, there are
already to many of them. I also don't care having the commit messages on
the -dev lists. They are easy enough to filter.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.openjdk.java.net/pipermail/discuss/attachments/20080314/614f502d/attachment.bin
More information about the discuss