Milestones and branches, usage and cleanup

[noirbizarre]

Hi !

I've seen there is some milestones defined but I was wondering if they are up to date.
Same for branches (0.7, 0.8, 0.9): are they still in use ? Do thy reflect something real ? If not, why not remove them.

There still is a 0.8.x milestone: https://github.com/MongoEngine/mongoengine/milestones/0.8.x but with only one issue.

The 0.9.0 is released but there still is a 0.9.x milstones with 36 open issues.

How about a little cleanup with the following milstones:

• 0.9.1 with Pymongo3 compatibility #946
• 0.10 and a 0.10.1 to package fixes on 0.10.0
• 1.0

I think this will help releasing, and mongoengine users will be informed about the roadmap.

Keeping the "Scheduled, not planned", "Features we're unsure of" and "Needs more information" makes sense (it's clever for bug triage)

[MRigal]

Hi @noirbizarre

The whole mongoengine rep got really messy last year, when it was very poorly maintained. We are trying since a couple months to do better, also with additional maintainers. Your thoughts are fully right!

After the first cleaning and fire-clearing part, we are now tackling the organization. We are now attacking a second more organisational part, which includes milestones. Regarding the roadmap, instead of creating every time a new ticket and having infos hanging around in long discussions, I would tend to use the wiki, which is the sense of #983

We had recently a discussion (https://groups.google.com/forum/#!forum/mongoengine-dev) about the priority and severity for bugs triage. We really want to start again using the milestones. Consider almost all tagging as outdated and not anymore accurate.

Regarding the milestones, we'll need a discussion, as for me the next release should be a 0.10.0, since we removed django from the mongoengine core. And I think a 1.0 is still very far from becoming real. We will need 2-3 more big releases before that.

[MRigal]

@rozza can I delete the version branches? I also think they don't make much sense for now, as long as we have a "linear development" and we do not release minor fixes for older major versions

[mmellison]

To chime in along with @MRigal -- we're working on it :)

+1 for deleting the version branches and just using tags (since we're doing linear development).

Labels and milestones will definitely help organize things but honestly at the moment we're more focused on cutting down the backlog as a whole. We're still looking at ~180 open issues, some of which are no longer valid.

I plan on spending some time in the next few days cleaning up the issues. Honestly, I think we're at the point where we can close a lot of them out with a "Please re-open if the issue currently exists in the latest release." message.

[MRigal]

OK, I've cleaned and labelled quite a bit of the issues present, as well as moving 11 from the 36 open issues to a 0.10 milestone. I've put the deadline in one month, it is gonna be challenging, but still doable

[noirbizarre]

Great !

For people wanting to help, it gives directions !!

[MRigal]

Hi @noirbizarre you may also have a look (and edit) over here: https://github.com/MongoEngine/mongoengine/wiki

[noirbizarre]

Great !

I advise you to create the corresponding milestones right now to permit progressive bug triage on the topic.

[noirbizarre]

If you want to allow people to comment the roadmap, you should create an issue with the same content.

[MRigal]

We have a 0.10 milestone. I'm not sure the next ones need to be created already. Basically almost all open issues should be fixed before 1.0. The rest depends a bit on the motivation/intereset/focus of the contributors.
For the roadmap, you're right, here it is #996

[bagerard]

CLosing, outdated