[Mailman-Developers] Re: conversation about 2->3 upgrade path

2020-05-24 Thread Abhilash Raj


On Tue, May 19, 2020, at 6:18 PM, Sumana Harihareswara wrote:
> On 5/19/20 6:16 PM, Sumana Harihareswara wrote:
> > On 5/17/20 10:05 PM, Abhilash Raj wrote:
> >> On Sat, May 16, 2020, at 2:04 PM, Sumana Harihareswara wrote:
> >>> https://mastodon.technology/@brion/104152363969142016
> >>>
> >>> Hi folks - I figured you might want to know about this small Mastodon
> >>> conversation.
> >>
> >> Thanks for letting us know, Sumana! I am not on Mastodon, so probably 
> >> won't be able to reply there.
> >>> Seems like the world of folks who are currently using Mailman 2 lists
> >>> includes people who need:
> >>> * materials to help their sysadmins understand how and why to upgrade 
> >>> to 3
> >>
> >> We do have migration docs for system admins:
> >>     https://docs.mailman3.org/en/latest/migration.html
> >>
> >> Although, the current migration involves running a command for all the 
> >> lists one-by-one and then import the Archives separately. The process 
> >> could be made a bit better IMO, but I haven't had time to prioritize 
> >> the effort recently. Maybe I should pick up my WIP MR again[1].
> >>
> >> [1]: https://docs.mailman3.org/en/latest/migration.html
> >>
> >>> * major hosting companies like Dreamhost to start offering Mailman 3,
> >>> and an easy upgrade path
> >>
> >> I am happy to help any hosting companies to migrate their Mailman 2 
> >> users off to Mailman 3. I haven't had any previous conversations, but 
> >> was wondering if there are any representatives on this list to start 
> >> off a conversation perhaps?
> >>
> >> The process can be fairly easily automated I think.
> >>
> > 
> > 
> > Thanks! I replied to the thread and some conversation is continuing there.
> > -Sumana
> 
> One response in that thread:
> 
>  > to close the loop on the dreamhost bit, i got a response to the 
> effect that postorious doesn't expose enough settings via web UI, so 
> until the web configuration experience is workable for them dreamhost 
> won't be planning a migration.

All the useful ones are now exposed, pending one (emergency flag for 
MailingLists), which is also exposed in master branch but not released yet.

Unless they mean other "settings" of some sort, then they'd need to be a bit 
more specific since everything is a setting ;-).


> 
> -Sumana
>

-- 
thanks,
Abhilash Raj (maxking)
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9


[Mailman-Developers] Re: Postorius, Hyperkitty new release candidates

2020-05-24 Thread Abhilash Raj
Hey Everyone,

It turned out that we added a lot of bugfixes soon after the rc1 and so I am 
going to do another rc before the stable release.

 - Postorius: 1.3.3rc2
   Changelog: 
https://docs.mailman3.org/projects/postorius/en/latest/news.html#rc2
   Download: https://pypi.org/project/postorius/1.3.3rc2/
 - Hyperkitty: 1.3.3rc2
   Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#rc2
   Download: https://pypi.org/project/HyperKitty/1.3.3rc2/
 - Django-mailman3: 1.3.3rc2
   Changelog: 
https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst
   Download: https://pypi.org/project/django-mailman3/1.3.3rc2/
 
The major changes between rc1 and rc2 are are mostly bugfixes.

One big cosmetic change is Settings page for List owners, which now has a 
vertical menu on the left instead of horizontal tabs. 

The major problem with horizontal tabs for settings was that we were running 
out of horizontal space in our page width, because of which we weren't able to 
separate out settings in as-many sections as wanted to. Bounce processing for 
example was a part of the "Member Policy" tab which included 
subscription/un-subscription policies. Now, we have a new section for "bounce 
processing" and flexibility to group other settings into a new section for 
better discovery of so many list settings.

Hopefully, this will be the last rc and I'll do a stable release next weekend!

Abhilash

On Sat, May 9, 2020, at 6:46 PM, Abhilash Raj wrote:
> Hi Everyone,
> 
> I am pleased to announce a couple of more releases:
> 
> - Postorius: 1.3.3rc1
>   Changelog: 
> https://docs.mailman3.org/projects/postorius/en/latest/news.html#rc1
>   Download: https://pypi.org/project/postorius/1.3.3rc1/
> - Hyperkitty: 1.3.3rc1
>   Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#rc1
>   Download: https://pypi.org/project/HyperKitty/1.3.3rc1/
> - Mailmanclient: 3.3.1rc1
>   Changelog: 
> https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclient/docs/NEWS.html#rc1-2020-05-09
>   Download: https://pypi.org/project/mailmanclient/3.3.1rc1/
> - Django-mailman3: 1.3.3rc1
>   Changelog: 
> https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst
>   Download: https://pypi.org/project/django-mailman3/1.3.3rc1/
> 
> Python 3.6+ and Django 2.0+ is supported for all of them. Django 3.0 
> support for Hyperkitty requires manually upgrading a dependency 
> (django-haystack>=3.0b2, once a stable version of this has been 
> released, it shouldn't require manually upgrading).
> 
> There are tons of bug-fixes across the board and some new features. 
> 
> Biggest visible change is switch to Bootstrap 4, which has been long 
> pending for us. Bootstrap 4 completely changes the CSS grid model using 
> the new Flexbox. There might be some small changes or breakages when 
> using on mobile. Please report such issues to us via Gitlab!
> 
> Some other notable changes are in Postorius, which includes many more 
> list settings exposed include content filtering settings, bounce 
> processing (which was added in the previous release of Mailman Core) 
> settings and some other ones. You can now also specify a reason when 
> rejecting held messages.
> 
> There was also a gnarly bug, which caused the name of some members to 
> be the string "None". For the longest time, I couldn't figure out the 
> reason for it, but it ended up being a simple fix in mailmanclient's 
> json serialization of display_name, which would result in Python's None 
> value being passed as string "None" to Mailman's API for subscription.
> 
> There is also better support for filtering visible lists based on the 
> current vhost, which I see a few people are already waiting for from 
> mailman-users list.
> 
> A full changelog has been added to each project in the top. These are 
> still pre-releases and if you are installing via pip, you would need 
> the `--pre` flag, for e.g.
> 
> $ pip install --pre --upgrade postorius hyperkitty
> 
> As with all other releases, these have also been running on 
> mail.python.org and lists.mailman3.org for some time now, so it should 
> be relatively safe to upgrade to. Stable releases for this is now 
> scheduled in 1 week, hopefully, next weekend.
> 
> -- 
>   thanks,
>   Abhilash Raj (maxking)

-- 
  thanks,
  Abhilash Raj (maxking)
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3

Security Policy: https://wiki.list.org/x/QIA9