New git workflow

[Davide Valsecchi]

Ehi guys,

The new workflow is clear? Do you have any question?

Please report any possible problem you see now because we are going to use
it.

Thanks!

Bye
Davide

2016-02-08 12:36 GMT+01:00 Davide Valsecchi <valsecchi.davide94 at gmail.com>:

> The idea is that the schedule will not include all open tasks ( as now) :
> every release page will include only features scheduled for that release.
> Doing so we can organize our work for two or more cycle. All the tasks not
> precisely scheduled could be inserted in a "open tasks" page, and included
> in the release as additional completed tasks.
>
> On every release page we have also to insert a section for "hotfixes" with
> tasks planned or completed for minor releases (useful to track status of
> bugfixes).
>
> The idea is that a new release is bounded to a few major changes or new
> features. All other little task could be inserted when they are ready.
>
> Did I explain this clearly?
>
> Davide
>
> 2016-02-08 12:27 GMT+01:00 Gianluca Rigoletti <
> gianluca.rigoletti at gmail.com>:
>
>> Good to hear this news!
>>
>> One question: how do we manage the release page on meta?
>> Now we have some version release page that contains all the tasks tracked
>> on phab.
>> Does it remain the same? We will still have a page with the tasks we are
>> going to work
>> and we are going to programmatically release, right?
>>
>> 2016-02-08 12:04 GMT+01:00 Davide Valsecchi <valsecchi.davide94 at gmail.com
>> >:
>>
>>>
>>>
>>> 2016-02-08 11:59 GMT+01:00 Cristian Baldi <bld.cris.96 at gmail.com>:
>>>
>>>>
>>>> Hey Davide,
>>>>
>>>> amazing job!
>>>>
>>>> I really like this feature-based workflow.
>>>>
>>>> Any idea about when we can start using this?
>>>>
>>>
>>> I think that we can immediately start using it. The W2L_0.6 is already
>>> there and all the development could continue from master, where develop was
>>> already merged.
>>>
>>>
>>>>
>>>> Does this workflow also apply to the related projects like the various
>>>> scripts we have or it is just for the Wiki part of WIkiToLearn?
>>>>
>>>
>>> I think that maintaining the same scheme in all projects would be a good
>>> idea. We should have master and release branches also in submodules and in
>>> all project, to be able of referring them easily.
>>>
>>> Bye
>>>
>>> Davide
>>>
>>>>
>>>> Good job again!
>>>>
>>>> Cristian
>>>>
>>>> 2016-02-07 21:19 GMT+01:00 Davide Valsecchi <
>>>> valsecchi.davide94 at gmail.com>:
>>>>
>>>>> Hi all,
>>>>>
>>>>> We have already spoken about the new git workflow on telegram channel.
>>>>> I've tried to summerize the proposals and I've written the new doc page
>>>>> with the new flow explained.
>>>>>
>>>>>
>>>>> http://meta.wikitolearn.org/Guide_for_the_development_of_WikiToLearn/Git_Workflow
>>>>> and
>>>>>
>>>>> http://meta.wikitolearn.org/Guide_for_the_development_of_WikiToLearn/Development_workflow
>>>>>
>>>>> Tell me if you like it or what we can do better
>>>>>
>>>>> Thank you!
>>>>>
>>>>> Davide
>>>>>
>>>>> _______________________________________________
>>>>> WikiToLearn-Tech mailing list
>>>>> WikiToLearn-Tech at kde.org
>>>>> https://mail.kde.org/mailman/listinfo/wikitolearn-tech
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> WikiToLearn-Tech mailing list
>>> WikiToLearn-Tech at kde.org
>>> https://mail.kde.org/mailman/listinfo/wikitolearn-tech
>>>
>>>
>>
>>
>> --
>> Gianluca
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/wikitolearn-tech/attachments/20160211/8c2bc244/attachment.html>