Developers of Sympa

[David Verdin <address@concealed>]

Dear all,

Le 22/10/13 10:07, Guillaume Rousse a écrit :

address@concealed">Le 22/10/2013 09:51, David Verdin a écrit :

Dear Soji,

I agree with you: We need to keep proper legal information and we'll
take your template. Thsi template works, is a good short term solution
and we'll keep further discussion about licence and discmlaimers for
when we are not more than one year late to issue a new Sympa version.

As I'm talking about it: we need to issue a Sympa version soon. our
community will start to wonder why no Sympa version is issued. They can
start to think that the project is dead, as nothing new was issued since
more than one year.

What we want here:

  * Have an alpha in production in november
  * Issue a beta in december.
  * Have a stable version in the beginning of 2014 (probably February).

I'll take the latest discussions in the developpepers mailing list,
propose a decision, and we'll stick with it for the 7.0.

We need to issue a Sympa version, or the project will be in a very bad
shape.

That seems indeed a good idea, but I think it's suicidal to consider the current content of sympa-cleanup branch as a viable solution to produce even an alpha release: the code doesn't even compile, and is a ugly mix between one year of parallel development.

Of course !
I need to work hard on this to fix all the ugliness the merge produced.

address@concealed">
For me, the viable solution would be to use as base either:
a) sympa-6.2 branch, for new features

There was a version prior to the merge that is running smoothly on our own server since one year.
6.2a.32 if I remember correctly.

address@concealed">b) sympa-cleanup before the merge, for code readability

Code readability is good, but I think we will have more adhesion to a new version for features; that's what people want, and that's what proves the project is alive.

address@concealed">
And once one branch chosen as base, eventually replay some of the changes introduced in the other progressively, using the minimal test suite to catch regression after each commit.

Do you think this is a lot of work?

address@concealed">
Given most of my initial changes were purely syntactic ones, easy to replay mechanically, and than I never even attempted to actually run my code outside of unit tests, I really think we should use sympa-6.2 as base.

Your proposal looks good, but I want Soji's approval on this.
For a start, I don't hink all soji's evolution regarding configuration caching are present on the version we're running.

Soji, as you invested a lot of time and energy in Sympa, you earned the right to have demands on what will be or not in the next Sympa version. If we issue the current 6.2 in production on https://groupes.renater.fr/sympa, woud it be good enough for you?

Best regards,

David

--
A bug in Sympa? Quick! To the bug tracker!

David Verdin Études et projets applicatifs
Tél : +33 2 23 23 69 71 Fax : +33 2 23 23 71 21   www.renater.fr	RENATER 263 Avenue du Gal Leclerc 35042 Rennes Cedex

Attachment: smime.p7s
Description: Signature cryptographique S/MIME