[Bf-committers] Blender-Staging Repository

[Daniel Salazar - patazstudio.com]

Lord Loki! What a flashback :D abrazos
Daniel Salazar
patazstudio.com


On Wed, Nov 19, 2014 at 4:11 AM, Campbell Barton <ideasman42 at gmail.com> wrote:
> Hi Jorge, added you to the bf-blender-staging project.
>
> Added some guidelines to the project page.
> https://developer.blender.org/project/view/56/
>
>
> Also added instructions for using the staging repository along-side an
> existing git checkout,
> so you can quickly move between staging and stable Blender master
> without having multiple checkouts (and build dirs).
> https://developer.blender.org/diffusion/BS/
>
> On Wed, Nov 19, 2014 at 9:32 AM, Jorge Bernal <jbernalmartinez at gmail.com> wrote:
>> Hi Campbell,
>> I would like to gain access to the new tuhopuu repo.
>> I have got several patches committed in blender and now i'm working in a
>> big patch (BGE logic bricks clean up).
>> My work:
>> http://wiki.blender.org/index.php/User:Lordloki/Blender_activity_record_book
>>
>> As curiosity, I had commit access to the former tuhopuu branch :-)
>>
>> Regards,
>> lordloki
>> El 18/11/2014 21:01, "Campbell Barton" <ideasman42 at gmail.com> escribió:
>>
>>> Patch review continues to be a bottleneck, but we'd like to help get
>>> patch authors get involved even if we don't have to review patches for
>>> inclusion in master.
>>>
>>> The possibility of having a new "tuhopuu" repo came up (from CVS days
>>> where devs could gain access easily and commit what they liked to work
>>> on...), this sound like it could be fun...
>>> but someone still has to sync this with master & resolve conflicts, if
>>> we don't ever expect the changes to go into official releases... its
>>> not the best use of our time.
>>> Especially when there are enough free 3rd-party git-hosting providers
>>> around.
>>>
>>>
>>> Here's the plan:
>>> We've setup a new git repository, matching git.blender.org:blender.git,
>>>
>>> * Patch authors are given access to this git repository (low barrier of
>>> entry).
>>> * Patches can be committed to blender-staging (no lengthy review, just
>>> check functionality is OK for releases).
>>> * Buildbot can be made to build this repo too. (for user testing).
>>> * Each release we re-mirror from master, (any longer term development
>>> can happen in a branch of blender-staging if really needed).
>>>
>>> This helps newer developers become fa miler with development tools &
>>> process, so it goes smoother when they get access to the official
>>> repository.
>>> Ideally, it means patches end up being tested more thoroughly too.
>>>
>>> Anyone who doesn't have commit access & would like, feel free to ask
>>> on this mailing-list (with a link to your work).
>>> We'll go over the patch tracker and suggest patches to be committed &
>>> granting devs access to the repository in the next week or so.
>>>
>>> https://developer.blender.org/diffusion/BS/
>>>
>>> --
>>> - Campbell
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>
>
>
> --
> - Campbell
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers