Hi all,

While what Stefaan says is of course true I would however like to add that there aactually are some additional advantages to having seperate repositories per package on Bitbucket:

   * configuration of commit rights per package
   * semi-automatic packaging for distribution
   * more selective retrieval of packages of interest to users / developers
   * independent evolution of packages in terms of tagging / versions
   * unlimited size and number of repositories
   * ...

All that being said, the seperation of dev and stable is only usefull if and when "simple" fixes are correctly propagated. It's a big change, but I'm sure in time we'll get used to it.

Best regards,
Hans

On 14/03/2011 15:47, Stefaan Vanbillemont wrote:
Hello all developers,

I'm busy testing some issues registered on our support website (bugs and new features). So I created two clones on my localhost:

- bitbucket_stable
- bitbucket_dev

Problem I'm encountering right now is that most of the fixes are comitted in the dev repos and not in the stable repos! This means that our entire switch to stable/dev repositories has no effect. So I kindly ask all developers to make sure they follow the workflow we agreed on:

*1. bugs (with NO database changes) are commited to the stable repos
2. bugs (with database changes) & new features are commited to the dev repos 3. before changing code in the dev repos please MERGE the dev code from the stable code so bugfixes are included in your new development!
*
If we keep working like we do now the entire setup with multiple stable/dev repos was a complete waste of time and we could have sticked to Google Code. In addition to that, when you update a support ticket to mark it as fixed make sure you include in what type of repo it was fixed/developed.

Kind Regards,

Stefaan Vanbillemont
Directie Onderwijs - Digitaal Leren
Hogeschool Gent


_______________________________________________
Dev mailing list
[email protected]
http://lists.chamilo.org/listinfo/dev

--

*Hans De Bisschop*
Hoofddeskundige ICTO | Lead Developer Chamilo 2.0
Software Coordinator Chamilo Association
Erasmushogeschool Brussel
Nijverheidskaai 170 | B-1070 Brussel
T 02 559 02 54 | i 254
[email protected] <mailto:[email protected]> | www.erasmushogeschool.be <http://www.erasmushogeschool.be/>

Kom eens langs: www.erasmushogeschool.be/infodagen <http://www.erasmushogeschool.be/infodagen> of lees onze elektronische nieuwsbrief: ehbrief.ehb.be <http://ehbrief.ehb.be/>
P Before printing, think about the environment

_______________________________________________
Dev mailing list
[email protected]
http://lists.chamilo.org/listinfo/dev

Reply via email to