Re: [Libreoffice-qa] Lifecycle of builds?

2013-04-12 Thread Petr Mladek
Robinson Tryon píše v Čt 11. 04. 2013 v 12:26 -0400:
 On Thu, Apr 11, 2013 at 4:08 AM, Petr Mladek pmla...@suse.cz wrote:
  Robinson Tryon píše v St 10. 04. 2013 v 11:29 -0400:
  I think that only the single EOL date make sense. We do not provide
  bugfix releases for bugfix releases. We provide bugfix releases for the
  minor version X.Y.
 
 +1
 
   Perhaps we could add some language on the ReleasePlan page to
  help telegraph the impending end of the series?
  ...
  I have updated the table title at
  https://wiki.documentfoundation.org/ReleasePlan to mention
  basic dates for the initial and bugfix releases. I wonder if this
  might be enough.
 
 I think that helps a bit. I believe I understand the situation a bit
 better now that we've had the conversation, but I'm still slightly
 confused about the versioning, and that makes me wonder if users would
 also find themselves confused :-)
 
 Taking the 3.6 branch as an example, the first release came out by Aug
 12th., after which point there were no new major/minor builds until
 4.0 was released just after 3.6.5 in February. That means that for 6
 months, the 3.6 branch was our most up-to-date release. That also
 means (if I understand correctly) that we didn't ship any new features
 for 6 months. Is that correct?

Yes, it is correct. I have just tried to slightly improve 
https://wiki.documentfoundation.org/ReleasePlan#Summary and
https://wiki.documentfoundation.org/ReleasePlan#Schedule

You might want to read the rules for committing into the different
branches, see https://wiki.documentfoundation.org/Development/Branches

In theory, it is possible to get feature even into the bugfix release.
In practice, it happens only for .1 or .2 bugfix release and only very
rarely. And it is never anything big. These are usually some changes
where it is hard to decide if it is a feature or a bug fix.

Also you might want to look at 
http://cgit.freedesktop.org/libreoffice/core/log/
http://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-4-0
It shows that master branch got more commits within last 24 hours than
the stable 4-0 branch within 2 weeks. It shows that we are pretty
conservative about the stable and feature complete branches.


Best Regards,
Petr

___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] minutes of ESC call ...

2013-04-12 Thread Eike Rathke
Hi,

On Thursday, 2013-04-11 18:19:08 +0100, Michael Meeks wrote:

   + work on fixing automated load test issues (Kendy,Fridrich,Eike)
 [ Kendy -8, Eike -2 so far ]

All Calc crashers of that set seem to be fixed now.

  Eike

-- 
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
For key transition see http://erack.de/key-transition-2013-01-10.txt.asc
Support the FSFE, care about Free Software! https://fsfe.org/support/?erack


pgp05HZ31WUPN.pgp
Description: PGP signature
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] Lifecycle of builds?

2013-04-12 Thread Robinson Tryon
On Fri, Apr 12, 2013 at 4:00 AM, Petr Mladek pmla...@suse.cz wrote:
 Taking the 3.6 branch as an example, the first release came out by Aug
 12th., after which point there were no new major/minor builds until
 4.0 was released just after 3.6.5 in February. That means that for 6
 months, the 3.6 branch was our most up-to-date release. That also
 means (if I understand correctly) that we didn't ship any new features
 for 6 months. Is that correct?

 Yes, it is correct. I have just tried to slightly improve
 https://wiki.documentfoundation.org/ReleasePlan#Summary and
 https://wiki.documentfoundation.org/ReleasePlan#Schedule

Looking good.

 You might want to read [...a bunch of stuff...]


So much to read! :-) I've read a bit of that, but I'll try to find
time to read more of that soon when I take a break from updating wiki
pages...

Regarding the EOL date, I've mocked-up an example of how we could
display it on the wiki page:
https://wiki.documentfoundation.org/Talk:ReleasePlan#Draft:_Adding_EOL_to_the_table

(I grabbed the date from the image; Petr's date was Aug 14, 2013,
which also sounds fine to me)

--R
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] Bugzilla administration info - 3.3 non releases removed from Version Selector

2013-04-12 Thread Rainer Bielefeld

As announced here
http://lists.freedesktop.org/archives/libreoffice-qa/2013-April/004128.html
today I unchecked Bugzilla flag Enabled For Bugs for following versions.

So following versions will be removed from the LibO Versions dropdown 
for bug reports and for editing existing bugs. The versions will stay 
available for Queries.


Version... Active   Bugs Action
---
3.3.0 Beta3No98  Delete: disabled months ago
3.3.0 RC1  No   127  Delete
3.3.0 RC2  No   146  Delete
3.3.0 RC3  No69  Delete
3.3.0 RC4  No70  Delete
3.3.1 RC1  No49  Delete
3.3.2 RC1  No18  Delete
3.3.2 RC2  No24  Delete

This measure is to keep size of the dropdown acceptable, I am planning 
the same for 3.4 when I see that we have more or less no more reports 
for 3.4-non-release Versions.


3.3.0 Beta2 for inherited bugs and the 3.3 releases will stay active for 
reports of bugs what appeared with 3.3.x. Exact Version info should be 
contributed in the bug report.


After a fix for Bug 55460 - BUGZILLAASSISTANT: Exclude inactive 
versions from version selector
 https://bugs.freedesktop.org/show_bug.cgi?id=55460 also BSA version 
picker will become a little shorter.


CU

Rainer


P.S.: In this thread I want to keep you up to date, discussion if 
desired please in extra threads to keep this one clear and short.

___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-qa] QA Team Email

2013-04-12 Thread Joel Madero
Unless there are complaints by Monday, QA team is going to request the
following email -- QA-Admin@ -- from TDF, we understand that it's a
tentative email and can be revoked at any time but feel like having a team
email that we can do things like mass close bugs on FDO is a good thing for
many reasons including:

1) Same email can be used for every mass change on fdo

2) For people CC'ed on bugs, they *may* be able to auto filter emails from
FDO if it's generated by a change done by this admin account

3) Professional to have an admin email

4) Will somewhat protect our QA team from complaints from users when we do
these mass changes, although we want to address as many complaints as
possible, it's not the responsibility of a single user to be blamed for a
QA team decision (such as closing bugs)


If there is an issue with this please let me know no later than Monday,
else I am going to request it and move forward with some of our FDO
projects.

Best,
Joel

-- 
*Joel Madero*
LibreOffice QA Volunteer
jmadero@gmail.com
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] QA Team Email

2013-04-12 Thread Kieran Peckett
What would that e-mail do? I'm new to the team so haven't been in on any
discussions about it.

On Friday, 12 April 2013, Joel Madero wrote:

 Unless there are complaints by Monday, QA team is going to request the
 following email -- QA-Admin@ -- from TDF, we understand that it's a
 tentative email and can be revoked at any time but feel like having a team
 email that we can do things like mass close bugs on FDO is a good thing for
 many reasons including:

 1) Same email can be used for every mass change on fdo

 2) For people CC'ed on bugs, they *may* be able to auto filter emails from
 FDO if it's generated by a change done by this admin account

 3) Professional to have an admin email

 4) Will somewhat protect our QA team from complaints from users when we do
 these mass changes, although we want to address as many complaints as
 possible, it's not the responsibility of a single user to be blamed for a
 QA team decision (such as closing bugs)


 If there is an issue with this please let me know no later than Monday,
 else I am going to request it and move forward with some of our FDO
 projects.

 Best,
 Joel

 --
 *Joel Madero*
 LibreOffice QA Volunteer
 jmadero@gmail.com javascript:_e({}, 'cvml',
 'jmadero@gmail.com');


___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] QA Team Email

2013-04-12 Thread Joel Madero
Certain members would have access to use it for things such as mass closing
bugs (which we are moving forward with as soon as we get this email
address). So we would have a FDO account linked to the email address where
we could manage mass bug changes very easily. That's one very important use
of it. Other uses will be to possibly announce QA policy changes as we
become more organized, possibly even to sent out our minutes/agenda from QA
calls (not sure about this one yet). Basically anything that is QA team
related vs. an individual making a point has the potential of going through
this email. Its use will be quite limited and hopefully this will help for
people to prioritize emails from this account accordingly.

Immediate use will be FDO management though.


Welcome to the team, haven't seen you on freenode but feel free to join us
at #libreoffice-qa :)


Best,
Joel


On Fri, Apr 12, 2013 at 11:34 AM, Kieran Peckett crazyske...@gmail.comwrote:

 What would that e-mail do? I'm new to the team so haven't been in on any
 discussions about it.


 On Friday, 12 April 2013, Joel Madero wrote:

 Unless there are complaints by Monday, QA team is going to request the
 following email -- QA-Admin@ -- from TDF, we understand that it's a
 tentative email and can be revoked at any time but feel like having a team
 email that we can do things like mass close bugs on FDO is a good thing for
 many reasons including:

 1) Same email can be used for every mass change on fdo

 2) For people CC'ed on bugs, they *may* be able to auto filter emails
 from FDO if it's generated by a change done by this admin account

 3) Professional to have an admin email

 4) Will somewhat protect our QA team from complaints from users when we
 do these mass changes, although we want to address as many complaints as
 possible, it's not the responsibility of a single user to be blamed for a
 QA team decision (such as closing bugs)


 If there is an issue with this please let me know no later than Monday,
 else I am going to request it and move forward with some of our FDO
 projects.

 Best,
 Joel

 --
 *Joel Madero*
 LibreOffice QA Volunteer
 jmadero@gmail.com




-- 
*Joel Madero*
LibreOffice QA Volunteer
jmadero@gmail.com
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/