The next ...

[ikedas]

Branch for Release 6.2.70 #1384 was created.

If anyone wants to release the next version anytime, please feel free to do it.

[racke]

What about beta releases? Or we just go with the bug fixes?

[ikedas]

Beta releases are desirable, if they are meaningful.

Needless to say, all changes described in the release notes should be tested well. --- If they had been, we would not have had to completely revert the feature added in the two previous release.

Anyway, I have stepped down as release manager (That's why I haven't set up milestone tag 6.2.70 or alike). So @racke, please feel free to make suggestions for future releases.

[racke]

I guess it is up to me to pick up the baton as release manager. My idea is that we shouldn't wait too long for the 6.2.70 in order to fix the bugs introduced with 6.2.68 which bypassed our Potemkin beta tester team.

@ikedas Please send me instructions about how to release Sympa betas / new versions.

[ikedas]

Hi @racke,

Potemkin? ...Ah well, well, I'm convinced they will rise up in the end, but now seems not the time yet (however you probably are not talking about the battleship:smile:).

---

The instruction is here in "How to prepare a new source tarball". Some additional information:

• To commit changes, Sympa authors <sympa-developpers@listes.renater.fr> (p is duplicated) is used as the author at all.
• Item 3 (Retrieve latest translations and update translation) may not be necessary this time.
• Item 10 (Add tag to remote repository) will be automatically done by publishing a new release page. Conversely, all changes must have been pushed to the remote repository at the time the release page will be published.
• Afterward, you should post release announcements to sympa-announce@listes.renater.fr and lets@translate.sympa.org (both of them are moderated).
• After the all steps above, there is the task of pushing the release page to the website, which I will do, as it has not yet been automated.

Please let me know if I've left anything out.

[racke]

@ikedas reference was to Potemkin's villages where all houses are just the front without any living quarters to show up to visitors 😬

[ikedas]

I just learned it from Wikipedia yesterday. Well, person in power is often ignorant of the truth. 🙃

[ikedas]

I'd like to solve at least these two before the next release (we already know how to fix both of them).

• File names in incoming spool can be truncated #1410
• Incorrect character encoding when set custom attribute with special characters using the SOAP API #1407

---

These may be suspended to the next-next release.

• Deprecate scripts under bin/ #1386 (PRs have been submitted)
• Alternative PR for List admin update through the command line #903

I hope to resolve these asap but have not started yet.

• Exim: Failed to get envelope sender in "Return-path:" field #1354 (I've not yet found the solution)
• WWSympa crashes by topics.conf with inappropriate format #1242 (we have to find the way to handle errorneous topics.conf)
• mailto: link cannot be detected by some MUAs #1124 (mailto link should be replaced with link to web GUI if possible)

[racke]

I created milestones for 6.2.70 and 6.2.72 and assigned them to these issues.

[ikedas]

Thanks @racke !

But the last three in above may not be solved soon, so I moved them to 6.2.72....
And I added issues already closed to 6.2.70 for memory.

[racke]

So my tentative plan would be for the release:

• Test run / Automate release process
• Write email to list about change of release management, pending release and available beta testers
• Set release date base on feedback from the list
• Coordinate release with package builds

[ikedas]

Nice plan!

Test run / Automate release process

Currently test cases run by each push with a workflow of GitHub Actions (lacks many cases, though:unamused:).
I don't think we necessarily have to use GitHub Actions, but actions required to publish release seem already available.

[ikedas]

@everyone (particularly @racke ),

I personally think that none of the issues currently open need to be resolved before the next stable release.

• Should we declare a code freeze?
  I was pretty vague on this procedure, but it should have been done if possible.
• Will the next release be a beta or a directly stable release?

I will post about automating the release process in another thread.

[racke]

Code freeze would mean to me that we don't update sympa-6.2 with the exception of critical problems and translations.

As we did mostly bug fixes, I would prefer to make a stable release without beta.

[ikedas]

@racke (perhaps you author the release announcement),

I wrote a notice about the transition of web site and the lists. Please include this text in the next release announcement.

I am not a proper English writer, so please fix anything odd.

---

The community will have a new domain

The web site for the community of Sympa, which has been operating under the sympa.org domain, will now move to the new domain sympa.community.

After [date] in [month], the official website URL will be:

https://www.sympa.community

(Note: sympa-community.github.io, previously used URL, will be automatically redirected to the new site.)

In addition, the mailing lists for the community, which have been hosted by RENATER on their servers, will be migrated to the new domain. We will announce again when the transition is ready.

We would like to thank RENATER for hosting the website and mailing lists for two decades.

• Contact

  For inquiries regarding transition of web and lists, please contact devel@sympa.community.

The Sympa Community

---

[ikedas]

Hi @racke,
Will the fix to #1454 be ready for 6.2.70? I think we can merge it in the next few days, so please add it if possible.

[racke]

Using "make tidyall" in my environment creates a huge commit: https://github.com/sympa-community/sympa/compare/sympa-6.2...racke:tidy/6.2.70?expand=1

@ikedas Can you elaborate on your Tidy setup?

[ikedas]

Perhaps the versions of Test::PerlTidy and/or Perl::Tidy don’t match (see cpanfile),
Anuways this time , I think, skipping tidyall does not so matter.

[racke]

The versions are quite old:

 requires 'Test::PerlTidy', '== 20130104';
 requires 'Perl::Tidy', '== 20180220';

Skipping tidyall for this release.

[ikedas]

btw I was working on the release with a recent version of Perl compiled by myself instead of the one bundled to the OS; I added the --with-perl option to configure so that my own Perl would be used.

[ikedas]

I'll be away most of 17th to 19th. If you will be working for release in this weekend, please feel free to do it without asking me.

---

BTW for now following issues/prs are ready for merging. If no objection, It should be labelled 6.2.72 (not 6.2.70).

• Logs reflect Failure when include from SQL is carried out during nosync_time_ranges #1429 (confusing err log in inclusion)

• include_sql_query broken for CSV database driver #1434 (loading CSV driver crashes)

• Easy way to get permalinks for messages in web archives #1441 (add permalink on messages in web archive)

• Excess header fields are shown in the web archives #1447 (reduce header fields shown on archives)

• A group of PRs enhancing ARC feature:

  • Following typo fix in Mail::DKIM::ARC::Signer #1449
  • Should addition of ARC seal depend on DKIM signing? #1450
  • ARC: Add Authentication-Results: field (AR), if useful one is not found #1453
  • Forwarded messages should also be ARC sealed if possible #1457

• Import SOAP encoding schema in WSDL #1456 (fix broken SOAP schema)

• WWSympa: Page size cannot be changed on review and reviewbouncing #1466 (bug in web UI)

• Update SMTP status codes #1467 (update SMTP status codes used in bouncers page)

• Let some obsoleted parameters be retired and add convenient spam_status scenarios #1470 (spam_status feature: clarify parameters and add scenarios)

• Remove OChangeLog #1471 (remove unuseful OChangeLog file)

• Template error parsing not detected #1474 (temlate error in creation of automatic list not detected)

• Options for welcome_return_path & remind_return_path do not describe their function #1475 (clarify (welcome|remind)_return_path parameters)

[racke]

@ikedas Sorry, I don't understand your comment "It should be labelled 6.2.72 (not 6.2.70)." Can you elaborate please?

[ikedas]

I think these fixes/improvbements should be included in milestone 6.2.72, but not in 6.2.70, the next release.
So if no objection, I'd like to label these as 6.2.72.

[ikedas]

Since there are no objection, I did.
The reason is simple: if we don't label them, we'll miss them.

[racke]

Fine for me 👍

[ikedas]

@racke, when would the new release be possible? If you don't have the time to do it, shall I switch work?

It has been 9 months since the last release.

[ikedas]

Can I prepare draft of the release note?

[ikedas]

@racke, when would the new release be possible? If you don't have the time to do it, shall I switch work?

[racke]

Will do the release next Sunday. On 2 October 2022 12:47:34 EEST, IKEDA Soji ***@***.***> wrote: ***@***.***, when would the new release be possible? If you don't have the time to do it, shall I switch work?

-- Reply to this email directly or view it on GitHub: https://github.com/orgs/sympa-community/teams/everyone/discussions/30/comments/39 You are receiving this because you were mentioned. Message ID: ***@***.***>

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[ikedas]

Now all issues tagged 6.2.72 have had [on going] lael, i.e. have PR to solve their problems.

OTOH these are submitted and have [on going] label but have not had 6.2.72 tag:

• include_sql_query requests unuseful parameters for CSV database driver #1437 Correct parameters for CSV driver
• Update default of anonymous_header_fields parameter #1502 Update default of anonymous_header_fields parameter
• dmarc_protection.phrase "From" format INCORRECT #1498 dmarc_protection.phrase "From" format INCORRECT
• WWSympa: Authentication mechanism that does not require login if the authentication module allows it #1497 WWSympa: Authentication mechanism that does not require login if the authentication module allows it
• accessing db_additional_subscriber_fields fields in footer vs. tt2 templates #1494 accessing db_additional_subscriber_fields fields in footer vs. tt2 templates
• Deprecate conf_2_db feature #1424 Deprecate conf_2_db feature
• [WWSympa] Cannot allow owners to manage editors of a distribution list #1488 [WWSympa] Cannot allow owners to manage editors of a distribution list
• Deprecate "dkim" authentication method for scenarios #1483 Deprecate "dkim" authentication method for scenarios
• Template error parsing not detected #1474 Template error parsing not detected

@racke, if you like, could you please tag these?

[racke]

Done!