From: Paul D. <pau...@ds...> - 2006-11-17 23:33:15
|
Hi all, How come there are no entries for November in the jython-dev archive on SourceForge (http://sourceforge.net/mailarchive/forum.php?forum_id=5587)? |
From: Charlie G. <cha...@gm...> - 2006-11-18 02:31:31
|
Now that you've been welcomed to Jython, welcome to SourceForge! They have issues like this periodically, most frustratingly with svn. When it happens you can report it at https://sourceforge.net/tracker/?group_id=1&atid=200001 and they'll fix it. I just reported this. Charlie On 11/17/06, Paul Drummond <pau...@ds...> wrote: > Hi all, > > How come there are no entries for November in the jython-dev archive on > SourceForge (http://sourceforge.net/mailarchive/forum.php?forum_id=5587)? > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Charles O. N. <cha...@su...> - 2006-11-18 04:52:00
|
Charlie Groves wrote: > Now that you've been welcomed to Jython, welcome to SourceForge! They > have issues like this periodically, most frustratingly with svn. When > it happens you can report it at > https://sourceforge.net/tracker/?group_id=1&atid=200001 and they'll > fix it. I just reported this. It's that kind of nonsense that convinced us to move to Codehaus. Last year, the *week before JavaOne* CVS went down hard. That really pissed us off. Then on top of that there's the constant mailing list problems. No deal. -- Charles Oliver Nutter, JRuby Core Developer Blogging on Ruby and Java @ headius.blogspot.com Help spec out Ruby today! @ www.headius.com/rubyspec he...@he... -- cha...@su... |
From: Paul D. <pau...@ds...> - 2006-11-18 11:12:49
|
Based on what you were saying in your article Charles about inviting new developers to help give jython some new blood and direction, I wonder if a complete overhaul of the jython infrastructure would be feasible. Technical issues aside (hosting, etc), I would recommend using the *free* Trac system from Edgewall (http://trac.edgewall.org/) if such a massive change is considered possible. I use and administer a Trac system at work - it is an excellent system for bug tracking and general developer communication and management. It includes a fully integrated wiki and full integration with subversion also. Best of all, it is written in Python! On Saturday 18 November 2006 04:51, Charles Oliver Nutter wrote: > Charlie Groves wrote: > > Now that you've been welcomed to Jython, welcome to SourceForge! They > > have issues like this periodically, most frustratingly with svn. When > > it happens you can report it at > > https://sourceforge.net/tracker/?group_id=1&atid=200001 and they'll > > fix it. I just reported this. > > It's that kind of nonsense that convinced us to move to Codehaus. Last > year, the *week before JavaOne* CVS went down hard. That really pissed > us off. Then on top of that there's the constant mailing list problems. > No deal. |
From: Charles O. N. <cha...@su...> - 2006-11-18 16:31:33
|
Paul Drummond wrote: > Based on what you were saying in your article Charles about inviting new > developers to help give jython some new blood and direction, I wonder if a > complete overhaul of the jython infrastructure would be feasible. > > Technical issues aside (hosting, etc), I would recommend using the *free* Trac > system from Edgewall (http://trac.edgewall.org/) if such a massive change is > considered possible. > > I use and administer a Trac system at work - it is an excellent system for bug > tracking and general developer communication and management. It includes a > fully integrated wiki and full integration with subversion also. Best of all, > it is written in Python! Trac is pretty slicko; you'd need somewhere to host it though. Maybe that would work on SF, maybe not. Maybe you'd need somewhere else. SF isn't *awful* now, but it's certainly got its share of problems. I'd vote for a move to Trac, but it should happen quickly so as not to upset the flow of progress as things start to pick up. And if you could get Trac running under Jython, that would be worth even bigger headlines :) -- Charles Oliver Nutter, JRuby Core Developer Blogging on Ruby and Java @ headius.blogspot.com Help spec out Ruby today! @ www.headius.com/rubyspec he...@he... -- cha...@su... |
From: Paul D. <pau...@ds...> - 2006-11-18 20:26:02
|
On Saturday 18 November 2006 16:31, Charles Oliver Nutter wrote: > I'd vote for a move to Trac, but it should happen quickly so as not to upset > the flow of progress as things start to pick up. Anyone else? I realise it would be a big undertaking but from what I have read and seen, everything needs a serious overhaul anyway. Also, it would be a great way for me to get involved as I have lots of experience with Trac. > And if you could get Trac running under Jython, that would be worth even > bigger headlines :) Yes, that would be fantastic! :) :) |
From: A.M. K. <am...@am...> - 2006-11-18 21:36:55
|
On Sat, Nov 18, 2006 at 08:25:55PM +0000, Paul Drummond wrote: > Anyone else? I realise it would be a big undertaking but from what I have > read and seen, everything needs a serious overhaul anyway. Also, it would be FYI: we're in the slow process of moving CPython's bug tracking to Roundup. That's a sizable job, because we want to convert all the existing SourceForge bugs and patches and import them into the new tracker. One goal of the Roundup admins is to support multiple trackers, so if Roundup is suitable, that would also be an option. Even if you don't want to use Roundup, the people working on the task have written scripts to scrape bugs from SourceForge. That's probably still useful if you want to use some other bug tracker. Someone imported the data into a Trac setup; perhaps you can get their script. Join the tracker-discuss mailing list on python.org if this is of interest. There's no fixed schedule for the switchover yet, but I think the current goal is to switch CPython's bugs by December or January. --amk |
From: Frank W. <fwi...@gm...> - 2006-11-18 23:09:33
|
> FYI: we're in the slow process of moving CPython's bug tracking to > Roundup. That's a sizable job, because we want to convert all the > existing SourceForge bugs and patches and import them into the new > tracker. One goal of the Roundup admins is to support multiple > trackers, so if Roundup is suitable, that would also be an option. That is very interesting... I'm very interested in looking at roundup if CPython is going to use it. > > Even if you don't want to use Roundup, the people working on the task > have written scripts to scrape bugs from SourceForge. That's great! We'll definitely going to want to use those scripts if we decide to leave sourceforge. > Join the tracker-discuss mailing list on python.org if this is of > interest. There's no fixed schedule for the switchover yet, but I > think the current goal is to switch CPython's bugs by December or > January. I'll join the list, Thanks for the info! -Frank |
From: Charlie G. <cha...@gm...> - 2006-11-19 17:23:44
|
On 11/18/06, Frank Wierzbicki <fwi...@gm...> wrote: > > FYI: we're in the slow process of moving CPython's bug tracking to > > Roundup. That's a sizable job, because we want to convert all the > > existing SourceForge bugs and patches and import them into the new > > tracker. One goal of the Roundup admins is to support multiple > > trackers, so if Roundup is suitable, that would also be an option. > That is very interesting... I'm very interested in looking at roundup > if CPython is going to use it. I've got nothing but good things to say about roundup. We've used it as our bugtracker at work for the past few years and it's served admirably. The fact that we could migrate to it without having to do any conversion work from SourceForge is quite a bonus too. From what I've heard the sourceforge bug pages change enough that scraping tools have to be updated constantly to keep up. Charlie |
From: Paul D. <pau...@ds...> - 2006-11-19 18:47:27
|
Charlie Groves wrote: > I've got nothing but good things to say about roundup. We've used it > as our bugtracker at work for the past few years and it's served > admirably. For me, Trac wins over most bug-trackers because of it's wiki and subversion support, both of which are fully integrated. For example, I can create a new ticket in Trac describing a proposed change using wiki syntax then as changes are made I can link to the actual changesets which are displayed as pretty diffs within trac. Very nice :) I'm sure Roundup is very capable as a bug-tracker and as it's been chosen by the CPython team it's probably makes sense to go with it, but Trac has some great features that shouldn't be overlooked. Cheers, Paul. |
From: Frank W. <fwi...@gm...> - 2006-11-18 20:25:47
|
> Trac is pretty slicko; you'd need somewhere to host it though. Maybe > that would work on SF, maybe not. Maybe you'd need somewhere else. There is at least a chance that I can get Trac support for Jython at my day job (Red Hat) but no promises yet -- I'll have to ask around a little at work next week. Before I look into it, is this something that all the Jython developers could get behind? -Frank |
From: Oti <oh...@gm...> - 2006-11-26 20:58:56
|
sure! bugtrackers are made for bug tracking, so I certainly do not want to start another religious war. Oti. On 11/18/06, Frank Wierzbicki <fwi...@gm...> wrote: > > Trac is pretty slicko; you'd need somewhere to host it though. Maybe > > that would work on SF, maybe not. Maybe you'd need somewhere else. > There is at least a chance that I can get Trac support for Jython at > my day job (Red Hat) but no promises yet -- I'll have to ask around a > little at work next week. Before I look into it, is this something > that all the Jython developers could get behind? > > -Frank > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Frank W. <fwi...@gm...> - 2006-11-26 21:46:29
|
> There is at least a chance that I can get Trac support for Jython at > my day job (Red Hat) but no promises yet -- I'll have to ask around a > little at work next week. Given some new info (that the CPython folks are setting up a bug tracker with export/import scripts that we will be able to use) I want to wait and see how they do before I look into Trac support at Red Hat. -Frank |