On Nov 6, 2008, at 17:20, David Evans wrote:
This being the case, I wonder if it would be useful to add a MacPorts
1.8.0 milestone to Trac and perhaps
a Macports 1.7.1 if minor releases are contemplated. This would allow
the release team a mechanism
for categorizing outstanding tickets in a way that is visible to the
community.
At this time, I'm not going to be going through tickets figuring out
what should be in what release. I'm not too fussed about release
numbering and such actually. I'm much more interested in releasing
what's on trunk, then adding more features and bug fixes on trunk,
then releasing that again, etc. I don't need milestones to do that.
Changes will get included in MacPorts when they're done. Others may
see it differently and want to prioritize certain things...
As of now, I see 84 open tickets assigned to MacPorts base bugs,
some of
which seem to have a
solution attached but for whatever reason have not been committed.
And
some of these have been
around for some time. A good example is #8221.
Have you tested the solution attached to that ticket? Does it work?
You could add a note to the ticket with your findings. I admit I have
not tested it.
Is there an effort afoot to address any low hanging fruit here that
can
be incorporated into a 1.7.0
release without too much effort? Or is it too late for that?
I'd rather not. We already have a year's worth of good changes in
trunk. I'd like to release that as 1.7.0 as soon as possible. Let's
not delay any further trying to fix other things.
The next release after 1.7.0 should appear in much less time so there
needn't be such a push to add more things to 1.7.0.
Perhaps some that are now irrelevant that can be closed out?
Is there anything that the rest of us can do to help?
Certainly you can examine the open bugs and see if they are still
relevant, and close them if not.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
