[RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread Jürgen Schmidt
Hi,

we are still verifying some fixes to identify the Beta as real beta,
means some branding elements, names etc. And we are working on some
serious bugfixes that we have identified already.

The current plan is to start the build tomorrow and do the upload over
the weekend. That means we should have a RC for AOO 4.1 beta available
at the beginning of next.

The new icons are still not complete and I am not sure how we can or
should continue here. Replacing them for the final release is probably
not a good idea.

Work remaining before beta

1) Defect verification

2) Release Notes
check, update and finalize the release notes [1]

3) Communications
Clarify the communication/promotion for the beta. For example how many
users do we want to reach with the beta.

4) Release vote

Based on this a possible schedule can be

March 4th: availability of AOO 41. Beta RC + start vote
March 10th: public availability of AOO 41. Beta (until March 31th)
...: additional snapshot builds based on the beta including showstopper
fixes
April 2th: availability of AOO 4.1 RC
April 7th: public availability of AOO 4.1

Any opinions or feedback
Juergen


[1]
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



Re: [RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread Vladislav Stevanovic
Is it too late for update Serbian language?
Wlada


2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com:

 Hi,

 we are still verifying some fixes to identify the Beta as real beta,
 means some branding elements, names etc. And we are working on some
 serious bugfixes that we have identified already.

 The current plan is to start the build tomorrow and do the upload over
 the weekend. That means we should have a RC for AOO 4.1 beta available
 at the beginning of next.

 The new icons are still not complete and I am not sure how we can or
 should continue here. Replacing them for the final release is probably
 not a good idea.

 Work remaining before beta

 1) Defect verification

 2) Release Notes
 check, update and finalize the release notes [1]

 3) Communications
 Clarify the communication/promotion for the beta. For example how many
 users do we want to reach with the beta.

 4) Release vote

 Based on this a possible schedule can be

 March 4th: availability of AOO 41. Beta RC + start vote
 March 10th: public availability of AOO 41. Beta (until March 31th)
 ...: additional snapshot builds based on the beta including showstopper
 fixes
 April 2th: availability of AOO 4.1 RC
 April 7th: public availability of AOO 4.1

 Any opinions or feedback
 Juergen


 [1]
 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org




Re: [RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread jan i
On 27 February 2014 16:58, Vladislav Stevanovic 
stevanovicvladis...@gmail.com wrote:

 Is it too late for update Serbian language?
 Wlada


 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com:

  Hi,
 
  we are still verifying some fixes to identify the Beta as real beta,
  means some branding elements, names etc. And we are working on some
  serious bugfixes that we have identified already.
 
  The current plan is to start the build tomorrow and do the upload over
  the weekend. That means we should have a RC for AOO 4.1 beta available
  at the beginning of next.
 
  The new icons are still not complete and I am not sure how we can or
  should continue here. Replacing them for the final release is probably
  not a good idea.
 
  Work remaining before beta
 
  1) Defect verification
 
  2) Release Notes
  check, update and finalize the release notes [1]
 
  3) Communications
  Clarify the communication/promotion for the beta. For example how many
  users do we want to reach with the beta.
 
  4) Release vote
 
  Based on this a possible schedule can be
 
  March 4th: availability of AOO 41. Beta RC + start vote


just for my understanding, dont we need to vote on the beta as well as the
release. We send the beta out to general public, that would normally
require a vote (might be a fast one).

rgds
jan I.


  March 10th: public availability of AOO 41. Beta (until March 31th)
  ...: additional snapshot builds based on the beta including showstopper
  fixes
  April 2th: availability of AOO 4.1 RC
  April 7th: public availability of AOO 4.1
 
  Any opinions or feedback
  Juergen
 
 
  [1]
 
 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
  For additional commands, e-mail: dev-h...@openoffice.apache.org
 
 



Re: [RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread Jürgen Schmidt
On 2/27/14 5:11 PM, jan i wrote:
 On 27 February 2014 16:58, Vladislav Stevanovic 
 stevanovicvladis...@gmail.com wrote:
 
 Is it too late for update Serbian language?
 Wlada


 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com:

 Hi,

 we are still verifying some fixes to identify the Beta as real beta,
 means some branding elements, names etc. And we are working on some
 serious bugfixes that we have identified already.

 The current plan is to start the build tomorrow and do the upload over
 the weekend. That means we should have a RC for AOO 4.1 beta available
 at the beginning of next.

 The new icons are still not complete and I am not sure how we can or
 should continue here. Replacing them for the final release is probably
 not a good idea.

 Work remaining before beta

 1) Defect verification

 2) Release Notes
 check, update and finalize the release notes [1]

 3) Communications
 Clarify the communication/promotion for the beta. For example how many
 users do we want to reach with the beta.

 4) Release vote

 Based on this a possible schedule can be

 March 4th: availability of AOO 41. Beta RC + start vote

 
 just for my understanding, dont we need to vote on the beta as well as the
 release. We send the beta out to general public, that would normally
 require a vote (might be a fast one).

exactly, --- availability of Beta RC + start vote ;-)

Juergen

 
 rgds
 jan I.
 
 
 March 10th: public availability of AOO 41. Beta (until March 31th)
 ...: additional snapshot builds based on the beta including showstopper
 fixes
 April 2th: availability of AOO 4.1 RC
 April 7th: public availability of AOO 4.1

 Any opinions or feedback
 Juergen


 [1]

 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes

 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org



 


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



Re: [RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread Rob Weir
On Thu, Feb 27, 2014 at 11:38 AM, jan i j...@apache.org wrote:
 On 27 February 2014 17:18, Jürgen Schmidt jogischm...@gmail.com wrote:

 On 2/27/14 5:11 PM, jan i wrote:
  On 27 February 2014 16:58, Vladislav Stevanovic 
  stevanovicvladis...@gmail.com wrote:
 
  Is it too late for update Serbian language?
  Wlada
 
 
  2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com:
 
  Hi,
 
  we are still verifying some fixes to identify the Beta as real beta,
  means some branding elements, names etc. And we are working on some
  serious bugfixes that we have identified already.
 
  The current plan is to start the build tomorrow and do the upload over
  the weekend. That means we should have a RC for AOO 4.1 beta available
  at the beginning of next.
 
  The new icons are still not complete and I am not sure how we can or
  should continue here. Replacing them for the final release is probably
  not a good idea.
 
  Work remaining before beta
 
  1) Defect verification
 
  2) Release Notes
  check, update and finalize the release notes [1]
 
  3) Communications
  Clarify the communication/promotion for the beta. For example how many
  users do we want to reach with the beta.
 
  4) Release vote
 
  Based on this a possible schedule can be
 
  March 4th: availability of AOO 41. Beta RC + start vote
 
 
  just for my understanding, dont we need to vote on the beta as well as
 the
  release. We send the beta out to general public, that would normally
  require a vote (might be a fast one).

 exactly, --- availability of Beta RC + start vote ;-)


 ?? you cannot make the beta available before the vote period for the beta
 ends.


Right.  That is what it says availability Beta RC.  It is only the
Release Candidate that is available before the vote.   Before we can
release the beta we need to have a release vote on the beta RC.

-Rob

 Then while the beta is out, we can of course vote for the release.

 rgds
 jan I.



 Juergen

 
  rgds
  jan I.
 
 
  March 10th: public availability of AOO 41. Beta (until March 31th)
  ...: additional snapshot builds based on the beta including showstopper
  fixes
  April 2th: availability of AOO 4.1 RC
  April 7th: public availability of AOO 4.1
 
  Any opinions or feedback
  Juergen
 
 
  [1]
 
 
 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
  For additional commands, e-mail: dev-h...@openoffice.apache.org
 
 
 
 


 -
 To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



Re: [RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread Rob Weir
On Thu, Feb 27, 2014 at 12:09 PM, Edwin Sharp el...@mail-page.com wrote:
 IMHO don't implement new icons. If beta is not general public then increase 
 RC-final duration.


One approach would be to have a quiet beta release, announced only
on dev, qa, users mailing lists and forum.That will attract users
who are already somewhat familiar with the product.

Some users might see it as well on our download webpage, but it would
not be the default choice.

So we might get 1000-2000 users of the beta.

If we think we want more, then we can promote it via blog, social
network, website home page, etc.  This will get more users,
potentially 100,000 or more.  But that does not mean we get more good
quality bug reports in BZ.  It could be messy.

So it is a trade-off.  If we wanted we could start small and then
increase the publicity after a week.

-Rob

 On Thu, Feb 27, 2014, at 17:50, Jürgen Schmidt wrote:
 Hi,

 we are still verifying some fixes to identify the Beta as real beta,
 means some branding elements, names etc. And we are working on some
 serious bugfixes that we have identified already.

 The current plan is to start the build tomorrow and do the upload over
 the weekend. That means we should have a RC for AOO 4.1 beta available
 at the beginning of next.

 The new icons are still not complete and I am not sure how we can or
 should continue here. Replacing them for the final release is probably
 not a good idea.

 Work remaining before beta

 1) Defect verification

 2) Release Notes
 check, update and finalize the release notes [1]

 3) Communications
 Clarify the communication/promotion for the beta. For example how many
 users do we want to reach with the beta.

 4) Release vote

 Based on this a possible schedule can be

 March 4th: availability of AOO 41. Beta RC + start vote
 March 10th: public availability of AOO 41. Beta (until March 31th)
 ...: additional snapshot builds based on the beta including showstopper
 fixes
 April 2th: availability of AOO 4.1 RC
 April 7th: public availability of AOO 4.1

 Any opinions or feedback
 Juergen


 [1]
 https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes

 -
 To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: qa-h...@openoffice.apache.org


 -
 To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: qa-h...@openoffice.apache.org


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



Re: New QA Volunteer

2014-02-27 Thread Rob Weir
On Wed, Feb 26, 2014 at 7:23 AM, Jochen Nitschke j.nitsc...@ok.de wrote:
 Hi,

 I would like to join the bugzilla qa-team (j.nitsc...@ok.de).
 My interests lie in code quality and I would like to learn more about
 unit testing.
 I read the good volunteer orientation till Level 3 dev  qa, subscribed
 some mailing lists and managed to compile the code.
 Is it possible to sign me up for mwiki too? I couldn't find a link.


Hello Jochen,

I've added you to the qa-team in Bugzilla, so you should be OK there now.

We had some spam issues on the MWiki and new accounts were suspended.
But Andrea might be able to help you get in.

As for testing, we're right now doing verification testing of the 4.1
beta release candidate, to make sure that the critical bugs that the
developers marked as fixed are actually fixed.   If you want to help
with that Yuzhen can help you get started.

But you mentioned unit testing...  You might want to ask on the dev
mailing list about that (d...@openoffice.apache.org).  QA doesn't touch
unit testing.   But we do have a Java/Eclipse based GUI automation
testing framework that needs some attention, if you are interested in
that.

Regards,

-Rob



 Best regards
 Jochen Nitschke


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



Re: [RELEASE]: refined AOO 4.1 beta schedule

2014-02-27 Thread Marcus (OOo)

Am 02/27/2014 04:50 PM, schrieb Jürgen Schmidt:

Hi,

we are still verifying some fixes to identify the Beta as real beta,
means some branding elements, names etc. And we are working on some
serious bugfixes that we have identified already.

The current plan is to start the build tomorrow and do the upload over
the weekend. That means we should have a RC for AOO 4.1 beta available
at the beginning of next.

The new icons are still not complete and I am not sure how we can or
should continue here. Replacing them for the final release is probably
not a good idea.

Work remaining before beta

1) Defect verification

2) Release Notes
check, update and finalize the release notes [1]

3) Communications
Clarify the communication/promotion for the beta. For example how many
users do we want to reach with the beta.

4) Release vote

Based on this a possible schedule can be

March 4th: availability of AOO 41. Beta RC + start vote
March 10th: public availability of AOO 41. Beta (until March 31th)
...: additional snapshot builds based on the beta including showstopper
fixes
April 2th: availability of AOO 4.1 RC
April 7th: public availability of AOO 4.1

Any opinions or feedback


I'll try to make one day off to be available on March 10th the whole 
day, so we can be flexible with announcements and publications.


Marcus




[1]
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org