Hi Matthew,
> The other side of this is not having lots of builds close together improves
> stability and therefore performance.
The only thing causing disruptions are changes in routing and inter-node
communication but those builds will generally not talk to older nodes anyway,
right?
Your expertise in maintaining the very core of Freenet is invaluable. On short
notice nobody can take over your job so the decision about routing-relevant
merges, i.e. anything that touches old/new last good build, would still reside
in your hands; maybe in a separate branch that you merge into the main
development branch every now and then after you?ve reviewed other people?s
commits or wrote some yourself. The main development branch could hold the
more cosmetic stuff or changes that will not affect the network as a whole;
those changes can be reviewed by somebody with less knowledge about Freenet?s
intestines. Also, new builds containing only those changes could be released
with little chance of disrupting the network. This does, however, require that
we keep the source code maintained in the repository a little bit tighter than
we currently do. :)
Greetings,
David
--
David ?Bombe? Roden <bombe at pterodactylus.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20111104/49790081/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20111104/49790081/attachment.pgp>
