On Thu, 13 Nov 2014 04:43:39 +0100, Tommy ba...@quipo.it wrote:
On Wed, 12 Nov 2014 22:27:35 +0100, Joel Madero jmadero@gmail.com
wrote:
Fixed
thanks. one last fix needed.
4.3.3.2 is still credited as rc instead of release
bye, Tommaso
and the same regarding 4.3.4.1 rc which has
Hi,
On Thu, Nov 13, 2014 at 04:13:33PM +, Michael Meeks wrote:
* QA (Robinson)
There is a Bug Hunting Session for 4.4 coming up next week. If you did any
bigger refactoring or other work that primarily can be assumed to affect a
specific area of usecases, please add this to:
Hi Bjoern, all
On Fri, Nov 14, 2014 at 1:55 PM, Bjoern Michaelsen
bjoern.michael...@canonical.com wrote:
Hi,
On Thu, Nov 13, 2014 at 04:13:33PM +, Michael Meeks wrote:
* QA (Robinson)
There is a Bug Hunting Session for 4.4 coming up next week. If you did any
bigger refactoring or
On 2014-11-13 06:13 PM, Michael Meeks wrote:
* library bloat (Michael S)
+ not really an issue for release builds - --enable-mergelibs
+ big library + --enable-symbols - OOM
+ especially problematic CppuniTests with use_library_objects
+ perhaps a barrier to entry to
On Fri, Nov 14, 2014 at 03:42:16PM +0100, Sophie Gautier wrote:
Maybe it would be easier if I add the test cases to MozTrap? there could be
also a follow-up through the beta/rc/final.
Thank you, that would be great! I was suggesting to just edit the wiki as
telling hackers to enter stuff in
On Thu, 13 Nov 2014 07:13:29 +0100, Tommy ba...@quipo.it wrote:
sure, QA consensus is necessary, however please wait the official
release of 4.3.4 which is planned in Week 47 , Nov 17, 2014 - Nov 23,
2014 so we are sure the user will retest the bugs with the latest up to
date version
Hi Bjoern,
On Fri, Nov 14, 2014 at 5:37 PM, Bjoern Michaelsen
bjoern.michael...@canonical.com wrote:
On Fri, Nov 14, 2014 at 03:42:16PM +0100, Sophie Gautier wrote:
Maybe it would be easier if I add the test cases to MozTrap? there could
be
also a follow-up through the beta/rc/final.
Hi All,
I had recently been listening to a podcast and they mentioned that a
linux or bsd distro would have a keyword in its bug tracking system for
bugs that are worth mentioning in the release notes. So i was thinking
that a whiteboard keyword of the same could be done so that it is easy
to
Hi Jay,
Hi All,
I had recently been listening to a podcast and they mentioned that a
linux or bsd distro would have a keyword in its bug tracking system for
bugs that are worth mentioning in the release notes. So i was thinking
that a whiteboard keyword of the same could be done so that it is
Top posting reply to Joel's note...
Actually, it makes a lot of sense in that release notes really need a more
descriptive narrative for substantive enhancements and bug fixes. As is we
often simply list the fixes against prior releases.
Envision this whiteboard tagging would support two
10 matches
Mail list logo
