All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ferron <chris.e.ferron at linux.intel.com>
To: powertop@lists.01.org
Subject: [Powertop] [Announcement] PowerTOP Announcement
Date: Thu, 01 Nov 2012 09:40:03 -0700	[thread overview]
Message-ID: <5092A5E3.5070303@linux.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]

Hello,
     To day(November 1st 2012) marks string freeze for our next release 
cycle. Starting now until November 15th, we will only be taking bug 
fixes without string changes. The POT file has been updated to 
Transfex.net, and I will be pulling translation sever-times over the 
next 12 days. On November 12th I will pull translations for the last 
time, and only merge Major bugs fixes moving forward.

There is one date change for this release cycle. The community meeting 
was set for the November 22nd, but that actually falls on a US holiday.
So the community meeting will be moved back 1 day to November 21st.

Nov 1st (string freeze)
Nov 12th (stop taking all but critical patches)
Nov 15th (release v2.2)
Nov 22nd (community meeting about v2.3)

Community Meetings -
This meeting will be the first where members will contribute to what is 
added to PowerTOP's TODO list, discuss what PowerTOP needs for the next 
release. Feel free to post topics and start conversation threads prior 
to the meeting. We will gather topic that come up.

Meeting Times -
Location	        Local time	Time zone   UTC offset
Los Angeles (U.S.A)	8:00:00 AM	PST	    UTC-8
Moscow (Russia)	        8:00:00 PM	MSK	    UTC+4
London (UK)	        4:00:00 PM	GMT	    UTC

IRC# -
#PowerTOP on freenode.net


Cheers,
Chris


                 reply	other threads:[~2012-11-01 16:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5092A5E3.5070303@linux.intel.com \
    --to=powertop@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.