26 May
2011
26 May
'11
11:19 a.m.
On Thu, May 26, 2011 at 07:13, Caleb James DeLisle
<calebdelisle(a)lavabit.com> wrote:
We have 17 unresolved issues which are labeled as
needed to be fixed for 3.1-RC1.
http://jira.xwiki.org/jira/secure/IssueNavigator!executeAdvanced.jspa?jqlQu…
Some of these issues are relatively new and others are quite old and have had their
fix-for version advanced at each release.
In my opinion setting a fix-for version is equivalent to making a promise to produce a
fix by a certain date.
To make a promise and fail to keep it is bad but making a habit of periodically breaking
promises and making new ones is far worse.
Since I have proposed a freeze on new features I would like to propose removing these fix
for versions.
WDYT?
+1 for new features/improment and not critical bug on which nobody is
working on of course but I can see there is at least one recent
regression in there ( XWIKI-6580 ) that should really be fixed as any
known regression. It should actually be a blocker if it's really a
regression.
Caleb
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne