possible workflow for small changes

[Gary Ferland]

Almost daily I come across small changes that should be made to the documentation or code.  I support the  notion of not working directly on master.  Then, where should small changes be made and later reviewed?  

I will try out something simple - I just created a branch with Sunday's date as the name, 21sep19, and will post small things to it.  The main development will continue to be on the correct branch.  Small changes can be tossed in there and at the end of the week, reintegration proposed.  

Let's see if that helps the workflow.  It could be useful, or a needless complication.

thanks,

Gary

[Marios Chatzikos]

I'm OK with posting small changes directly to master, including updates to test suite monitors and documentation.  The former are much easier to do on master, because otherwise they can make reintegration painful.  The latter are rather innocuous -- but with the understanding that these are small fixes, not functionality that should be documented on a relevant development branch.

The sanctity of master should aid toward more robust development, not be an obstacle to that end.

On a related matter, I suggest adopting the following workflow: reintegrate branches to master locally, test in default mode, and with -DFLT_IS_DBL, and after all necessary updates to the test suite, push the local master to nublado.  Runs with other compilers are essential double checks that the main development and testing are solid.

Again, this respects the sanctity of master on nublado, but uses the other compiler runs to guarantee that.

The alternative of running with various compilers ahead of time to make sure that the test suite won't botch is limited by the fact that some compiler configurations are unique to the testing servers.

I hope this makes sense,

Marios

--
--
http://groups.google.com/group/cloudy-dev
---
You received this message because you are subscribed to the Google Groups "cloudy-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloudy-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cloudy-dev/b4b92684-52ac-4b85-be01-a53b1f1bb716n%40googlegroups.com.