Hello Saros-devs,
In my master thesis I'm working (as some already know) on the feature to
display action awareness information, for example if the dialog was opened,
which view was activated, what was refactort etc. The first attempts of
this are already in change in 1515 [1] .
Currently, this feature is configurable, it can be managed in the
"saros.properties" file, since it is still under development. Now I want to
extend this implementation through usability-tests, thus work in the user's
feedback or adapting already existing code. This would mean that already
existing changes in Gerrit, which are/were being reviewed (or merged), must
permanently be adapted/extended.
In [2], it says that (as expected) the master-branch ist for
feature-development, and no matter how often I adapt my feature to user
feedback, it is still a feature development. But in [3], it is explained
that for "larger development efforts (e.g. a new feature, large-scale
re-engineering)" a new branch can be created.
My question is, if it would make sense to create a new branch in my case.
What is the convention in this group with features that can be adapted
again and again? Does creating a new branch makes more sense in my case?
Kindly Regards,
Damla Durmaz
[1] http://saros-build.imp.fu-berlin.de/gerrit/#/c/1515/
[2] http://www.saros-project.org/ReleaseProcess/#How_to_merge
[3] http://www.saros-project.org/contribution#developing-in-a-branch
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
