|
List Info
Thread: Conference Call Re-scheduled
|
|
| Conference Call Re-scheduled |
|
2006-05-26 19:11:02 |
The weekly developer conference call has been rescheduled to
Wednesday,
May 31st, at 10 AM CDT (GMT -5), instead of Tuesday.
Please note that May 31st is the last day that new features
can be
merged into the trunk to be present for the upcoming 1.4
release. We
will likely be talking about any last minute additions that
need to be
made that day.
As always, if you have an item that you would like to
propose for
discussion on this call, please contact me off of the list.
Thanks,
Russell
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
| Conference Call Re-scheduled |
|
2006-05-26 20:08:50 |
On Friday, May 26, 2006, 15:11:02, Russell Bryant wrote:
> The weekly developer conference call has been
rescheduled to Wednesday,
> May 31st, at 10 AM CDT (GMT -5), instead of Tuesday.
On the subject of the conference calls, the last couple of
calls don't
have a recording available yet.
Are recordings no longer going to be made available or is it
just taking
a while?
--
rodd polylogics.com "The avalanche has already
started, it is too
Rod Dorman late for the pebbles to vote."
- Ambassador Kosh
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
| Conference Call Re-scheduled |
|
2006-05-27 14:51:03 |
On Fri, May 26, 2006 at 03:11:02PM -0400, Russell Bryant
wrote:
RB> The weekly developer conference call has been
rescheduled to Wednesday,
RB> May 31st, at 10 AM CDT (GMT -5), instead of Tuesday.
RB> Please note that May 31st is the last day that new
features can be
RB> merged into the trunk to be present for the upcoming
1.4 release. We
RB> will likely be talking about any last minute
additions that need to be
RB> made that day.
What about issue #6725?
--
JID: dsim.seiros.ru
ICQ: 58417635 (please, use jabber, if you can)
http://freesource.info/
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
| Conference Call Re-scheduled |
|
2006-05-27 15:10:18 |
On Saturday 27 May 2006 09:51, Denis Smirnov wrote:
> What about issue #6725?
Given that your patches are for oej's branch, specifically,
you
need to talk to oej.
--
Tilghman
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
| Conference Call Re-scheduled |
|
2006-05-27 16:01:22 |
On Sat, May 27, 2006 at 10:10:18AM -0500, Tilghman Lesher
wrote:
>> What about issue #6725?
TL> Given that your patches are for oej's branch,
specifically, you
TL> need to talk to oej.
This patch for trunk.
oej help me with just copy'n'paste my patches to
team/oej/codecnegotiation. Sometimes I create diff with
team/oej/codecnegotiation and trunk, and upload it to #6725.
--
JID: dsim.seiros.ru
ICQ: 58417635 (please, use jabber, if you can)
http://freesource.info/
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
| Conference Call Re-scheduled |
|
2006-05-28 04:02:27 |
Any possibility to:
* Add a short discussion on how to identify a commit as
an end-user
need-to-document change? I've gone through more
svn-commit messages
than I can remember looking for changes that change
end-user
functionality; any possibility of a character string
(ie *** or *&*)
to identify a commit which adds, modifies, or removes
a feature
available in /trunk or in /tags/1.4 to the end
Asterisk admin?
Changes mentioning doxygen or including
"\n" seem to make up a bulk
of the svn-commits I've saved for updating the docs
once the project
is up-to-date, but it'd be great to have a better
communication
system between developers and documentors.
* Discuss where to publish the docs, once up-to-date;
asteriskdocs.org? asterisk.org? digium.com? The
latest up-to-date
docs are here: http://mph.gotdns
.com:82/manual/en/
What's the date planned for the 1.4 release? I'm hoping
to get the docs
up-to-date and ready to publish a beta version of the
webdocs by that date,
though that depends on when the date is!
I'd be happy to be on the call as well, or just be a silent
party, if
developers would find that useful. Or just to harass me.
Beckman
------------------------------------------------------------
---------------
Peter Beckman
Internet Guy
beckmanpurplecow.com http://www.purplecow.com/
------------------------------------------------------------
---------------
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
| Conference Call Re-scheduled |
|
2006-05-28 06:59:11 |
We use mantis at work and have added a couple of custom
fields to the
tracker (using the custom fields option).
One of these is to notify training that there has been a
functionality
or UI changes that needs rollout. The trainers simply filter
all issues
with this flag set.
Julian.
Peter Beckman wrote:
> Any possibility to:
>
> * Add a short discussion on how to identify a
commit as an end-user
> need-to-document change? I've gone through more
svn-commit messages
> than I can remember looking for changes that
change end-user
> functionality; any possibility of a character
string (ie *** or *&*)
> to identify a commit which adds, modifies, or
removes a feature
> available in /trunk or in /tags/1.4 to the end
Asterisk admin?
>
> Changes mentioning doxygen or including
"\n" seem to make up a bulk
> of the svn-commits I've saved for updating the
docs once the project
> is up-to-date, but it'd be great to have a
better communication
> system between developers and documentors.
>
> * Discuss where to publish the docs, once
up-to-date;
> asteriskdocs.org? asterisk.org? digium.com?
The latest up-to-date
> docs are here: http://mph.gotdns
.com:82/manual/en/
>
> What's the date planned for the 1.4 release? I'm
hoping to get the docs
> up-to-date and ready to publish a beta version of the
webdocs by that date,
> though that depends on when the date is!
>
> I'd be happy to be on the call as well, or just be a
silent party, if
> developers would find that useful. Or just to harass
me.
>
> Beckman
>
------------------------------------------------------------
---------------
> Peter Beckman
Internet Guy
> beckmanpurplecow.com http://www.purplecow.com/
>
------------------------------------------------------------
---------------
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|
|
[1-7]
|
|