[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epp-dev] Query regarding Eclipse CVS repository
|
Hi Sandeep,
thanks for your interest... see my notes in your message below.
Maybe the newcomers forum (
http://www.eclipse.org/forums/index.php/i/2/) or the Eclipse Platform forum (
http://www.eclipse.org/forums/index.php/f/11/) can be another source of information. I've seen several similar questions in the past few years.
Regards,
Markus
On Thu, May 31, 2012 at 8:29 PM, Sandeep Krishnan
<krishsandy85@xxxxxxxxx> wrote:
Hello all,
I am a graduate student and my research involves studying Eclipse's CVS repository and bug database.
Maybe you should consider using the Git repositories, too, because many projects have migrated their code base from CVS to Git over the past 12 months. A good starting point is
http://git.eclipse.org/c/
I had a question regarding how the CVS repository is used. As far as I understand the development of Eclipse, the maintenance releases of one release (say Eclipse 3.6) and the milestone and RCs of Eclipse 3.7 happen somewhat in parallel (I got this mainly by seeing the release schedule of Eclipse). I wanted to know how the code development and commit into CVS works for this parallel development works. After say 3.6 is released sometime June, is it that the head revision continues with the development of the next release, 3.7? I saw some 3_x_maintenance branches but they have code only for some modules. Are these the branches where the SRs for a release are developed?
Yes, most Eclipse projects use these 'maintenance branches' for the service release development. Usually these maintenance branches contain bug fixes only. Which source code (HEAD, etc.) goes into a build of the next release depends from project to project. Many (but not all) projects require (or used to require with CVS, may have changed with Git...) that anything that is used in a build needs to be tagged first. Again, this is not true for each and every project.
And a related question is that whether there are different developer teams working on 3.6.1 and on 3.7 or do the same people work on both based on the priority of bugs?
You can always see who committed the source code... in all projects that I know it is the same team that works on the code base.
If there is any link or some guidelines on how this parallel development works, that may also be helpful.
I am posting it to this forum since the leaders of all projects are here. I apologize if it is the wrong place to post this query
Thanks,
Sandeep Krishnan
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
