RE: [Rainbowportal-devel] Why CVS is unused?
Brought to you by:
danijel_kecman,
manudea
From: Jonathan M. <jon...@jo...> - 2005-05-03 00:20:20
|
Hmmm..Well, The aim is that over the course of the next few weeks we are doing a few things, 1) stabilize the solution to represent 1.5 SP1, this means reproducing any changes that have been made to CVS that haven't been reproduced yet one of the reasons I encourage any active developer to contact the bet...@ra..., so that you can be working on making that happen. 2) Introduce the new Page Manager, Forum Module, File Manager and whatever else gets done in time 3) Finish testing and familiarizing ourselves with working with SVN. The goal being moving development to there so we get to benefit from all the SVN offers. 4) Introduce the different layers of development. Dev->test->staging->release . This way the code to be considered for release has gone through the process of being developed, tested, received its feedback and should then be considered ready to be a public release. This can then happen more regularly and with less issues if the processes are ironed out through a multi step process. 5) Ability to manage module images and css in theme directories 6) Some changes/updates to modules such as discussion, sitemap, file directory tree and others Currently we have a functioning SVN solution for the beta solution, we are just working on learning to administer it better and with more ease, ironing out any issues so to speak, so that when the masses move from CVS to SVN hopefully it's as smooth as possible. I think that over the next few weeks, things will become much clearer and easier for everyone, as more instructions and transitions come into play. For now I just Urge that anyone who is actively coding currently, should be making an effort to work with or on the betateam at this point, so that we can roll out a top notch SP1 for RB 1.5 as well as implement some much needed upgrades in the organization, switching from CVS -> SVN, and assuring a better development process that guarantees rainbow continues to improve on its reputation and quality while still growing both its community and code base. I think that it's amazing that so many people seem to be getting excited and showing lots of interest. I can assure you that although there are concerns, and a few bumps here and there, I strongly believe, and I think after following in the discussions and agreemenets over the past few months, what we are trying to do is put some of those things into action, that have been being spoken about more many months. I think its a lot of reasons to get excited, and like any changes it's hard at first and nerve recking but most often for the best. The fact that there are so many updates to the CVS solution as well as the beta solution just means we have a great many people excited about working and coding for rainbow, making it a better project than ever before I believe. But with a growth in numbers, we need more organization as well to support the community. To many people download CVS to have it be a test solution. So If anyone is an SVN wizard, and want to help us get on the ball quicker, you can contact the beta team. If you are actively working on the cvs core or modules, fixing bugs, or working on something you want to make for SP1 then I suggest you contact the beta team. Ok, well. If there are any questions, feel free to ask more, maybe some other people working on the beta stuff and pushing on getting "order to the chaos", you can review the message boards in the beta yahoo group to see some of the discussion and details as to the design plans. Regards, Jonathan _____ From: rai...@li... [mailto:rai...@li...] On Behalf Of Mike Stone Sent: Monday, May 02, 2005 3:22 PM To: rai...@li... Subject: Re: [Rainbowportal-devel] Why CVS is unused? Yes, I see your point. How can you go to Jira and work on issues when CVS is no longer being maintained with code changes. The Beta Team does have a lot of changes and is only a small number of us. I know they are working hard to get a place for everyone to hook back up and be a community again. Now if you make changes to CVS (which I guess you can) then someone will have to run back to CVS and find out what you changed and move it to the new Beta Project. Jonathan, can you or Rahul share with the DeV list what is coming and the time line for it. Mike Stone Director of Computer Information Services Kaskaskia College 27210 College Road Centralia, IL 62801 618-545-3201 www.kaskaskia.edu >>> jvi...@po... 5/2/2005 03:33:53 >>> In the last weeks there are a lot of new development make by people work in groups controlled by leader's. This is dangerous for the project. The new sources are not accessible to all the people and there are a risk for repeated or not compatible development. A lot of valid developers can not have time now to create new sources, but they have time to testear and to solve small problems. I agree in some cases work in groups, but I'm absolutly desagree with not use CVS like a normal container for sources, included the new aggregations. |