allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pranav Sharma" <pranav.sharma.nits+allura...@gmail.com>
Subject [allura:tickets] #8116 Branches directly from Tickets.
Date Sun, 14 Aug 2016 16:58:18 GMT
I think the implementation won't be that difficult as we can provide one more option as to
which repo we actually want to relate that branch to.

Also it doesn't matter it there are multiple trackers as the purpose of this feature would
be like - 

>     Create a branch, in this SCM, to improve/fix the issue/feature specified in this
ticket.

As this is originally inspired by Jira (Atlassian) which provides such a functionality, we
can further add a Jira as a integrated service in allura projects.

And yeah, this can be extended by adding options to as suggested of creating and deleting
branches online. Though the stale branches issue will be resolved using the suggested means,
but creating a branch to solve a particular issue type of thing is a development cycle what
I have seen most agile teams follow. As it doesn't allows stale branches to exist in the first
place.


---

** [tickets:#8116] Branches directly from Tickets.**

**Status:** open
**Milestone:** unreleased
**Created:** Thu Aug 11, 2016 07:49 PM UTC by Pranav Sharma
**Last Updated:** Sun Aug 14, 2016 03:28 PM UTC
**Owner:** Pranav Sharma


One of the basic and maintainable style followed by teams is to create branches related to
tickets, and limiting the creation of branches. I think this is a common trend and we should
make a feature which would add an option on tickets page to instantly create a new branch
from desired base. I believe this would help definitely to manage rogue branches even for
frequent committers. Also it helps to directly match what code changes are related to a particular
ticket. 

This would be completely optional and a team can switch it on only if they would want to limit
and manage branches.

Any suggestions are welcome.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message