Developers of Sympa

[David Verdin <address@concealed>]

OK, merge just started. I'll keep you informed when I'm done resolving the conflicts.

David

Le 18/07/13 10:47, David Verdin a écrit :

address@concealed"> Hi,

I just ran somes tests: only 59 tree conflicts and 2 textual conflicts; This way better than I feared.
It may take less than a week to merge, finally. :)

Cheers,

David

Le 18/07/13 09:51, David Verdin a écrit :

address@concealed"> Hi guys,

Le 18/07/13 05:45, IKEDA Soji a écrit :

On Wed, 17 Jul 2013 18:08:13 +0200
David Verdin <address@concealed> wrote:

It's hot in France, too... ;)
Le 16/07/13 16:52, IKEDA Soji a écrit :

Sorry for delaying response.  In the last week it keeps 35°C at
Tokyo.  In short, Tokyo is hot.

Shortly, I agree to David's proposal.

Great!

On Fri, 12 Jul 2013 14:32:56 +0200
David Verdin <address@concealed> wrote:

Le 12/07/13 05:27, IKEDA Soji a écrit :

BTW: Rainy season, the season of hydrangea, has end in Tokyo.
Summer is come.  Would we be better to release Sympa 6.2 faster,
or be better to get well-factored codebase?  ...I cannot decide.

Well, here is a proposal I made to Marc and Guillaume when I met them a
few weeks ago. by looking at the history of discussion on this list, I
forgot to inform you of this discussion; For this, I apologize.

As we are far past the delay I had in mind for releasing the 6.2, I
propose that we don't release the 6.2.
instead, we will continue our refocatoring over the summer and relase a
7.0 with the new code base in September / October.

The advantage of this is that we won't have to support a code base that
we already now is doomed to disappear, letting us concentrate on code
improvments.
Also, once I'm done rolling back to filesystem spools, I'll merge the
current branches and put all that on git. That will be the basis for
development of the 7.0. In that context, not releasing the 6.2 will
prevent having to handle frequent merges between SVN and git.

So that's roughly the plan I had in mind.

Before merging, I want to be able to make all the spools work on the
filesystem. That way, I'll know if troubles come from the merges or from
the current code.

Do you agree with this plan of action?

A few comment/questions:

- My local work to refactor interaction between messages and
   spools will be finished in this month.  May I continue it?

See below.

- I wish, if possible, the codebase just before merging to Git
   would be released and announced broadly as "7.0a1" or so, to
   collect feedbacks from the user community.

Well we could certainly wait until Sympa 7.0 is in production before 
switching to git

- On git workplace, who would/should check, proof or approve pull
   requests sent by us (current developers) or others?

Étienne and I (as soon as we have figured out how it works).
I think that Sympa core developpers should not be moderated, whatever 
they do.

I see.

And by "core developpers", I mean all five of us.

a little word to finish: July is running. I wonder whether it would not 
be a good idea to merge with Guillaume's work right now.
I explain: it wil take time to finish the current refactoring and we 
wille certainly break things when we merge with sympa-cleanup branch.
so why not merge right now? That we'll be sure to have this merge 
available during the summer and we could start working together.

It's in sense.  By now I can hardly rewrite class names with
Guillaume's ones in my brain.

Yes, he's kind of contageous. I have the same problem. In addition, it will be easier to use a new development logical in the definitive code environment.

All I need is your word that you won"t commit anything when we have 
agreed to start merging.
I just merged Mark Overmeer's work to the 6. branch, so I'm ready to go 
as soon as you agree / disagree with my proposal.

Agreed?

I agreed.  I let go of the keyboard.  Go ahead!

Great!
I'll start som simulations and will go as soon as Guillaume has agreed for the merge.

Cheers,

David

Regards,

--- Soji

David

Regards,

David

Regards,

--- Soji


-- 
A bug in Sympa? Quick! To the bug tracker! 
<https://sourcesup.renater.fr/tracker/?group_id=23>
RENATER logo
*David Verdin*
Infrastructure pour les Services Informatiques

Tél : +33 2 23 23 69 71
Fax : +33 2 23 23 71 21

www.renater.fr <http;//www.renater.fr>
	RENATER
263 Avenue du Gal Leclerc
35042 Rennes Cedex

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

David Verdin Infrastructure pour les Services Informatiques
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

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

David Verdin Infrastructure pour les Services Informatiques
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

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

David Verdin Infrastructure pour les Services Informatiques
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: pngyqC6FaEnEU.png
Description: PNG image

Attachment: pngIBDbYV4f8d.png
Description: PNG image

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