My responses to some of Paul's comments:

- Forking for 1.3.x - We should fork for 1.3.x once the first release candidate (or alpha?) version is released.  In other words, fork as part of cutting the release.  That should keep us focused on 1.3.x until the first iteration is out.  While we are iterating, we want to keep merging between master and master-1.3.x easy.

- MS SQL / ADODB:
a. I agree that we should evaluate progress made on 1.3.x and advertise achieved improvements.  That doesn't mean we can't look into other options for 1.4 and have even better improvements.
b. The place to keep MS SQL is a fork under your GitHub account.  As per discussion with Paul earlier, I would like the master-2.x branch to move to Paul's github account, same applies for the new branch that should contain current master + db changes.  Remember, just keep it a single purpose branch - not Paul's goodness branch :)
c. When to merge into master?
i. First, the team has reviewed and agreed about the high level change and the approach.  (DL discussion then pull request)
ii. Second, as late as possible to reduce merge pain - we don't want every bug fix in 1.3.x to be costly to merge into master due to the scope of the DB API call changes.  Hence, I recommend getting this merged pre-forking of 1.4.x.  That should come after the first couple of stable 1.3.x releases are out.

Thanks,
-Victor



On Fri, Oct 18, 2013 at 1:47 AM, Robert Munteanu <robert.munteanu@gmail.com> wrote:
On Fri, Oct 18, 2013 at 1:16 AM, Damien Regad <dregad@mantisbt.org> wrote:
> On 2013-10-17 22:30, Paul Richards wrote:
>> When can we branch master into master-1.3?
>
> IMO it would be a mistake to do this too early. We should at least wait
> until we reach a release candidate state before branching.

+1 . Do we really want to start development on 1.4 until 1.3 is stable
and has had some good exposure? Remember that some people ( myself
included ) simply stay away from the .0 or even .1 releases for really
important stuff.

I'd advise keeping focus on 1.3 for a bit longer.

>
>> I said in a round about way to victor/damien before [and maybe to list -
>> not sure], that I need mssql changes done by end of October. So to do
>> that properly, I've got 13 days to test db api changes, and need
>> somewhere to put them. It would strike me we could branch 1.3 off master
>> to do this now we've got most of everyone's commits in.
>
> I would prefer if you actually gave a try to Mantis as it is now with
> the latest ADODB, in theory (I can't test myself) MSSQL should be much
> better now.
>
> If you really want to move forward with this, I'd recommend you keep it
> in a private fork/branch for now, and most importantly, keep it
> up-to-date by frequently merging from master.

+1

>
>> Can we leave
>> publicising the oracle support off the 1.3 release notes?
>
> That's one of the major improvements we can "sell" to the users, I think
> it would be a mistake not to publicize it.

+1 . Unless we know it's broken, we should publicize it.

Robert

>
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> mantisbt-dev mailing list
> mantisbt-dev@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev



--
http://robert.muntea.nu/

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
mantisbt-dev mailing list
mantisbt-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev