RE: Porting Java Lucene 2.9 to Lucene.Net (was: RE: Lucene 2.9 RC2 now available for testing)
-Original Message- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Monday, August 31, 2009 1:00 AM To: java-dev@lucene.apache.org Subject: Re: Porting Java Lucene 2.9 to Lucene.Net (was: RE: Lucene 2.9 RC2 now available for testing) : My question is, I would prefer to track SVN commits to keep track of : changes, vs. what I'm doing now. This will allow us to stay weeks : behind a Java release vs. months or years as it is now. However, while : I'm subscribed to SVN's commits mailing list, I'm not getting all those : commits! For example, a commit made this past Friday, I never got an : email for, while other commits I do. Any idea what maybe going on? i suggest you track things based on a combination of svn base url (ie: trunk vs a branch) and the specific svn revision number at the moment of your latest checkout -- that way you don't even need to subscribe to the commit list, just do an svn diff -r whenever you have some time to work on it and see what's been committed since the last time you worked on it. Hell: you could probably script all of this and have hudson do it for you. -Hoss What we need is a way to map an SVN commit in Java Lucene to a Lucene.Net JIRA issue. This way, we can track and assign those JIRA issues as port tasks in Lucene.Net world. I don't know much about how SVN revision numbers work. If from SVN revision numbers, we can get back each commit, then this is the best solution (especially if hudson can do it for us). -- George - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Porting Java Lucene 2.9 to Lucene.Net (was: RE: Lucene 2.9 RC2 now available for testing)
: My question is, I would prefer to track SVN commits to keep track of : changes, vs. what I'm doing now. This will allow us to stay weeks : behind a Java release vs. months or years as it is now. However, while : I'm subscribed to SVN's commits mailing list, I'm not getting all those : commits! For example, a commit made this past Friday, I never got an : email for, while other commits I do. Any idea what maybe going on? i suggest you track things based on a combination of svn base url (ie: trunk vs a branch) and the specific svn revision number at the moment of your latest checkout -- that way you don't even need to subscribe to the commit list, just do an svn diff -r whenever you have some time to work on it and see what's been committed since the last time you worked on it. Hell: you could probably script all of this and have hudson do it for you. -Hoss - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Porting Java Lucene 2.9 to Lucene.Net (was: RE: Lucene 2.9 RC2 now available for testing)
On Aug 29, 2009, at 10:58 AM, George Aroush wrote: Hi Folks, I have been following the expected release of Lucene.Net 2.9 for some weeks now, and about 2 weeks ago, just before RC1 was released, I grabbed the code off the trunk and started my initial port. Today, I compared what I have with what's in RC2, only 6 Java files changes -- this is good. My question is, I would prefer to track SVN commits to keep track of changes, vs. what I'm doing now. This will allow us to stay weeks behind a Java release vs. months or years as it is now. However, while I'm subscribed to SVN's commits mailing list, I'm not getting all those commits! For example, a commit made this past Friday, I never got an email for, while other commits I do. Any idea what maybe going on? There has been some flakiness with ASF servers, so maybe that is the reason? Are you using forwarding on people.a.o? - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Porting Java Lucene 2.9 to Lucene.Net (was: RE: Lucene 2.9 RC2 now available for testing)
while I'm subscribed to SVN's commits mailing list, I'm not getting all those commits! For example, a commit made this past Friday, I never got an email for, while other commits I do. Any idea what maybe going on? There has been some flakiness with ASF servers, so maybe that is the reason? Are you using forwarding on people.a.o? No, I'm not using any forwarding. If the code, in the truck, goes through minimal changes for about 2 weeks, I should be fine (until when we figure out the mail issue). -- George - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Porting Java Lucene 2.9 to Lucene.Net
George Aroush wrote: while I'm subscribed to SVN's commits mailing list, I'm not getting all those commits! For example, a commit made this past Friday, I never got an email for, while other commits I do. Any idea what maybe going on? There has been some flakiness with ASF servers, so maybe that is the reason? Are you using forwarding on people.a.o? No, I'm not using any forwarding. If the code, in the truck, goes through minimal changes for about 2 weeks, I should be fine (until when we figure out the mail issue). -- George - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org Have you noticed it happen more than the one time? I've seen similar odd drops on the reg mailing list rarely - a random reply will show up to an original email I never got. Didn't notice it happen enough to claim its anything but bad luck though ;) It makes me wonder what I've missed and not realized though. I'm not forwarding either. bq. If the code, in the truck, goes through minimal changes for about 2 weeks, It should be fairly stable over the next week - bug fixes, build issues, and doc are still fair game, but it should be quite contained and rarely involve code changes (knock on wood). When we unfreeze, there is likely to be rapid development moving towards 3.0 - we will branch off 2.9 before that though, and you will probably want to move from trunk to the branch. -- - Mark http://www.lucidimagination.com - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Porting Java Lucene 2.9 to Lucene.Net
I have been watching SVN commits for about 2-3 weeks now (since the announcement that the trunk was going to be an RC) during this time, I have not received any email. It was emails from JIRA that hinted me at code checkin's. -- George -Original Message- From: Mark Miller [mailto:markrmil...@gmail.com] Sent: Saturday, August 29, 2009 11:56 AM To: java-dev@lucene.apache.org Subject: Re: Porting Java Lucene 2.9 to Lucene.Net George Aroush wrote: while I'm subscribed to SVN's commits mailing list, I'm not getting all those commits! For example, a commit made this past Friday, I never got an email for, while other commits I do. Any idea what maybe going on? There has been some flakiness with ASF servers, so maybe that is the reason? Are you using forwarding on people.a.o? No, I'm not using any forwarding. If the code, in the truck, goes through minimal changes for about 2 weeks, I should be fine (until when we figure out the mail issue). -- George - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org Have you noticed it happen more than the one time? I've seen similar odd drops on the reg mailing list rarely - a random reply will show up to an original email I never got. Didn't notice it happen enough to claim its anything but bad luck though ;) It makes me wonder what I've missed and not realized though. I'm not forwarding either. bq. If the code, in the truck, goes through minimal changes for about 2 weeks, It should be fairly stable over the next week - bug fixes, build issues, and doc are still fair game, but it should be quite contained and rarely involve code changes (knock on wood). When we unfreeze, there is likely to be rapid development moving towards 3.0 - we will branch off 2.9 before that though, and you will probably want to move from trunk to the branch. -- - Mark http://www.lucidimagination.com - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Porting Java Lucene 2.9 to Lucene.Net
I missed no commit mails the last days. Maybe they were declared as spam by your mail filter software? - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: George Aroush [mailto:geo...@aroush.net] Sent: Saturday, August 29, 2009 10:36 PM To: java-dev@lucene.apache.org Subject: RE: Porting Java Lucene 2.9 to Lucene.Net I have been watching SVN commits for about 2-3 weeks now (since the announcement that the trunk was going to be an RC) during this time, I have not received any email. It was emails from JIRA that hinted me at code checkin's. -- George -Original Message- From: Mark Miller [mailto:markrmil...@gmail.com] Sent: Saturday, August 29, 2009 11:56 AM To: java-dev@lucene.apache.org Subject: Re: Porting Java Lucene 2.9 to Lucene.Net George Aroush wrote: while I'm subscribed to SVN's commits mailing list, I'm not getting all those commits! For example, a commit made this past Friday, I never got an email for, while other commits I do. Any idea what maybe going on? There has been some flakiness with ASF servers, so maybe that is the reason? Are you using forwarding on people.a.o? No, I'm not using any forwarding. If the code, in the truck, goes through minimal changes for about 2 weeks, I should be fine (until when we figure out the mail issue). -- George - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org Have you noticed it happen more than the one time? I've seen similar odd drops on the reg mailing list rarely - a random reply will show up to an original email I never got. Didn't notice it happen enough to claim its anything but bad luck though ;) It makes me wonder what I've missed and not realized though. I'm not forwarding either. bq. If the code, in the truck, goes through minimal changes for about 2 weeks, It should be fairly stable over the next week - bug fixes, build issues, and doc are still fair game, but it should be quite contained and rarely involve code changes (knock on wood). When we unfreeze, there is likely to be rapid development moving towards 3.0 - we will branch off 2.9 before that though, and you will probably want to move from trunk to the branch. -- - Mark http://www.lucidimagination.com - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
