Menu
▾
▴
subtext-devs — For devs of Subtext. Please keep non-dev discussion in the subtext-users list.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(238) |
Jun
(130) |
Jul
(92) |
Aug
(54) |
Sep
(12) |
Oct
(30) |
Nov
(26) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(126) |
Feb
(592) |
Mar
(301) |
Apr
(266) |
May
(147) |
Jun
(220) |
Jul
(261) |
Aug
(704) |
Sep
(227) |
Oct
(239) |
Nov
(561) |
Dec
(273) |
| 2007 |
Jan
(331) |
Feb
(443) |
Mar
(294) |
Apr
(512) |
May
(316) |
Jun
(213) |
Jul
(66) |
Aug
(135) |
Sep
(189) |
Oct
(150) |
Nov
(77) |
Dec
(39) |
| 2008 |
Jan
(26) |
Feb
(28) |
Mar
(112) |
Apr
(197) |
May
(121) |
Jun
(131) |
Jul
(251) |
Aug
(388) |
Sep
(79) |
Oct
(54) |
Nov
(69) |
Dec
(133) |
| 2009 |
Jan
(114) |
Feb
(7) |
Mar
(86) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|
From: Tim H. <ti...@ti...> - 2011-12-12 19:56:15
|
I just got a new Akismet key and seems to be working now. maybe i was hitting a limit on another one. ------- http://timheuer.com/blog/ twitter: @timheuer On Mon, Dec 12, 2011 at 12:51 AM, Simone Chiaretta < sim...@gm...> wrote: > This is strange... I'm not getting any spam comment on my posts... > > On Mon, Dec 12, 2011 at 2:04 AM, Tim Heuer <ti...@ti...> wrote: > >> For the longest time my Akismet config with Subtext was GREAT. Over the >> past year it has been non-existent. Nothing in my error logs and I even >> upgraded to the paid Akismet account. Other sites (Wordpress) that use my >> Akismet account are working totally fine and stopping things regularly. >> >> Subtext just is allowing everything in right now. >> >> -th >> >> ------- >> http://timheuer.com/blog/ >> twitter: @timheuer >> >> >> ------------------------------------------------------------------------------ >> Learn Windows Azure Live! Tuesday, Dec 13, 2011 >> Microsoft is holding a special Learn Windows Azure training event for >> developers. It will provide a great way to learn Windows Azure and what it >> provides. You can attend the event by watching it streamed LIVE online. >> Learn more at http://p.sf.net/sfu/ms-windowsazure >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > > > -- > Simone Chiaretta > Microsoft MVP ASP.NET - ASPInsider > Blog: http://codeclimber.net.nz > RSS: http://feeds2.feedburner.com/codeclimber > twitter: @simonech > > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Simone C. <sim...@gm...> - 2011-12-12 08:51:26
|
This is strange... I'm not getting any spam comment on my posts... On Mon, Dec 12, 2011 at 2:04 AM, Tim Heuer <ti...@ti...> wrote: > For the longest time my Akismet config with Subtext was GREAT. Over the > past year it has been non-existent. Nothing in my error logs and I even > upgraded to the paid Akismet account. Other sites (Wordpress) that use my > Akismet account are working totally fine and stopping things regularly. > > Subtext just is allowing everything in right now. > > -th > > ------- > http://timheuer.com/blog/ > twitter: @timheuer > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta Microsoft MVP ASP.NET - ASPInsider Blog: http://codeclimber.net.nz RSS: http://feeds2.feedburner.com/codeclimber twitter: @simonech Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Simon P. <si_...@ho...> - 2011-12-12 07:18:01
|
Hi Tim, your best bet would be to post on http://code.google.com/p/subtext/ Cheers Si ________________________________________________ Simon Philp w: www.siphilp.co.uk in: www.linkedin.com/in/siphilp t: twitter.com/siphilp Date: Sun, 11 Dec 2011 19:04:13 -0800 From: ti...@ti... To: sub...@li... Subject: [Subtext-devs] HttpHandlerConfiguration gone in 2.5 I'm just getting around to upgrading to 2.5 and some things are missing that I had previously customized (and weren't caught/warned by the upgrade tool). One that I can't identify the new pattern is to do custom handlers. In 2.1 I had this in my web.config: <HandlerConfiguration defaultPageLocation="DTP_.aspx" type="Subtext.Framework.UrlManager.HandlerConfiguration, Subtext.Framework"> <HttpHandlers> <HttpHandler pattern="(?:/about\.aspx)$" controls="about.ascx"/> </HttpHandlers> </HandlerConfiguration> Where do I place that now? I'm not on IIS7. -th ------- http://timheuer.com/blog/ twitter: @timheuer ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Subtext-devs mailing list Sub...@li... https://lists.sourceforge.net/lists/listinfo/subtext-devs |
|
From: Tim H. <ti...@ti...> - 2011-12-12 03:04:19
|
I'm just getting around to upgrading to 2.5 and some things are missing that I had previously customized (and weren't caught/warned by the upgrade tool). One that I can't identify the new pattern is to do custom handlers. In 2.1 I had this in my web.config: <HandlerConfiguration defaultPageLocation="DTP_.aspx" type="Subtext.Framework.UrlManager.HandlerConfiguration, Subtext.Framework"> <HttpHandlers> <HttpHandler pattern="(?:/about\.aspx)$" controls="about.ascx"/> </HttpHandlers> </HandlerConfiguration> Where do I place that now? I'm not on IIS7. -th ------- http://timheuer.com/blog/ twitter: @timheuer |
|
From: Tim H. <ti...@ti...> - 2011-12-12 01:57:49
|
For the longest time my Akismet config with Subtext was GREAT. Over the past year it has been non-existent. Nothing in my error logs and I even upgraded to the paid Akismet account. Other sites (Wordpress) that use my Akismet account are working totally fine and stopping things regularly. Subtext just is allowing everything in right now. -th ------- http://timheuer.com/blog/ twitter: @timheuer |
|
From: Christopher P. <chr...@bl...> - 2010-06-08 19:43:23
|
has an OSS license, FYI. http://www.jetbrains.com/eforms/openSourceRequest.action?licenseRequest=RSOSL -- -Christopher Pelatari | http://bluefenix.net |
|
From: Tim H. <ti...@ti...> - 2009-08-11 22:16:31
|
Just to follow up on this...after some extensive analysis/changes/etc with myself, Phil and Feedburner contacts, it looks like a race condition on BlogInfo.HostFullyQualifiedUrl. Bug logged: http://code.google.com/p/subtext/issues/detail?id=83 -th On Wed, Aug 5, 2009 at 3:17 PM, Tim Heuer <ti...@ti...> wrote: > Thanks Travis. I *finally* was able to reproduce it...after approximately > 4000 request testing :-) > > using this simple console code: > > WebClient wc = new WebClient(); > wc.Headers[HttpRequestHeader.UserAgent] = "FeedBurner/1.0 ( > http://www.FeedBurner.com)"; > > for (int i = 0; i < 300; i++) > { > Console.WriteLine(string.Format("Fetching {0}...", > i.ToString())); > wc.DownloadFile("http://timheuer.com/blog/feedburner.aspx", > string.Format("output/response{0}.xml", i.ToString())); > } > > I did eventually get some files that had https links on all the content. > For the life of me I cannot figure out where in Subtext this would be doing > it though! I'm guessing it has something to do with SubtextContext, but > can't see where the scheme would be switching. > > -th > > > On Wed, Aug 5, 2009 at 7:56 AM, Travis Illig <ti...@pa...>wrote: > >> I haven't seen this in my feed and I use Feedburner. I'll keep watching, >> though. >> -T >> -- >> Travis Illig >> http://www.paraesthesia.com >> >> >> On Tue, Aug 4, 2009 at 9:50 PM, Tim Heuer <ti...@ti...> wrote: >> >>> Hey all, >>> >>> I've been having problems with Feedburner lately. Subscribers have been >>> noting duplicates being delivered in my feed. The dupes are exact same >>> content, except one is delivering all links in HTTPS (all comments, image >>> refs, etc.). In talking with Google (yes, I FINALLY managed to get someone >>> on Feedburner to actually talk with), their diagnostics show that my feed is >>> delivering the content twice. >>> >>> I cannot find anything that would be causing this so I'm asking if you've >>> seen it. What might trigger a change in the content to cause the feed data >>> links to be in https? Note: NO content is in HTTPS that I'm linking to or >>> anything. >>> >>> I've spelunked the source for Subtext and didn't see anything glaring at >>> me, but hoping someone might have insights. >>> >>> -th >>> >>> SIDENOTE: we hard-code a check for "Feedburner" in the user agent for >>> delivering RSS feeds. We might want to flag a work item to make that more >>> flexible. i'm guessing Feedburner's user agent might change at some point >>> to "Google Feeds" and it would suck to have to ask users to upgrade their >>> bins just for a config change. >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>> 30-Day >>> trial. Simplify your report design, integration and deployment - and >>> focus on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> Subtext-devs mailing list >>> Sub...@li... >>> https://lists.sourceforge.net/lists/listinfo/subtext-devs >>> >>> >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > |
|
From: Simone C. <sim...@gm...> - 2009-08-06 18:29:27
|
No SSL... sorry On Thu, Aug 6, 2009 at 6:05 PM, Tim Heuer <ti...@ti...> wrote: > Anyone willing to let me peg your internal RSS feed for a few minutes? :-) > > I'm able to repro my SSL issue and want another to compare. > > My config: > -dedicated server running IIS6 using host headers and has a valid SSL cert > installed > -Subtext 2.1.x > -currently using feedburner to burn the feed > > Ideally I'd love to have someone as close to that config as possible. I'd > need your RSS feed that feedburner is looking at. It will basically be 1000 > requests :-) > > Replies offline if willing/able to help. > > Thanks, > > -th > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta Microsoft MVP ASP.NET - ASPInsider Blog: http://codeclimber.net.nz RSS: http://feeds2.feedburner.com/codeclimber twitter: @simonech Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Steven H. <ste...@gm...> - 2009-08-06 16:47:03
|
I'm hosting via Orcs Web, so shared server, II6, an no SSL... sorry. -steve On Thu, Aug 6, 2009 at 12:05 PM, Tim Heuer <ti...@ti...> wrote: > Anyone willing to let me peg your internal RSS feed for a few minutes? :-) > > I'm able to repro my SSL issue and want another to compare. > > My config: > -dedicated server running IIS6 using host headers and has a valid SSL cert > installed > -Subtext 2.1.x > -currently using feedburner to burn the feed > > Ideally I'd love to have someone as close to that config as possible. I'd > need your RSS feed that feedburner is looking at. It will basically be 1000 > requests :-) > > Replies offline if willing/able to help. > > Thanks, > > -th > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Tim H. <ti...@ti...> - 2009-08-06 16:05:56
|
Anyone willing to let me peg your internal RSS feed for a few minutes? :-) I'm able to repro my SSL issue and want another to compare. My config: -dedicated server running IIS6 using host headers and has a valid SSL cert installed -Subtext 2.1.x -currently using feedburner to burn the feed Ideally I'd love to have someone as close to that config as possible. I'd need your RSS feed that feedburner is looking at. It will basically be 1000 requests :-) Replies offline if willing/able to help. Thanks, -th |
|
From: Tim H. <ti...@ti...> - 2009-08-05 22:17:29
|
Thanks Travis. I *finally* was able to reproduce it...after approximately
4000 request testing :-)
using this simple console code:
WebClient wc = new WebClient();
wc.Headers[HttpRequestHeader.UserAgent] = "FeedBurner/1.0 (
http://www.FeedBurner.com)";
for (int i = 0; i < 300; i++)
{
Console.WriteLine(string.Format("Fetching {0}...",
i.ToString()));
wc.DownloadFile("http://timheuer.com/blog/feedburner.aspx",
string.Format("output/response{0}.xml", i.ToString()));
}
I did eventually get some files that had https links on all the content.
For the life of me I cannot figure out where in Subtext this would be doing
it though! I'm guessing it has something to do with SubtextContext, but
can't see where the scheme would be switching.
-th
On Wed, Aug 5, 2009 at 7:56 AM, Travis Illig <ti...@pa...>wrote:
> I haven't seen this in my feed and I use Feedburner. I'll keep watching,
> though.
> -T
> --
> Travis Illig
> http://www.paraesthesia.com
>
>
> On Tue, Aug 4, 2009 at 9:50 PM, Tim Heuer <ti...@ti...> wrote:
>
>> Hey all,
>>
>> I've been having problems with Feedburner lately. Subscribers have been
>> noting duplicates being delivered in my feed. The dupes are exact same
>> content, except one is delivering all links in HTTPS (all comments, image
>> refs, etc.). In talking with Google (yes, I FINALLY managed to get someone
>> on Feedburner to actually talk with), their diagnostics show that my feed is
>> delivering the content twice.
>>
>> I cannot find anything that would be causing this so I'm asking if you've
>> seen it. What might trigger a change in the content to cause the feed data
>> links to be in https? Note: NO content is in HTTPS that I'm linking to or
>> anything.
>>
>> I've spelunked the source for Subtext and didn't see anything glaring at
>> me, but hoping someone might have insights.
>>
>> -th
>>
>> SIDENOTE: we hard-code a check for "Feedburner" in the user agent for
>> delivering RSS feeds. We might want to flag a work item to make that more
>> flexible. i'm guessing Feedburner's user agent might change at some point
>> to "Google Feeds" and it would suck to have to ask users to upgrade their
>> bins just for a config change.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Subtext-devs mailing list
>> Sub...@li...
>> https://lists.sourceforge.net/lists/listinfo/subtext-devs
>>
>>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Subtext-devs mailing list
> Sub...@li...
> https://lists.sourceforge.net/lists/listinfo/subtext-devs
>
>
|
|
From: Travis I. <ti...@pa...> - 2009-08-05 14:56:41
|
I haven't seen this in my feed and I use Feedburner. I'll keep watching, though. -T -- Travis Illig http://www.paraesthesia.com On Tue, Aug 4, 2009 at 9:50 PM, Tim Heuer <ti...@ti...> wrote: > Hey all, > > I've been having problems with Feedburner lately. Subscribers have been > noting duplicates being delivered in my feed. The dupes are exact same > content, except one is delivering all links in HTTPS (all comments, image > refs, etc.). In talking with Google (yes, I FINALLY managed to get someone > on Feedburner to actually talk with), their diagnostics show that my feed is > delivering the content twice. > > I cannot find anything that would be causing this so I'm asking if you've > seen it. What might trigger a change in the content to cause the feed data > links to be in https? Note: NO content is in HTTPS that I'm linking to or > anything. > > I've spelunked the source for Subtext and didn't see anything glaring at > me, but hoping someone might have insights. > > -th > > SIDENOTE: we hard-code a check for "Feedburner" in the user agent for > delivering RSS feeds. We might want to flag a work item to make that more > flexible. i'm guessing Feedburner's user agent might change at some point > to "Google Feeds" and it would suck to have to ask users to upgrade their > bins just for a config change. > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Tim H. <ti...@ti...> - 2009-08-05 05:19:06
|
Hey all, I've been having problems with Feedburner lately. Subscribers have been noting duplicates being delivered in my feed. The dupes are exact same content, except one is delivering all links in HTTPS (all comments, image refs, etc.). In talking with Google (yes, I FINALLY managed to get someone on Feedburner to actually talk with), their diagnostics show that my feed is delivering the content twice. I cannot find anything that would be causing this so I'm asking if you've seen it. What might trigger a change in the content to cause the feed data links to be in https? Note: NO content is in HTTPS that I'm linking to or anything. I've spelunked the source for Subtext and didn't see anything glaring at me, but hoping someone might have insights. -th SIDENOTE: we hard-code a check for "Feedburner" in the user agent for delivering RSS feeds. We might want to flag a work item to make that more flexible. i'm guessing Feedburner's user agent might change at some point to "Google Feeds" and it would suck to have to ask users to upgrade their bins just for a config change. |
|
From: Yonah W. <yo...@wa...> - 2009-05-12 02:59:24
|
I have been enticed by Phil Haack's latest blog post to get some open source experience and figured his recommendation for subtext was as good as any other. I was going to start with unit tests or FxCop errors as per the suggestion on the wiki http://www.subtextproject.com/DesktopDefault.aspx?tabid=150 <http://www.subtextproject.com/DesktopDefault.aspx?tabid=150&pageID=31&pageN ame> &pageID=31&pageName= however it turns out that the links to the coverage reports are dead. Maybe I should start by updating the links in the wiki. Are there updated links? Is this still the recommended place to start? |
|
From: Phil H. <ph...@mi...> - 2009-03-29 17:51:24
|
Let's use the existing subtext Google Group for everything for both users and devs for now. But yeah, we should post a message there. PHil From: su...@go... [mailto:su...@go...] On Behalf Of Simone Chiaretta Sent: Sunday, March 29, 2009 7:37 AM To: sub...@li...; su...@go... Subject: [subtext] Re: [Subtext-devs] We are now live on Google Code! Another question: on SourceForge there is the forum. How are we going to deal with it? Maybe we can add another google group named subtext-users and write on SF that the forum is not going to be monitored by ST devs anymore and to post questions on Google Groups Ideas? Simone 2009/3/28 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Ok, please join http://groups.google.com/group/subtext-notifications if you want our commit emails etc... Phil From: Ray Booysen [mailto:ra...@ra...<mailto:ra...@ra...>] Sent: Saturday, March 28, 2009 2:57 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] We are now live on Google Code! Perfect! 2009/3/28 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Ok, so I'm hearing that we should create yet another Google group. How about: Subtext-Notifications It'll have * Commit emails * Issue Emails (aka when new issues are created) * Other emails generated by activity in the Subtext Google Code project... The existing Subtext google group will solely be for discussion. Does that sound good? Phil From: Simone Chiaretta [mailto:sim...@gm...<mailto:sim...@gm...>] Sent: Saturday, March 28, 2009 2:46 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] We are now live on Google Code! Yeah... let's get rid of that old baggage :) Simo 2009/3/28 Ray Booysen <ra...@ra...<mailto:ra...@ra...>> Might as well switch everything. Create another group and move over. :) 2009/3/28 Phil Haack <ph...@mi...<mailto:ph...@mi...>> p.s. I'll still use subtext-commits on sourceforge for commit emails. Feels weird to create a whole nother Google group just for commit emails and I don't want to spam the main group with commit emails. Any thoughts? Phil From: Jon Galloway [mailto:jon...@gm...<mailto:jon...@gm...>] Sent: Friday, March 27, 2009 4:53 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] We are now live on Google Code! Sounds good. Why stay on sourceforge for mailing lists? Any advantage over moving to Google discussions? I mean, if you're gonna move, might as well do it all at once. 2009/3/27 Steven Harman <ste...@gm...<mailto:ste...@gm...>> Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I'd be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...<mailto:ph...@mi...>] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li...<mailto:sub...@li...> Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let's continue to use this mailing list for developer discussions. For forums, let's use http://groups.google.com/group/subtext For issues, we'll use http://code.google.com/p/subtext/issues/list As we're ready to fix items, we can copy associated issues from SourceForge manually. I've copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don't have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I'd like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc... via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Ray Booysen ra...@ra...<mailto:ra...@ra...> ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Ray Booysen ra...@ra...<mailto:ra...@ra...> ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Subtext" group. To post to this group, send email to su...@go... To unsubscribe from this group, send email to sub...@go... For more options, visit this group at http://groups.google.com/group/subtext?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
From: Simone C. <sim...@gm...> - 2009-03-29 14:37:31
|
Another question: on SourceForge there is the forum. How are we going to deal with it? Maybe we can add another google group named subtext-users and write on SF that the forum is not going to be monitored by ST devs anymore and to post questions on Google Groups Ideas? Simone 2009/3/28 Phil Haack <ph...@mi...> > Ok, please join http://groups.google.com/group/subtext-notifications if > you want our commit emails etc… > > > > Phil > > > > *From:* Ray Booysen [mailto:ra...@ra...] > *Sent:* Saturday, March 28, 2009 2:57 PM > > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] We are now live on Google Code! > > > > Perfect! > > 2009/3/28 Phil Haack <ph...@mi...> > > Ok, so I’m hearing that we should create yet another Google group. How > about: > > > > Subtext-Notifications > > > > It’ll have > > · Commit emails > > · Issue Emails (aka when new issues are created) > > · Other emails generated by activity in the Subtext Google Code > project… > > > > The existing Subtext google group will solely be for discussion. > > > > Does that sound good? > > > Phil > > > > *From:* Simone Chiaretta [mailto:sim...@gm...] > *Sent:* Saturday, March 28, 2009 2:46 PM > > > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] We are now live on Google Code! > > > > Yeah... let's get rid of that old baggage :) > Simo > > 2009/3/28 Ray Booysen <ra...@ra...> > > Might as well switch everything. Create another group and move over. :) > > 2009/3/28 Phil Haack <ph...@mi...> > > > > p.s. I’ll still use subtext-commits on sourceforge for commit emails. Feels > weird to create a whole nother Google group just for commit emails and I > don’t want to spam the main group with commit emails. Any thoughts? > > > > Phil > > > > *From:* Jon Galloway [mailto:jon...@gm...] > *Sent:* Friday, March 27, 2009 4:53 PM > > > *To:* sub...@li... > > *Subject:* Re: [Subtext-devs] We are now live on Google Code! > > > > Sounds good. > > > > Why stay on sourceforge for mailing lists? Any advantage over moving to > Google discussions? I mean, if you're gonna move, might as well do it all at > once. > > > > 2009/3/27 Steven Harman <ste...@gm...> > > Branch-per-feature is precisely the way I'd like to work... assuming the > SCM supported branch/fork & merge as first-class citizens. An SCM like, > say... Git does just that. :) > > I'm fine with doing it in SVN as well, it just sucks that all of the > branching has to happen remotely, on the centralized repository, as that > causes a good deal of noise. Anyhow... let's try it, and if it falls on its > face, we'll try something else. > > -steve > > //---- 90% of being smart is knowing what you're dumb at ----// > http://stevenharman.net/ > > 2009/3/27 Phil Haack <ph...@mi...> > > After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers > do their work on a major feature in a private branch. Then when the feature > work is done, they request a code review before merging it into trunk. Kind > of a neat idea. > > > > What do you guys think about using that as our new workflow? If we did > that, I’d be happy to be a bit more liberal with giving commit access out. > > > > Tiny changes could still happen in trunk. But med to large features should > be done in a private branch. > > > > Phil > > > > *From:* Phil Haack [mailto:ph...@mi...] > *Sent:* Friday, March 27, 2009 4:25 PM > > > *To:* sub...@li... > > *Subject:* [Subtext-devs] We are now live on Google Code! > > > > Hi All, > > > > We are live on Google Code! http://code.google.com/p/subtext/ > > > > One cool thing about Google Code is how well it associates checkins with > issues if you follow the guidelines: > http://code.google.com/p/subtext/wiki/DeveloperGuide > > > > For now, let’s continue to use this mailing list for developer discussions. > For forums, let’s use http://groups.google.com/group/subtext > > > > For issues, we’ll use http://code.google.com/p/subtext/issues/list > > > > As we’re ready to fix items, we can copy associated issues from SourceForge > manually. I’ve copied a few already which are all assigned to me. If you > want to work on any of them, assign them to yourself. > > > > If you don’t have commit access yet, just attach a patch to an issue and > one of us will merge it in and/or grant you commit access. I’d like to have > tighter review process around code commits and accepting committers. One > cool thing about Google Code is you can request code reviews for commits > etc… via a commit checkin comment. > > > > http://code.google.com/p/support/wiki/CodeReviews > > > > Phil > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Ray Booysen > ra...@ra... > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Ray Booysen > ra...@ra... > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Phil H. <ph...@mi...> - 2009-03-29 06:25:15
|
When you check in fixes for an issue, please mark it as "Fixed". Also, be sure to occasionally run the query which shows issues that need to be verified http://code.google.com/p/subtext/issues/list?can=7&q=&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles It'd be great if we can get someone other than the person who fixed these items to help verify them. Phil |
|
From: Phil H. <ph...@mi...> - 2009-03-29 00:38:10
|
Don't forget to rate Subtext in the App Gallery. And download it via Web Platform Installer at least once. :) http://www.microsoft.com/web/gallery/SubText.aspx Phil |
|
From: Phil H. <ph...@mi...> - 2009-03-28 22:34:04
|
For now, I modified the guidelines in the wiki. If the change is a small change and you think one commit will resolve the issue, I'd suggest doing it directly in trunk and request a review. We can always revert the change if we don't like it. For larger changes where there may be multiple commits, it makes sense to require a private branch. Make sense? Phil |
|
From: Phil H. <ph...@mi...> - 2009-03-28 22:23:24
|
Ok, please join http://groups.google.com/group/subtext-notifications if you want our commit emails etc… Phil From: Ray Booysen [mailto:ra...@ra...] Sent: Saturday, March 28, 2009 2:57 PM To: sub...@li... Subject: Re: [Subtext-devs] We are now live on Google Code! Perfect! 2009/3/28 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Ok, so I’m hearing that we should create yet another Google group. How about: Subtext-Notifications It’ll have • Commit emails • Issue Emails (aka when new issues are created) • Other emails generated by activity in the Subtext Google Code project… The existing Subtext google group will solely be for discussion. Does that sound good? Phil From: Simone Chiaretta [mailto:sim...@gm...<mailto:sim...@gm...>] Sent: Saturday, March 28, 2009 2:46 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] We are now live on Google Code! Yeah... let's get rid of that old baggage :) Simo 2009/3/28 Ray Booysen <ra...@ra...<mailto:ra...@ra...>> Might as well switch everything. Create another group and move over. :) 2009/3/28 Phil Haack <ph...@mi...<mailto:ph...@mi...>> p.s. I’ll still use subtext-commits on sourceforge for commit emails. Feels weird to create a whole nother Google group just for commit emails and I don’t want to spam the main group with commit emails. Any thoughts? Phil From: Jon Galloway [mailto:jon...@gm...<mailto:jon...@gm...>] Sent: Friday, March 27, 2009 4:53 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] We are now live on Google Code! Sounds good. Why stay on sourceforge for mailing lists? Any advantage over moving to Google discussions? I mean, if you're gonna move, might as well do it all at once. 2009/3/27 Steven Harman <ste...@gm...<mailto:ste...@gm...>> Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I’d be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...<mailto:ph...@mi...>] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li...<mailto:sub...@li...> Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let’s continue to use this mailing list for developer discussions. For forums, let’s use http://groups.google.com/group/subtext For issues, we’ll use http://code.google.com/p/subtext/issues/list As we’re ready to fix items, we can copy associated issues from SourceForge manually. I’ve copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don’t have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I’d like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc… via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Ray Booysen ra...@ra...<mailto:ra...@ra...> ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Ray Booysen ra...@ra...<mailto:ra...@ra...> |
|
From: Ray B. <ra...@ra...> - 2009-03-28 21:57:12
|
Perfect! 2009/3/28 Phil Haack <ph...@mi...> > Ok, so I’m hearing that we should create yet another Google group. How > about: > > > > Subtext-Notifications > > > > It’ll have > > · Commit emails > > · Issue Emails (aka when new issues are created) > > · Other emails generated by activity in the Subtext Google Code > project… > > > > The existing Subtext google group will solely be for discussion. > > > > Does that sound good? > > > Phil > > > > *From:* Simone Chiaretta [mailto:sim...@gm...] > *Sent:* Saturday, March 28, 2009 2:46 PM > > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] We are now live on Google Code! > > > > Yeah... let's get rid of that old baggage :) > Simo > > 2009/3/28 Ray Booysen <ra...@ra...> > > Might as well switch everything. Create another group and move over. :) > > 2009/3/28 Phil Haack <ph...@mi...> > > > > p.s. I’ll still use subtext-commits on sourceforge for commit emails. Feels > weird to create a whole nother Google group just for commit emails and I > don’t want to spam the main group with commit emails. Any thoughts? > > > > Phil > > > > *From:* Jon Galloway [mailto:jon...@gm...] > *Sent:* Friday, March 27, 2009 4:53 PM > > > *To:* sub...@li... > > *Subject:* Re: [Subtext-devs] We are now live on Google Code! > > > > Sounds good. > > > > Why stay on sourceforge for mailing lists? Any advantage over moving to > Google discussions? I mean, if you're gonna move, might as well do it all at > once. > > > > 2009/3/27 Steven Harman <ste...@gm...> > > Branch-per-feature is precisely the way I'd like to work... assuming the > SCM supported branch/fork & merge as first-class citizens. An SCM like, > say... Git does just that. :) > > I'm fine with doing it in SVN as well, it just sucks that all of the > branching has to happen remotely, on the centralized repository, as that > causes a good deal of noise. Anyhow... let's try it, and if it falls on its > face, we'll try something else. > > -steve > > //---- 90% of being smart is knowing what you're dumb at ----// > http://stevenharman.net/ > > 2009/3/27 Phil Haack <ph...@mi...> > > After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers > do their work on a major feature in a private branch. Then when the feature > work is done, they request a code review before merging it into trunk. Kind > of a neat idea. > > > > What do you guys think about using that as our new workflow? If we did > that, I’d be happy to be a bit more liberal with giving commit access out. > > > > Tiny changes could still happen in trunk. But med to large features should > be done in a private branch. > > > > Phil > > > > *From:* Phil Haack [mailto:ph...@mi...] > *Sent:* Friday, March 27, 2009 4:25 PM > > > *To:* sub...@li... > > *Subject:* [Subtext-devs] We are now live on Google Code! > > > > Hi All, > > > > We are live on Google Code! http://code.google.com/p/subtext/ > > > > One cool thing about Google Code is how well it associates checkins with > issues if you follow the guidelines: > http://code.google.com/p/subtext/wiki/DeveloperGuide > > > > For now, let’s continue to use this mailing list for developer discussions. > For forums, let’s use http://groups.google.com/group/subtext > > > > For issues, we’ll use http://code.google.com/p/subtext/issues/list > > > > As we’re ready to fix items, we can copy associated issues from SourceForge > manually. I’ve copied a few already which are all assigned to me. If you > want to work on any of them, assign them to yourself. > > > > If you don’t have commit access yet, just attach a patch to an issue and > one of us will merge it in and/or grant you commit access. I’d like to have > tighter review process around code commits and accepting committers. One > cool thing about Google Code is you can request code reviews for commits > etc… via a commit checkin comment. > > > > http://code.google.com/p/support/wiki/CodeReviews > > > > Phil > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Ray Booysen > ra...@ra... > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Ray Booysen ra...@ra... |
|
From: Phil H. <ph...@mi...> - 2009-03-28 21:54:46
|
Ok, so I'm hearing that we should create yet another Google group. How about: Subtext-Notifications It'll have * Commit emails * Issue Emails (aka when new issues are created) * Other emails generated by activity in the Subtext Google Code project... The existing Subtext google group will solely be for discussion. Does that sound good? Phil From: Simone Chiaretta [mailto:sim...@gm...] Sent: Saturday, March 28, 2009 2:46 PM To: sub...@li... Subject: Re: [Subtext-devs] We are now live on Google Code! Yeah... let's get rid of that old baggage :) Simo 2009/3/28 Ray Booysen <ra...@ra...<mailto:ra...@ra...>> Might as well switch everything. Create another group and move over. :) 2009/3/28 Phil Haack <ph...@mi...<mailto:ph...@mi...>> p.s. I'll still use subtext-commits on sourceforge for commit emails. Feels weird to create a whole nother Google group just for commit emails and I don't want to spam the main group with commit emails. Any thoughts? Phil From: Jon Galloway [mailto:jon...@gm...<mailto:jon...@gm...>] Sent: Friday, March 27, 2009 4:53 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] We are now live on Google Code! Sounds good. Why stay on sourceforge for mailing lists? Any advantage over moving to Google discussions? I mean, if you're gonna move, might as well do it all at once. 2009/3/27 Steven Harman <ste...@gm...<mailto:ste...@gm...>> Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I'd be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...<mailto:ph...@mi...>] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li...<mailto:sub...@li...> Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let's continue to use this mailing list for developer discussions. For forums, let's use http://groups.google.com/group/subtext For issues, we'll use http://code.google.com/p/subtext/issues/list As we're ready to fix items, we can copy associated issues from SourceForge manually. I've copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don't have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I'd like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc... via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Ray Booysen ra...@ra...<mailto:ra...@ra...> ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Simone C. <sim...@gm...> - 2009-03-28 21:46:27
|
Yeah... let's get rid of that old baggage :) Simo 2009/3/28 Ray Booysen <ra...@ra...> > Might as well switch everything. Create another group and move over. :) > > 2009/3/28 Phil Haack <ph...@mi...> > > p.s. I’ll still use subtext-commits on sourceforge for commit emails. >> Feels weird to create a whole nother Google group just for commit emails and >> I don’t want to spam the main group with commit emails. Any thoughts? >> >> >> >> Phil >> >> >> >> *From:* Jon Galloway [mailto:jon...@gm...] >> *Sent:* Friday, March 27, 2009 4:53 PM >> *To:* sub...@li... >> *Subject:* Re: [Subtext-devs] We are now live on Google Code! >> >> >> >> Sounds good. >> >> >> >> Why stay on sourceforge for mailing lists? Any advantage over moving to >> Google discussions? I mean, if you're gonna move, might as well do it all at >> once. >> >> >> >> 2009/3/27 Steven Harman <ste...@gm...> >> >> Branch-per-feature is precisely the way I'd like to work... assuming the >> SCM supported branch/fork & merge as first-class citizens. An SCM like, >> say... Git does just that. :) >> >> I'm fine with doing it in SVN as well, it just sucks that all of the >> branching has to happen remotely, on the centralized repository, as that >> causes a good deal of noise. Anyhow... let's try it, and if it falls on its >> face, we'll try something else. >> >> -steve >> >> //---- 90% of being smart is knowing what you're dumb at ----// >> http://stevenharman.net/ >> >> 2009/3/27 Phil Haack <ph...@mi...> >> >> After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers >> do their work on a major feature in a private branch. Then when the feature >> work is done, they request a code review before merging it into trunk. Kind >> of a neat idea. >> >> >> >> What do you guys think about using that as our new workflow? If we did >> that, I’d be happy to be a bit more liberal with giving commit access out. >> >> >> >> Tiny changes could still happen in trunk. But med to large features should >> be done in a private branch. >> >> >> >> Phil >> >> >> >> *From:* Phil Haack [mailto:ph...@mi...] >> *Sent:* Friday, March 27, 2009 4:25 PM >> >> >> *To:* sub...@li... >> >> *Subject:* [Subtext-devs] We are now live on Google Code! >> >> >> >> Hi All, >> >> >> >> We are live on Google Code! http://code.google.com/p/subtext/ >> >> >> >> One cool thing about Google Code is how well it associates checkins with >> issues if you follow the guidelines: >> http://code.google.com/p/subtext/wiki/DeveloperGuide >> >> >> >> For now, let’s continue to use this mailing list for developer >> discussions. For forums, let’s use http://groups.google.com/group/subtext >> >> >> >> For issues, we’ll use http://code.google.com/p/subtext/issues/list >> >> >> >> As we’re ready to fix items, we can copy associated issues from >> SourceForge manually. I’ve copied a few already which are all assigned to >> me. If you want to work on any of them, assign them to yourself. >> >> >> >> If you don’t have commit access yet, just attach a patch to an issue and >> one of us will merge it in and/or grant you commit access. I’d like to have >> tighter review process around code commits and accepting committers. One >> cool thing about Google Code is you can request code reviews for commits >> etc… via a commit checkin comment. >> >> >> >> http://code.google.com/p/support/wiki/CodeReviews >> >> >> >> Phil >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > > > -- > Ray Booysen > ra...@ra... > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: <cod...@go...> - 2009-03-28 21:06:55
|
haacked commented on revision r3356 in project subtext. Details are at http://code.google.com/p/subtext/source/detail?r=3356 Score: Positive General Comment: Good catch! Respond to these comments at http://code.google.com/p/subtext/source/detail?r=3356 -- You received this message because you starred this review, or because your project has directed all notifications to a mailing list that you subscribe to. You may adjust your review notification preferences at: http://code.google.com/hosting/settings |
|
From: Ray B. <ra...@ra...> - 2009-03-28 07:32:47
|
Might as well switch everything. Create another group and move over. :) 2009/3/28 Phil Haack <ph...@mi...> > p.s. I’ll still use subtext-commits on sourceforge for commit emails. > Feels weird to create a whole nother Google group just for commit emails and > I don’t want to spam the main group with commit emails. Any thoughts? > > > > Phil > > > > *From:* Jon Galloway [mailto:jon...@gm...] > *Sent:* Friday, March 27, 2009 4:53 PM > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] We are now live on Google Code! > > > > Sounds good. > > > > Why stay on sourceforge for mailing lists? Any advantage over moving to > Google discussions? I mean, if you're gonna move, might as well do it all at > once. > > > > 2009/3/27 Steven Harman <ste...@gm...> > > Branch-per-feature is precisely the way I'd like to work... assuming the > SCM supported branch/fork & merge as first-class citizens. An SCM like, > say... Git does just that. :) > > I'm fine with doing it in SVN as well, it just sucks that all of the > branching has to happen remotely, on the centralized repository, as that > causes a good deal of noise. Anyhow... let's try it, and if it falls on its > face, we'll try something else. > > -steve > > //---- 90% of being smart is knowing what you're dumb at ----// > http://stevenharman.net/ > > 2009/3/27 Phil Haack <ph...@mi...> > > After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers > do their work on a major feature in a private branch. Then when the feature > work is done, they request a code review before merging it into trunk. Kind > of a neat idea. > > > > What do you guys think about using that as our new workflow? If we did > that, I’d be happy to be a bit more liberal with giving commit access out. > > > > Tiny changes could still happen in trunk. But med to large features should > be done in a private branch. > > > > Phil > > > > *From:* Phil Haack [mailto:ph...@mi...] > *Sent:* Friday, March 27, 2009 4:25 PM > > > *To:* sub...@li... > > *Subject:* [Subtext-devs] We are now live on Google Code! > > > > Hi All, > > > > We are live on Google Code! http://code.google.com/p/subtext/ > > > > One cool thing about Google Code is how well it associates checkins with > issues if you follow the guidelines: > http://code.google.com/p/subtext/wiki/DeveloperGuide > > > > For now, let’s continue to use this mailing list for developer discussions. > For forums, let’s use http://groups.google.com/group/subtext > > > > For issues, we’ll use http://code.google.com/p/subtext/issues/list > > > > As we’re ready to fix items, we can copy associated issues from SourceForge > manually. I’ve copied a few already which are all assigned to me. If you > want to work on any of them, assign them to yourself. > > > > If you don’t have commit access yet, just attach a patch to an issue and > one of us will merge it in and/or grant you commit access. I’d like to have > tighter review process around code commits and accepting committers. One > cool thing about Google Code is you can request code reviews for commits > etc… via a commit checkin comment. > > > > http://code.google.com/p/support/wiki/CodeReviews > > > > Phil > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Ray Booysen ra...@ra... |
755 messages has been excluded from this view by a project administrator.
