Hi all,
after the release, we now have a 3.0.x branch (version number 3.0.1-SNAPSHOT) and develop (version number 3.1.0-SNAPSHOT).
As discussed last year in Bolsena, I think the idea is now:
- to commit fixes and minor features in 3.0.x branch which will then be merged in develop
- major features to develop.
Same for PR, which should go to 3.0.x branch first and then to develop by merge (to avoid cherry picking too much).
Is this fine for everyone ?
Another question is how to deal with that in transifex (which is currently getting files from develop). Any ideas ?
Cheers.
Francois
El 29/4/2015 16:52, “Francois Prunayre” <fx.prunayre@anonymised.com> escribió:
Hi all,
after the release, we now have a 3.0.x branch (version number 3.0.1-SNAPSHOT) and develop (version number 3.1.0-SNAPSHOT).
As discussed last year in Bolsena, I think the idea is now:
- to commit fixes and minor features in 3.0.x branch which will then be merged in develop
- major features to develop.
Same for PR, which should go to 3.0.x branch first and then to develop by merge (to avoid cherry picking too much).
Is this fine for everyone ?
+1!!
Another question is how to deal with that in transifex (which is currently getting files from develop). Any ideas ?
transifex does not take changes from repository, right?
Cheers.
Francois
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork