[Doxygen-develop] Team with jenkins

[Peter M. <ped...@gm...>]

yo, hi ho..

its off to docs we go
with a bit and a bang with my shit code..

I understand where u come from ...

But I can help..

So first trick is to delegate jobs and build a trustes team..

Dont trust me btw.. trust one of your trusted already...

But delegate as fast as possible..

Get othere to do things for you nad forget the history.. please..

Just whack it into git and then we can all have fun and replace history
later..
Probably a GSOC code for doxygen musueum..


But what I do like is the idea of compiling docs online..
and for that we need a serveers and the latext code..

>>>>>>>>>>>>>>>> Future >>>>>>>
So we need to step up a bit
we already have a docs system for javascript (indeed ;-)
and we got go
and aarduino code
and web of things
<<<<<<<<<<<<<<<
And the only candidate who can make sense outta that..
Si the color designer and the coder..

So Plugins are in..
and imho we need desinger based plugins..

Then we are freeeeeeeeeeee...
we caan design all ou own aapis..
and publish then automaticaly with doxygen..

I no longer need to ponder and look at the code,

============================
Moved to Git
=============================
As soonas we move to git..
We can build automatically the builds for
windows, et all..
That is every commit to master..

This helps downsteam..
Compiling all the code on master is the "done deal" so we expect this to be
a regular monnthly things or not//

<<<<<<<<<<<<<<
Breaking downstream
<<<<<<<<<<<<<<<<<<<<
Instaling doxygen5
well with new parser, some things will break big time..
so we need a simple solution to this problem..

We need some guidanve to some "fix" but i dont think this is possible..
Need new design.. and a cmd line interface to do this..

>>>>>>>>>>>
releases
: We need some system to release software automatically every month or so..
aad push

<<<<
next
>>
Next is the branch of next stuff before it goes into master.......
This is what is expected to be out soon..

>>
to get into next, u need to be having it merged and working and a
branch/fork..


<<

This is the way that the general c++ and core code work..

HOWEVER..
I do not think that the fortran, c or parsers should exist in the core
code..

These need to be plugins and their own..

Style.......................#


How make that nice...