[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Missing ASF-wide announcement for 1.7.9, 1.6.21

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Mon, 8 Apr 2013 21:26:46 +0400

2013/4/5 Ben Reser <ben_at_reser.org>:
> On Fri, Apr 5, 2013 at 8:05 AM, Konstantin Kolinko
> <knst.kolinko_at_gmail.com> wrote:
>> Hi!
>>
>> 1. The announcements for recently released Subversion 1.7.9 and 1.6.21
>> apparently has not been sent to ASF announcements list,
>> "announce at apache.org".
>>
>> Its archives are here:
>> http://mail-archives.apache.org/mod_mbox/www-announce/201304.mbox/browser
>>
>> Looking into those archives, I do not see announcements for 1.6.20 and
>> 1.7.8 either,
>> so this omission is not new.
>
> My fault, I didn't know we were doing this. However I don't think
> 1.6.x releases should go to that list since technically they aren't
> Apache releases. I've sent the 1.7.9 release announcement to this
> list.
>

Thank you! I saw your announcement.

Regarding 1.6.x, all versions (except a few 1.7 betas) between April
2010 and February 2012 were announced on that list. This includes
1.6.11 .. 1.6.17 and 1.5.9. Announcements ceased since March 2012 for
either 1.7.x or 1.6.x.

Personally, I do not care about 1.6.x.
I hope that there will be a 1.8.x release sometime this year, and so
this topic about 1.6.x will become obsolete.

>> 2. A good practice is to begin the subject line of such messages with
>> "[ANN]" or "[ANNOUNCE]".
>
> That makes sense if we're sure all the lists we're sending it to don't
> add any sort of prefixes on their own.
>

A mailing list prefix does not matter much. What matters is whether
you want to distinguish this message from others on that mailing list.
So it is OK to have two prefixes.

I agree that it does not matter for the announcements list as there
are no non-announcement messages in it. So, OK. I just noted that you
looked out of line here.

>> It might be a good idea to update the community guide accordingly,
>> to explicitly mention the announce_at_a.o mailing list in addition to the
>> three subversion.a.o ones.
>> http://subversion.apache.org/docs/community-guide/releasing.html#releasing-release
>
> Hmm the docs actually say "The mail to announce_at_subversion.apache.org
> will also be forwarded to
> announce_at_apache.org." I take that to mean it should happening
> automatically, if this was the intention should we fix this breakage
> or should we just change the docs. If it's reasonable to make it
> automatic I'd prefer that even if we end up with some 1.6.x releases
> on the other list.

I did not note that sentence. ;)

Looking at the file history, that phrase was added in r1140689 (June 2011).

I have not heard about such automated forwards elsewhere. It might be
that it was some typo. It does not say "automatically". So maybe it
meant that release manager forwards the message.

Actually,
- Such forwarding does not happen.
- All announcements that were sent by Hyrum Wright explicitly include
"announce at apache org" in the list of addresses

E.g. looking at announcement for 1.7.3, there is "View raw message"
link at the bottom of the page, where you can see the addressees list.

http://mail-archives.apache.org/mod_mbox/www-announce/201202.mbox/%3CCAFwo6TZonyaVvhFiHQ0__J=XsT_JdiE0QLF7=08PA3Zv4E7JxQ@mail.gmail.com%3E

BTW,
a minor thing that is also missing in a release is update to this DOAP file:
http://svn.apache.org/viewvc/subversion/site/publish/doap.rdf?view=markup

I mean, it still says "1.6.15".

The DOAP file is used to publish project info here:
http://projects.apache.org/projects/subversion.html

Description:
http://projects.apache.org/doap.html

Best regards,
Konstantin Kolinko
Received on 2013-04-08 19:27:19 CEST

This is an archived mail posted to the Subversion Dev mailing list.