> Paul: A polite way of not using "won't fix", and allowing easy tracking against db
> layer changes. Issues that need still apply to the new db layer will be
> brought back out of the suspended state during the next week.
[Victor] If something is not checked into "master" it doesn't exist and you shouldn't close pull requests or bugs because of it. And for something to make it to master, it has to go through the pull request+ review process.
>> Paul: It's fucking stupid that I can't use Mantis at work, due to the fact I'm
>> stuck waiting for a green light to work on DB changes I wrote and tested 2-3
>> years ago, and it's hindering my enjoyance of doing anything else productive
>> with Mantis. From either Saturday, or Monday I will be spending 3-5 hours
>> per day working on getting the new DB Layer into Mantis ( as quite frankly
>> I've had enough waiting). I don't really care if I spend those 3-5 hours a
>> day helping users convert old corrupt db's, coding, testing, or writing
>> emails to the mailing list, but I'm committed to putting in that amount of
>> time until 30th April. I will make sure I send either an updated pull
>> request or a status mail daily so that everyone is kept in the loop until
[Victor] As any change, you are always welcome to put together a pull request. You shouldn't be stuck for a green light to get the work done. Having said that from the project perspective, this is not the top priority compared to releasing 1.3. We should be taking a project-centric view of priorities. If it is really "hindering your enjoyance", why don't you focus on it rather than getting into source control plugin, html email notifications, etc. This basically paralyzes everyone else.
> Paul: And TBH, if that amount of effort is not enough to get stuff done, it's
> quite clear that mantis is not going anywhere.
[Victor] If we keep spending our energy talking about DBs (for every bug fix) and re-opening bugs and pull requests, yes, we won't be getting anywhere.