Re: No more dev change posts to wget-patches?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>> I would like for devs to be able to avoid the hassle of posting
>> non-trivial changes they make to the wget-patches list. To my mind,
>> there are two ways of accomplishing this:
>>
>> 1. Make wget-patches a list _only_ for submitting patches for
>> consideration by devs, no longer with the additional purpose of
>> communicating changes from the devs to the users.
>
> I don't think wget-patches was ever meant for communicating changes
> from the developers to the users. The main wget list was supposed to
> be used for that. As far as I'm aware, wget-patches was always a list
> meant for receiving patches (and possibly tracking them).
>
>> If using wget-patches to communicate changes that have been made is
>> in fact still a useful thing, then option #2 would be best. However,
>> it's not clear to me that a significant number of people are
>> actually reading wget-patches for this purpose, in which case any
>> that do want to know about such changes are probably better off
>> subscribing to wget-notify to see them, and I should employ option
>> #1.
>
> I think I agree with your reasoning.
Well, cool.
In that case, I think we will "exercise option #1" and discontinue the
practice of announcing changes (other than in the form of NEWS/Release
Notes at time of release) to the wget and/or wget-patches lists. As it
happens, there have already been several changes (such as the switch to
GPLv3) which have made it into the current trunk, but which have not had
associated announcements (I figured, if we decided such announcements
were still necessary, I could announce them retroactively! :) ).
There could still be some utility to having a trunk- and
release-branch-only commit notifications list, as I'm sure there are
people who may be interested in changes as they are happening, but not
in each piddling little code change as it's being written; but as far as
I'm concerned, it's easier just to let such people subscribe to
wget-notify and filter out the bug updates, and anything going to
/{tags,branches}/bugs/*.
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGnRKB7M8hyUobTrERCBvTAJ9RZmCmL0yZ5y+c7Wjs27PCBoNbiQCcCAK0
jxBOWNfepbR8ogm9zVdYclE=
=W8Lj
-END PGP SIGNATURE-
Re: No more dev change posts to wget-patches?
Micah Cowan <[EMAIL PROTECTED]> writes: > I would like for devs to be able to avoid the hassle of posting > non-trivial changes they make to the wget-patches list. To my mind, > there are two ways of accomplishing this: > > 1. Make wget-patches a list _only_ for submitting patches for > consideration by devs, no longer with the additional purpose of > communicating changes from the devs to the users. I don't think wget-patches was ever meant for communicating changes from the developers to the users. The main wget list was supposed to be used for that. As far as I'm aware, wget-patches was always a list meant for receiving patches (and possibly tracking them). > If using wget-patches to communicate changes that have been made is > in fact still a useful thing, then option #2 would be best. However, > it's not clear to me that a significant number of people are > actually reading wget-patches for this purpose, in which case any > that do want to know about such changes are probably better off > subscribing to wget-notify to see them, and I should employ option > #1. I think I agree with your reasoning.
No more dev change posts to wget-patches?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I would like for devs to be able to avoid the hassle of posting non-trivial changes they make to the wget-patches list. To my mind, there are two ways of accomplishing this: 1. Make wget-patches a list _only_ for submitting patches for consideration by devs, no longer with the additional purpose of communicating changes from the devs to the users. 2. Have svnmailer post any changes made to trunk or to release branches to wget-patches automatically. This means such announcements will no longer be limited to trivial changes. Note that I've asked dotsrc.org to implement the same non-subscriber authentication measures that are currently employed for the main wget list (as previously discussed), so hopefully the level of spam seen on wget-patches will be dramatically decreased. If using wget-patches to communicate changes that have been made is in fact still a useful thing, then option #2 would be best. However, it's not clear to me that a significant number of people are actually reading wget-patches for this purpose, in which case any that do want to know about such changes are probably better off subscribing to wget-notify to see them, and I should employ option #1. Input welcome. :) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGks7f7M8hyUobTrERCBgTAJ0VIi4Wd1Xq9DYQY95Hjoo1UXk5owCdECAX mdxQzH7DQD3pfYnM4YP8J8U= =gShz -END PGP SIGNATURE-
