Join us on irc.freenode.net in #fedora-meeting for this important
meeting, wherein we shall determine the readiness of the Fedora 18 Alpha.
As previously announced last week, we moved Go/No-Go to Thursday.
Thursday, August 30, 2012 @21:00 UTC (17:00 EDT/14:00 PDT/23:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."
"Verifying that the Release criteria are met is the responsibility of
the QA Team."
For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting
In the meantime, keep an eye on the Fedora 18 Alpha Blocker list:
http://qa.fedoraproject.org/blockerbugs/current
Jaroslav
--
Jaroslav Řezník <jreznik(a)redhat.com>
Your schedule wrangler
Office: +420 532 294 275
Mobile: +420 602 797 774
Red Hat, Inc. http://www.redhat.com/
Fedora 18 Alpha Release Readiness Meeting.
date: 2012-08-23
place: irc.freenode.net in #fedora-meeting-1
time: 19:00 UTC (3 PM Eastern, 12 PM Pacific, 21 PM CEST)
This Thursday, August 23, we will meet to make sure we are coordinated
and ready for the public release of Fedora 18 Alpha on Tuesday, August
28, 2012. Please note that this meeting will occur on August 23 *even
if the release is delayed at the Go/No-Go meeting on August 22.* - in
half hour (I tell you secret - it's going to be No-Go...).
This meeting works best when we have representatives from all of the
teams, so we'll be looking for the following people to attend or send a
representative in their place. Unfortunately I won't be available
during the whole day (see PS...), so let's hope we'll meet.
We will meet in #fedora-meeting-1 because of conflict in meeting
schedules.
Ambassadors -- Christoph Wickert
Design -- Máirín Duffy
Documentation -- Ben Cotton
FESCo -- Kevin Fenzi
Fedora Engineering Manager -- Tom "Spot" Callaway
Fedora Project Leader -- Robyn Bergeron
Infrastructure -- Kevin Fenzi
Marketing -- Robyn Bergeron
Quality -- Adam Williamson
Release Engineering -- Dennis Gilmore
Translation -- Noriko Mizumoto
Websites -- Kévin Raymond
PS: Sorry for late announce but you know, life does not reflect schedules
and even Fedora is my true family, there's still one more important for
me...
Hello,
I would like to announce there is a new group for the drupal 7
version[1] of our FAS module. I have just added Paul Frields and Rabi
Shanker Gua (GSOC student) to the group. If anyone would like to work
on this module then feel free to contact me.
1: http://git.fedorahosted.org/git/drupal7-authfas.git
--
Peter Borsa
http://asrob.eu
gpg fingerprint: EF52 EF5D 9604 E11C 8219 242B AB24 5B0B C6CD 1242
On Fri, Aug 10, 2012 at 07:12:49PM +0200, Peter Borsa wrote:
> Hello Paul!
>
> I would like to ask something, Kevin (nirik) reported me that there is
> a cron error from Insight and I tried to fix that but I cannot.
[...snip...]
>
> " # Restore following two stanzas when D7 ports are ready
>
> drupal7::featurerepo { 'insight':
> extramodname => 'fedora-insight-features',
> extramodurl =>
> 'git://git.fedorahosted.org/git/fedora-insight-features.git',
> extramodbranch => 'd7-devel',
> }
>
> drupal7::themerepo { 'insight':
> extrathemename => 'fedora-insight-theme',
> extrathemeurl => 'git://git.fedorahosted.org/fedora-insight-theme.git',
> extrathemebranch => 'd7-devel',
> }
>
> drupal7::featurerepo { 'insight':
> extramodname => 'drupal6-authfas',
> extramodurl => 'git://git.fedorahosted.org/drupal6-authfas.git',
> extramodbranch => 'd7work',
> }
> "
>
> I think it would be better, if we would use one Feature repository
> that's why what do you think about we push the drupal 7 port of
> drupal6-authfas module to "fedora-insight-features" repository? Or do
> we create a new drupal7-authfas repository on fedorahosted?
Replying to logistics list to keep things transparent ;-)
Well, you *could* in theory put the D7 version of the authfas module
in 'fedora-insight-features'. But I think it might be hard to find
there in case someone comes looking for it.
Perhaps better would be to make a new 'drupal7-authfas' project and
simply clone the git history there? If the 'd7work' branch in
'drupal6-authfas' is where the new code lives currently, you could
just make that branch the new 'master' for a new 'drupal7-authfas'
project. I'm not a git wizard but it sounds do-able.
Helpful opinions appreciated!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
Peter, I've upgraded you to 'administrator' role for the
drupal6-authfas module. I wanted to ensure you were able to help
people gain commit access to the code as needed.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com