Victor,
It was originally agreed ages ago to replace the DB Layer in the next
release after 1.2.
Every time I've tried to work on this, it's been blocked in some way. It's
depressing that despite known this plan that people have come along and
tried to fix the issues we are replacing the DB Layer to fix in the current
code - making it harder to port changes, and wasting work.
I've said multiple times that I need the new db layer in a release sooner
than later. You even said we could do a release with the new db layer soon
(within a month) after the 1.3 release when you offered that as a way
forwards.
Asking people who are interested in using the Mantis with other Databases
(e.g. pgsql, mssql and oracle) for feedback on the new DB Layer is the only
way to ensure we can do a release with the new DB Layer within a month of
1.3.
Personally, I feel that yet again yourself and Damien are attempting to
block and throw out the work on the new Db Layer. Even last week, Damien
'pushed' a wrong branch to Master with changes to the DB Layer in Mantis -
then apologies to the list when I queried the push. Damien offered to help
port patches from next to 1.3 and so far only things that have been ported
are patches I've ported.
If you can guarantee and promise we'll do what you originally said - a
release with the new DB Layer within 1 Month of 1.3, then I'll be happier,
but given the past record of people saying they'd go with a plan then
changing their mind, I'm not currently convinced.
Paul
On Tue, May 20, 2014 at 7:01 AM, Victor Boctor <***@outlook.com> wrote:
> +1 for all comments from Robert and Damien.
>
> Thanks Roland for volunteering to cleanup this mess.
>
> Paul,
>
> This is not the first time this happens and we are having such
> time-wasting-circular-frustrating conversations. And unfortunately, I can
> almost bet money it is not going to be the last.
>
> - Advertising db support as broken - we have been having conversations
> about this topic, going out and spamming the community that it is broken
> doesn't seem fit.
>
> - Contact ***@.... for testing - we have mentioned several times that we
> are focused on 1.3 and that we are only going to introduce any further
> releases when 1.3.0 stable is out.
>
> - I'm not sure what you are trying to do here? If you are really trying
> to get the new db layer out, then you should have less of the
> non-constructive discussions that slow down 1.3 and hence whatever follows
> that.
>
> My feel is that you have ignored all of us and went directly and pushed
> your opinion (who no one else seems to share) to a bunch of people in the
> community.
>
>
> > Date: Tue, 20 May 2014 07:21:17 +0200
> > From: ***@atrol.de
> > To: mantisbt-***@lists.sourceforge.net; ***@mantisbt.org
> > Subject: Re: [mantisbt-dev] Confusing bug changes related to database
> support
>
> >
> > IIRC correct there was a discussion for this about one year ago and we
> created
> > tags "2.0.x check" and "2.0.x fixed" for it.
> > Furtermore Paul created http://www.mantisbt.org/bugs/view.php?id=15720and
> > http://www.mantisbt.org/bugs/view.php?id=15721 for tracking purposes.
> > This is enough and I see no need for cloning issues. Adding a new tag
> like "DB
> > check" is also acceptable.
> >
> > If no one objects I will do the following cleanup, starting not earlier
> than
> > Friday, or maybe earlier if all agree.
> > - delete all cloned issue
> > - add tags "2.0.x check" where original issues don't have this tag
> > - remove the comments
> >
> > Roland
> >
> > > Damien Regad <***@mantisbt.org> hat am 20. Mai 2014 um 01:44
> geschrieben:
> > >
> > >
> > > Hi Robert,
> > >
> > > My thoughts exactly, thanks for your message. I had actually started
> > > writing a much nastier e-mail than the one you sent, but then I decided
> > > to withhold it. I'm glad you worded it in a much more calm and factual
> way.
> > >
> > > Paul,
> > >
> > > In addition to what Robert wrote, I would like to point out that this
> is
> > > not the first time that you're spamming the tracker like this. Please
> > > immediately stop
> > >
> > > 1. spamming the tracker with non-constructive comments
> > > 2. saying that DB xyz support is known broken
> > >
> > > Despite what you're pretending, your activity is not helping our users
> > > at all, it only creates confusion and projects a bad image of Mantis
> and
> > > of our team. So why don't you be constructive for a change, and help us
> > > testing and debugging 1.3 instead ?
> > >
> > > We've been through this several times before... I'm sure you remember
> > > that in January, Victor ended up cutting your access because of such
> > > behavior. Back then I defended you, but I'm sorry to say that lately
> > > I've been thinking that maybe he was right and I should have let it
> happen.
> > >
> > > There was a collective decision to release 1.3, with improved support
> > > for oracle and pgsql on the current DB layer, so just accept it and
> play
> > > along with the team - even if you don't like it. That's how democracy
> > > works.
> > >
> > > I've told you several times that I would help with 2.0 / db layer, but
> > > only *after* 1.3 is live. Until then, the focus is on 1.3 and anything
> > > you're doing against its release (like downvoting submitted changes)
> > > achieves nothing except further postponing the 2.0 go live and
> > > aggravating other team members.
> > >
> > > If you are not willing to play ball, then I believe the best thing for
> > > everyone involved would be if you went and released "GrangewayBT 1.0"
> on
> > > your own.
> > >
> > > Despite our increasingly frequent disagreements, I honestly think it
> > > would be a shame if you did, but we (I) just can't go on like this with
> > > you not pulling in the same direction as the rest of the team.
> > >
> > > Think about it. And do the right thing.
> > > Damien
> > >
> > >
> > >
> > > On 2014-05-19 16:18, Robert Munteanu wrote:> Hi all,
> > > >
> > > b> I've just noticed that a lot of bugs ( probaly related to dbtype !=
> > > > 'MySQL' ) have had this confusing process applied to them:
> > > >
> > > > - note added [1]
> > > > - issue cloned
> > > > - issue assigned to grangeway (Paul)
> > > > - note added again [1]
> > > >
> > > > The net result is that issues that were marked as fixed for
> 1.3.x.are
> > > > now open again, as clones, and we have a confusing note added all
> over
> > > > the place. My personal opinion about this is:
> > > >
> > > > - the bug-tracker should not be a task-list for in-progress
> rewrites.
> > > > One bug for that is fine ( e.g. 'Integrate DB API 2.0 ' )
> > > > - the notes about DB support are confusing and misleading
> > > >
> > > > Therefore my proposal is
> > > >
> > > > - resolve the newly created issues as won't fix or delete them
> outright
> > > > - remove all the comments similar to [1]
> > > >
> > > > Note that this is not a discussion about the new DB API and its
> > > > inclusion, or about notifying MantisBT users about early access to
> > > > not-yet-integrated features. It's a discussion about the process of
> > > > using the bugtracker, so please keep it this way.
> > > >
> > > > Thanks,
> > > >
> > > > Robert
> > > >
> > > >
> > > > [1]: MantisBT currently supports Mysql and has support for other
> > > > database engines.
> > > >
> > > > The support for other databases is known to be problematic.
> > > >
> > > > Having implemented the current database layer into Mantis 10 years
> > > > ago, I'm currently working on replacing the current layer.
> > > >
> > > > If you are interested in using Mantis with non-mysql databases - for
> > > > example, Oracle, PGSQL or MSSQL, and would be willing to help out
> > > > testing the new database layer, please drop me an email at
> > > > paul-P/***@public.gmane.org
> > > >
> > > > In the meantime, I'd advise running Mantis with Mysql Only to avoid
> > > issues.
> > > >
> > > > Thanks
> > > > Paul
> > > >
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> > > Instantly run your Selenium tests across 300+ browser/OS combos.
> > > Get unparalleled scalability from the best Selenium testing platform
> available
> > > Simple to use. Nothing to install. Get started now for free."
> > > http://p.sf.net/sfu/SauceLabs
> > > _______________________________________________
> > > mantisbt-dev mailing list
> > > mantisbt-***@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
> >
> >
> ------------------------------------------------------------------------------
> > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> > Instantly run your Selenium tests across 300+ browser/OS combos.
> > Get unparalleled scalability from the best Selenium testing platform
> available
> > Simple to use. Nothing to install. Get started now for free."
> > http://p.sf.net/sfu/SauceLabs
> > _______________________________________________
> > mantisbt-dev mailing list
> > mantisbt-***@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> mantisbt-dev mailing list
> mantisbt-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
>