[jsword-devel] [sword-devel] How to compile And Bible from jsword from the upstream repo?

[DM Smith]

I may have said it poorly. We weren't using a branching model. We tagged releases, but did not create a branch for stable against which changes could be submitted.

If we did, then Martin could have submitted changes against that and we could have integrated them into the main development stream.

Further the av11n work should have been done on it's own publicly visible development branch. That would have left trunk (aka master under git) as able to be released at any time.

Release frequency does play into it. But the development model lead to infrequent releases.

With git and continuous integration we should be able to release from master at any time with minimal effort.

Lots of ways to do it, but branching will be a boon. I'm looking forward to reading Matěj's links. I'm still not clear on the best dev model.

-- DM

On Oct 30, 2012, at 3:21 PM, Douglas Campos <qmx at qmx.me> wrote:

> 
> On Oct 30, 2012, at 11:27 AM, DM Smith wrote
>> While I agree with you, the way we had been maintaining JSword forced it. We were developing the next release on trunk (very bad idea). That prevented Martin from using it directly. Martin has done nothing sneaky (code is very visible and Martin has kept us in the loop on the changes), has been feeding some changes back into JSword and once av11n is done, then we can meld them back together.
> Are you sure that developing on trunk was the problem? Maybe release frequency, but developing the next version on trunk is a good idea in general :)
> 
>> But because of the downstream fork, it makes it hard for you/anyone to integrate av11n into AndBible.
>> 
>> In Him,
>> 	DM
>> 
>> 
>>> 
>>> Best,
>>> 
>>> Matěj
>>> 
>>> -- 
>>> http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz
>>> GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
>>> 
>>> This conversation can serve no purpose anymore. Good bye.
>>>  -- HAL9000 in 2001: Space Odyssea
>>> _______________________________________________
>>> jsword-devel mailing list
>>> jsword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>> 
>> 
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
> 
> -- qmx
> 
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel