[scribus-dev] GitHub Scribus Project is set up

[Pierrick Brunet]

Hi,

Usually (in most projects I saw), master is the current developpement 
version (last code reviewed and accepted by the core dev team) and tag 
are used for release.
Having a master for release may be a good idea if developpement version 
is not stable enough so that if user want to compile the default 
(master) scribus branch, he will default on a stable version.

I also wonder if workflow is impacted by this modification?

- Github have a bugtracker, can user use this one? Or Mantis is the default?
- Github have Pull Request workflow, contributors can use it? or they 
have to continue submitting patch on Mantis?

Chelen

On 28/07/2014 10:19, a.l.e wrote:
> hi
>
> i don't know, but i would expect the master to be the development 
> branch...
>
> ciao
> a.l.e
>
>> Yeah, I'm sure this will help !
>>
>> JLuc
>>
>>
>> Le 28/07/2014 07:48, Oleksandr Moskalenko a écrit :
>>> Hi,
>>>
>>> GitHub Scribus Community Project is now live. See 
>>> https://github.com/scribusproject for details and the README in the
>>> master branch.
>>>
>>>
>>>     Branches
>>>
>>>   * devel - main development branch
>>>   * master = release - release only branch. It will be empty until 
>>> 1.5.0 is tagged.
>>>   * svn - only used to synchronize the Git repository with the 
>>> Subversion repository. All others are short-lived feature
>>>     or hotfix branches according to the Git Flow model 
>>> http://nvie.com/posts/a-successful-git-branching-model/
>>>
>>>
>>> The only up-to-date branch from the scribus git server that was 
>>> copied over was ProPal. The other two feature branches
>>> would need to be brought up-to-date before moving if necessary.
>>>
>>> The svn branch should be automatically updated from Subversion 
>>> hourly. Please merge from it into the 'devel' branch as
>>> you work on the code.
>>>
>>> JLuc, Kunda, and ale have owner level access to the project.
>>>
>>> Regards,
>>>
>>> Alex
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> scribus-dev mailing list
>> scribus-dev at lists.scribus.net
>> http://lists.scribus.net/mailman/listinfo/scribus-dev
>
>
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev