So I'm a little uncertain of the best path, my thoughts are along the
lines of:
There are a number of forks (lots) that have bug fixes which would be
useful to get into the 1.0 release.
I also get the impression that a number of the users of these forks have
fixes that they deem critical for their environment.
The question then is how many (if any) of these we should wrap up into
the 1.0 release.
One possible path is lets just do the 1.0 release as the code stands, so
that downloaders have some level of confidence when the get the 1.0
release and lets us get it out the door quickly.
We could then look at a 1.1 release that takes the bug fixes from these
many forks.
With either scenario we need to work out how we get the fixes from those
forks in to the 1.x release.
We can try contacting some of the developers (I've tried with some but
not all have email addresses attached) and request them to send us push
requests against the 1.x branch or failing that we could start picking
off bug fixes from those forks and generate the pull requests ourselves.
We also need to determine what versions of asterisk we will support for
1.0 vs 2.0
I've included asterisk-users on this thread as while these are
development issues I think we need to here what our users need.
So opinions on the best path?
So vote:
Issue 1:
Create release 1.0 using existing code with NO fixes, then 1.1 with fixes.
Create release 1.0 with fixes.
Issue 2:
Request developers to make push requests.
Marshall the forks and do push requests ourselves.
Issue 2 may be a noop in the sense that if fork developers don't respond
then we will have to do it ourselves.
Issue 3:
Choose which versions of asterisk must be supported in 1.0.
1.4
1.6
1.8
10
11
12
13
Choose which versions of asterisk must be supported in 2.0
1.4
1.6
1.8
10
11
12
13
14
Brett
On 15/04/15 06:03, Martin Duncan wrote:
>
> Brett,
>
> It all sounds good. Let me know which has the highest priority and I
> will start on that.
>
> Regards,
>
> Martin
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
> _______________________________________________
> Asterisk-java-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/asterisk-java-devel
--
S. Brett Sutton
Ph: 1300 NOOJEE (1300 666 533)
Noojee Telephony Solutions - On Demand Contact Centres Solutions
www.noojee.com.au
|
