Menu
▾
▴
javapathfinder-devel
|
From: Taehoon L. <ta...@ky...> - 2008-04-24 09:06:17
|
First of all, Thank you for the acceptance. I've got e-mail from John Penix. This is answer for it. I already subscribed mailing-list and checked out code from repository However, I have one question. Will the JavaPathFidner's repository be used to commit my contributions? or another repository is used? |
|
From: John P. <jp...@go...> - 2008-04-24 17:12:49
|
Hi Taehoon, That is the repository - the NASA team is working straight from sourceforge. That being said, we will need to define some kind of process or protocol for having so many people working at once. Hopefully, in most cases people will be working on independent things. When this is not the case, we will have to coordinate merging one person's change into another person's work. We might also use branches so that we can check-in and review different pieces that don't quite work together yet. Thanks for asking this. This is a great example of how we will all work together to make everyones contributions add up into something very cool. John On Thu, Apr 24, 2008 at 1:47 AM, Taehoon Lee <ta...@ky...> wrote: > > First of all, Thank you for the acceptance. > > I've got e-mail from John Penix. > This is answer for it. > > I already subscribed mailing-list and checked out code from repository > > However, I have one question. > Will the JavaPathFidner's repository be used to commit my contributions? > or another repository is used? > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Javapathfinder-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javapathfinder-devel > > |
|
From: John P. <jp...@go...> - 2008-04-24 17:15:03
|
Hey Peter, Some of us, including me, might not be familiar with branching and merging in version control, specifically as done in subversion. Do you know of a good overview document we could share? If not, I'll "google" it and track on down. jp On Thu, Apr 24, 2008 at 10:11 AM, John Penix <jp...@go...> wrote: > Hi Taehoon, > > That is the repository - the NASA team is working straight from > sourceforge. > > That being said, we will need to define some kind of process or protocol > for having so many people working at once. Hopefully, in most cases people > will be working on independent things. When this is not the case, we will > have to coordinate merging one person's change into another person's work. > We might also use branches so that we can check-in and review different > pieces that don't quite work together yet. > > Thanks for asking this. This is a great example of how we will all work > together to make everyones contributions add up into something very cool. > > John > > > On Thu, Apr 24, 2008 at 1:47 AM, Taehoon Lee <ta...@ky...> > wrote: > >> >> First of all, Thank you for the acceptance. >> >> I've got e-mail from John Penix. >> This is answer for it. >> >> I already subscribed mailing-list and checked out code from repository >> >> However, I have one question. >> Will the JavaPathFidner's repository be used to commit my contributions? >> or another repository is used? >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save $100. >> Use priority code J8TL2D2. >> >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> _______________________________________________ >> Javapathfinder-devel mailing list >> Jav...@li... >> https://lists.sourceforge.net/lists/listinfo/javapathfinder-devel >> >> > |
|
From: Peter C. M. <Pet...@na...> - 2008-04-24 17:23:39
|
http://svnbook.red-bean.com/en/1.4/svn.branchmerge.html but I would prefer not to create branches w/o a real reason. If people work mostly in their sandboxes (i.e. JPF extensions) there should be no reason for branches (as long as the code compiles). If somebody works outside (i.e. in the core) I have to know, because I change a lot there and don't want to end up with endless merge efforts. Likewise, if I need to fix something for one project, I'd rather like to do this once, in one place -- Peter On Apr 24, 2008, at 10:14 AM, John Penix wrote: > Hey Peter, > > Some of us, including me, might not be familiar with branching and > merging in version control, specifically as done in subversion. Do > you know of a good overview document we could share? > > If not, I'll "google" it and track on down. > > jp > > On Thu, Apr 24, 2008 at 10:11 AM, John Penix <jp...@go...> > wrote: > Hi Taehoon, > > That is the repository - the NASA team is working straight from > sourceforge. > > That being said, we will need to define some kind of process or > protocol for having so many people working at once. Hopefully, in > most cases people will be working on independent things. When this > is not the case, we will have to coordinate merging one person's > change into another person's work. We might also use branches so > that we can check-in and review different pieces that don't quite > work together yet. > > Thanks for asking this. This is a great example of how we will all > work together to make everyones contributions add up into something > very cool. > > John > > > On Thu, Apr 24, 2008 at 1:47 AM, Taehoon Lee > <ta...@ky...> wrote: > > First of all, Thank you for the acceptance. I've got e-mail from > John Penix. This is answer for it. I already subscribed mailing- > list and checked out code from repository However, I have one > question. Will the JavaPathFidner's repository be used to commit my > contributions? or another repository is used? > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http:// > java.sun.com/javaone > _______________________________________________ > Javapathfinder-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javapathfinder-devel > > > |
|
From: John P. <jp...@go...> - 2008-04-24 17:34:36
|
Thanks Peter, I agree, creating branches should be a last resort. However, everyone will probably be synching and possibly merging and resolving, so they should be familiar with the general concepts. John On Thu, Apr 24, 2008 at 10:23 AM, Peter C. Mehlitz <Pet...@na...> wrote: > http://svnbook.red-bean.com/en/1.4/svn.branchmerge.html > > but I would prefer not to create branches w/o a real reason. If people work > mostly in their sandboxes (i.e. JPF extensions) there should be no reason > for branches (as long as the code compiles). If somebody works outside (i.e. > in the core) I have to know, because I change a lot there and don't want to > end up with endless merge efforts. Likewise, if I need to fix something for > one project, I'd rather like to do this once, in one place > > -- Peter > > > On Apr 24, 2008, at 10:14 AM, John Penix wrote: > >> Hey Peter, >> >> Some of us, including me, might not be familiar with branching and merging >> in version control, specifically as done in subversion. Do you know of a >> good overview document we could share? >> >> If not, I'll "google" it and track on down. >> >> jp >> >> On Thu, Apr 24, 2008 at 10:11 AM, John Penix <jp...@go...> wrote: >> Hi Taehoon, >> >> That is the repository - the NASA team is working straight from >> sourceforge. >> >> That being said, we will need to define some kind of process or protocol >> for having so many people working at once. Hopefully, in most cases people >> will be working on independent things. When this is not the case, we will >> have to coordinate merging one person's change into another person's work. >> We might also use branches so that we can check-in and review different >> pieces that don't quite work together yet. >> >> Thanks for asking this. This is a great example of how we will all work >> together to make everyones contributions add up into something very cool. >> >> John >> >> >> On Thu, Apr 24, 2008 at 1:47 AM, Taehoon Lee <ta...@ky...> >> wrote: >> >> First of all, Thank you for the acceptance. I've got e-mail from John >> Penix. This is answer for it. I already subscribed mailing-list and checked >> out code from repository However, I have one question. Will the >> JavaPathFidner's repository be used to commit my contributions? or another >> repository is used? >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save $100. >> Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// >> java.sun.com/javaone >> _______________________________________________ >> Javapathfinder-devel mailing list >> Jav...@li... >> https://lists.sourceforge.net/lists/listinfo/javapathfinder-devel >> >> >> >> > |
|
From: Peter C. M. <Pet...@na...> - 2008-04-25 18:11:37
|
Hi GSoC'ers,
Since Taehoon brought it up, here's the answer reg. how we handle
repository access: "it depends" (<quote>Back off, man. I'm a
scientist</quote>)
More specifically, the mentors will decide this on a per-project
basis, with the following options:
(a) work on a separate project repository that only uses JPF binaries
(preferably new Sourceforge project, under open source license)
(b) work on JPF trunk but in sandbox (JPF extension)
NO unannounced changes to core!
NO commits that don't compile!
(c) work on public JPF branch,
merge down is responsibility of student,
merge up is responsibility of mentor
(d) work on private copy of repository,
submit patches to mentor (who merges into trunk)
I'm pretty agnostic as to what option to choose, as long as we
- don't end up with tons of branches
- don't get any surprise core changes
- don't break the trunk build with extension commits
The overall goal is that we don't step on each others toes, don't
break JPF for other users, minimize merge efforts, and maximize
student exposure (after all, who does all the goodies deserves the
public credit).
Students - please discuss with your mentors
Mentors - please let me know who needs repository access, and make
sure everybody who does has a Sourceforge account
-- Peter
---------------------------------------------------------------------
Peter C. Mehlitz Robust Software Engineering Group
PSGS/NASA Ames Research Center Pet...@na...
M/S 269-3 http://ti.arc.nasa.gov/people/mehlitz
Moffett Field, CA 94035 (650) 604-1682
On Apr 24, 2008, at 1:47 AM, Taehoon Lee wrote:
>
> First of all, Thank you for the acceptance. I've got e-mail from
> John Penix. This is answer for it. I already subscribed mailing-
> list and checked out code from repository However, I have one
> question. Will the JavaPathFidner's repository be used to commit my
> contributions? or another repository is used?
> ----------------------------------------------------------------------
> ---
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://
> java.sun.com/javaone_______________________________________________
> Javapathfinder-devel mailing list
> Jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javapathfinder-devel
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X