[mantisbt-dev] Github milestones

[Damien Regad]

In light of the recent discussion started by vboctor on the next release,
and grangeway's intent of continuing to submit pull requests, I think it
would be good to be able to categorize those PRs that should make it in 1.3,
and the ones to be postponed to 2.x

Therefore I propose to create Milestones in our repository.

Thoughts ? Objections ?

D

[Roland Becker]

Maybe the easiest and a pragmatic way to be able to focus on 1.3 when viewing
again and again at open PR's.

But this will generate some additional work to syncronize the milestone
information in Github with target versions in our bug tracker where we have
existing issues.

I fear also that we will get even more PR's without related issues.
We might see a quite poor roadmap / change log if we work this way.

The cleaner? way would be:

- Enter issue if there is no existing one for a PR (at least after the PR got
+1)
- Add note with link to the PR
- Set target version

Post by Damien Regad
In light of the recent discussion started by vboctor on the next release,
and grangeway's intent of continuing to submit pull requests, I think it
would be good to be able to categorize those PRs that should make it in 1.3,
and the ones to be postponed to 2.x
Therefore I propose to create Milestones in our repository.
Thoughts ? Objections ?
D
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
mantisbt-dev mailing list
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

[Damien Regad]

Post by Roland Becker
Maybe the easiest and a pragmatic way to be able to focus on 1.3 when
viewing again and again at open PR's.

That's the goal - something quick and easy...

Post by Roland Becker
But this will generate some additional work to syncronize the milestone
information in Github with target versions in our bug tracker where we
have existing issues.

I really did not intend to use this to as a replacement or even complement
of the roadmap we maintain in the tracker through the target version - just
something to remind ourselves of the outcome of a discussion

Post by Roland Becker
I fear also that we will get even more PR's without related issues.

That's a risk indeed, although it is a separate discussion. I agree that
ideally we should have an issue on the tracker for every feature and bug fix.

Post by Roland Becker
We might see a quite poor roadmap / change log if we work this way.
- Enter issue if there is no existing one for a PR (at least after the PR got
+1)
- Add note with link to the PR
- Set target version

A better approach indeed, although it generates more overhead.

Now who can convince Paul to adhere to that ;-)