[Vtigercrm-developers] Community Help: Set roadmap for 7.5.0

[nilay khatri]

Prasad, it is more cleaner. You can still release a hotfix for 7.4.0 as you
would be able to merge code for that into master because 7.5.0 active
development is in a separate branch.

Also all those reverts, fixed small issues, typo mistakes and all those
clutter will not create mess in the master if we follow a separate branch
approach.


On Tue, Aug 10, 2021 at 5:08 PM Prasad <prasad at vtiger.com> wrote:

> Nilay,
>
> Master represents the next release - don't see a need for a special branch
> to maintain.
> Unless I'm missing something specific.
>
> Regards,
> Prasad
>
> On Tue, Aug 10, 2021 at 5:02 PM nilay khatri <nilay.spartan at gmail.com>
> wrote:
>
>> Prasad, instead of project, better we create a branch (I guess you will
>> have to do it on code.vtiger.com), call it 7.5.0.
>>
>> All the MRs will be sent to 7.5.0 branch. After the final build it can be
>> then merged with Master, marking it as a new release.
>>
>> On Tue, Aug 10, 2021 at 4:52 PM Prasad <prasad at vtiger.com> wrote:
>>
>>> You can create a project at code.vtiger.com (GIT) and push MR to master
>>> <https://code.vtiger.com/vtiger/vtigercrm>.
>>>
>>> On Tue, Aug 10, 2021 at 4:45 PM S T Prasad <stprasad at stprasad.com>
>>> wrote:
>>>
>>>> Hello Nilay,
>>>>
>>>> The discussion on the thread, which prompted you to provide this fresh
>>>> start so to speak on community participation is very welcome.
>>>>
>>>> I propose that the community have its own repository , where the
>>>> community perspective will be better laid out.
>>>>
>>>> If there is agreement, then we can start a public repo on Github right
>>>> away.
>>>>
>>>>
>>>> With best regards,
>>>>
>>>> S.T.Prasad (Skype: stprasad at stprasad.com)
>>>> Founder and Chief Shikari
>>>> http://www.vtigress.com
>>>> The Purr-fect mate for vTiger
>>>>
>>>>
>>>> On Tue, Aug 10, 2021 at 4:12 PM nilay khatri <nilay.spartan at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Hope every one is keeping safe and well.
>>>>>
>>>>> So as mentioned by Prasad from Vtiger's team, the extencations for
>>>>> next version 7.5.0 are to fix bugs and it other contributions from the
>>>>> community.
>>>>>
>>>>> So as a community it would be great to set a roadmap ourselves, take
>>>>> responsibilities for tasks/issues that interest you and take the product
>>>>> ahead.
>>>>>
>>>>> The next version release is targeted for Jan 2022, giving us 4 months
>>>>> of time.
>>>>>
>>>>> My suggestion would be to split this into 3 + 1, keeping 3 months for
>>>>> development contributions and last 1 month towards bug fixes and testing.
>>>>>
>>>>> Given the short period of time, it would be wise to focus towards open
>>>>> issues which are bugs, rather than introducing any new feature or trying to
>>>>> enhance the framework. As the framework upgrades are planned for next major
>>>>> version.
>>>>>
>>>>>
>>>>> Ideally we can start a poll and which ever issues gets the highest
>>>>> vote can be prioritized. But many of us might be already working on the
>>>>> open issues or already have a fix, so let us first make a list of
>>>>> Contributors and respective issues that they are interested in. Also, let's
>>>>> share the feedback in the next 10 days which is on or before 20th Aug.
>>>>>
>>>>> Based on this input then we can finalize the distribution of issues
>>>>> among the contributors and take it forward.
>>>>>
>>>>> Suggestions open, I am just initiating the thought.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> http://www.vtiger.com/
>>>>
>>>> _______________________________________________
>>>> http://www.vtiger.com/
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>
>> _______________________________________________
>> http://www.vtiger.com/
>
> _______________________________________________
> http://www.vtiger.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20210810/3d6c9f46/attachment.html>