[jsword-devel] JSword, Jira and the mailing list
christopher.burrell at gmail.com
Fri Apr 23 11:27:29 MST 2010
+1 for the new model. It would allow us to keep track of issues separately.
On 23 April 2010 02:11, Tonny Kohar <tonny.kohar at gmail.com> wrote:
> On Thu, Apr 22, 2010 at 6:28 PM, DM Smith <dmsmith at crosswire.org> wrote:
> > I'd like to propose a change to how we make changes to JSword.
> > For JSword I'd like to move toward a model that all changes are described
> > Jira. Jira is best when it is seen as a planning tool. I'd like to see
> > change described there and targeted to an appropriate release (which
> > based on circumstances). Patches would be attached to it, generated from
> > current trunk. By discussion in the issue, the patch would be iterated to
> > its final form with each version of the patch being appended to the
> > Under this model, Jira would be hooked into jsword-devel. If so, then
> > jsword-devel would be used for initial discussion and upon consensus an
> > issue would be created and then further discussion would happen w/in Jira
> > that issue. By having all changes described in Jira, it is easier to
> > generate release notes.
> > With time patches have a tendency to get stale and not apply cleanly. By
> > having them in Jira attached to issues, the burden to update them is
> > When they are submitted via a mailing list, they get lost and when they
> > emailed to me, I have the sole burden to keep them current and apply
> +1 for the proposed model
> Just wondering, currently who have the commit right ? is it only you
> (DM Smith) ?
> Tonny Kohar
> Alkitab Bible Study
> jsword-devel mailing list
> jsword-devel at crosswire.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jsword-devel