AW: [Mapbender_dev] Mapbender Commit Policy

[Manns, Marc]

Hi Karim,

this is Ok for me,
so how do we do this?

* Every developer create an seperate branch
* We commit into a (trunk_dev).

If we all create our own branch'es i need a little "how to" 
because i've never done this before.

regards Marc 


-----Ursprüngliche Nachricht-----
Von: mapbender_dev-bounces at lists.osgeo.org [mailto:mapbender_dev-bounces at lists.osgeo.org] Im Auftrag von Karim Malhas
Gesendet: Montag, 28. Februar 2011 18:33
An: mapbender_dev at lists.osgeo.org
Betreff: [Mapbender_dev] Mapbender Commit Policy


As discussed on todays IRC meeting, we would ask all developers to stop commiting into trunk directly. Instead I ask you to create a branch, and when your feature or bugfix is done, find someone on IRC to review it and merge it to trunk.

This keeps the trunk clean of half finished features and it gives you someone else to look over your code to find errors.

At this time this policy is not enforced, merely suggestd behaviour.

Kind Regards,
Karim Malhas
_______________________________________________
Mapbender_dev mailing list
Mapbender_dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapbender_dev