[Mailman-Users] Availability of patches on Launchpad

[Richard Barrett]

On 7 Sep 2008, at 23:14, lists at viplist.us wrote:

> Not sure what patches your are seeing, but right now there are zero  
> patches
> on Launchpad and the are removed from Sourceforge.
>
> Having two different Mailman listings on Launchpad does not help,  
> either.
> Only one has the pogram - but neither have any patches.
>
> https://launchpad.net/mailman/+download
>
> has the standard Mailman program.
>
> ~mailman has nothing.
>
> Where are you seeing any patches at all?
>

I found links to those of my older patches (two of them) that were  
transferred from the sourceforge tracker linked under the right menu  
heading "Bug attachments" on the following pages:

     https://bugs.launchpad.net/mailman/+bug/266553 - was 444879 on  
sourceforge
     https://bugs.launchpad.net/mailman/+bug/266554 - was 444884 on  
sourceforge

In essence these entire tracker items, including attachments, appear  
to have been transferred from sourceforge to Launchpad.

The sourceforge tracker items for my other enhancements do not seem  
to have been transferred.

I guess it is not intended that the old approach with sourceforge of  
putting enhancements into the tracker with patch files attached,  
should be followed with Launchpad. I expect someone is going to tell  
me I should create my own branches of Mailman on Launchpad for each  
of my enhancement and publish what were patch file contents in that  
way. When I have time I may do that but in the meantime ...

>
>
> ----- Original Message -----
> From: Richard Barrett <r.barrett at openinfo.co.uk>
> To: mailman-users at python.org
> Date: Sun, 7 Sep 2008 19:17:10 +0100
> Subject: [Mailman-Users] Availability of patches on Launchpad
>
>> If you are a user of patches I have published for Mailman in the past
>> then read on. Otherwise, apologies for cluttering up your mailbox.
>>
>> In the recent switch from Sourceforge to Launchpad a number of the
>> current patches that I publish for Mailman do not appear to have made
>> the cut and are now unavailable from either Sourceforge or Launchpad.
>> As far as I am aware none of the patches that did not make it have
>> been incorporated into core Mailman but I am willing to be corrected
>> on this.
>>
>> Subject to the usual caveat that I will only maintain it while I use
>> it myself, I shall continue to publish my patches via:
>>
>> http://www.openinfo.co.uk/mm/index.html
>>
>> The tableau below summarise what I believe to be the case.
>>
>> Format of tableau is:
>>
>> SourceforgeNumber LaunchpadNumber Description
>>
>> - means unavailable on Launchpad
>>
>> made the cut
>>
>> 444879 266553 Archive indexer control to improve indexing.
>> 444884 266554 Integration of Mailman & htdig for archive searching.
>>
>> did not make the cut
>>
>> 644797 - Revised mailer exit status.
>> 760567 - Moderation request message content.
>> 820723 - Mailman/pipermail/MHonarc integration
>> 850805 - Aggressive anti email address harvesting measures
>> 1442025 - List Specialisation for Support Groups
>> 1483446 - Daily mbox files for list mbox archives
>>
>> --------------------------------------------------------------------- 
>> --
>> Richard Barrett                               http:// 
>> www.openinfo.co.uk
>>
>>
>>
>> ------------------------------------------------------
>> Mailman-Users mailing list
>> Mailman-Users at python.org
>> http://mail.python.org/mailman/listinfo/mailman-users
>> Mailman FAQ: http://wiki.list.org/x/AgA3
>> Searchable Archives: http://www.mail-archive.com/mailman-users% 
>> 40python.org/
>> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-users/lists% 
> 40viplist.us
>>
>> Security Policy: http://wiki.list.org/x/QIA9
>>