User forums > General (but related to Code::Blocks)
8.03 release?
Biplab:
I believe we have enough persons available to make a release. We don't need another dev to do that (though new devs are always welcome). Most important think we need is "Our Willingness to Release Regularly". We do have several Linux/Mac packagers with us and Killerbot can package for Windows platform. I don't see any reason that we can't make a release at the moment.
MortenMacFly:
--- Quote from: Biplab on January 23, 2010, 02:54:56 pm ---I don't see any reason that we can't make a release at the moment.
--- End quote ---
I do. Yiannis has basically no time. Without him we are lost.
Biplab:
--- Quote from: MortenMacFly on January 23, 2010, 02:58:10 pm ---
--- Quote from: Biplab on January 23, 2010, 02:54:56 pm ---I don't see any reason that we can't make a release at the moment.
--- End quote ---
I do. Yiannis has basically no time. Without him we are lost.
--- End quote ---
Sorry. I can't agree on this. :)
Absence of devs can always happen in an Open-source project. We have our regular jobs to do to earn our bread and butter. On top of that our family also needs a fair bit of time from us. During this economic crisis our job life has become even tougher. So when we combine them we may not have enough time for C::B, which is fair enough.
However the project should not suffer due to absence of dev/project leader. You can consult with Yiannis if necessary and just get his "OK" message through chat. If we are unable to contact him, we can also consult Thomas on this.
What I mean is we should commit ourselves on releasing a new build at a timely interval. It's really needed for the benefit of C::B.
MortenMacFly:
--- Quote from: Biplab on January 23, 2010, 03:21:44 pm ---What I mean is we should commit ourselves on releasing a new build at a timely interval.
--- End quote ---
Agreed. Still: We do have a lot to do for a release which is a high workload. For example: Collecting all packages (of one stream-line); editing the webpage and updating it to a new version, upload binaries, update links etc. This can only be done by a person with edit rights on our webpage and (at least) upload rights at BerliOS. That's why I've proposed to kind of "outsource" packaging to a motivated (new?!) team member with nothing else but doing that. I think it's enough work already and IMHO exactly the reason why nothing but nightlies happens.
I can't do all of that because I am not producing packages for any other OS than Windows and I simply don't have the time. And I don't see any of us being able to do that alone. So it must be a collaborate work (as always). Hence on co-coordinator that knows what to do can track and collect everything needed whenever it's time for a release. If anyone of us is willing to do that step forward. If its a team member I don't mind.
Biplab:
--- Quote from: MortenMacFly on January 23, 2010, 03:34:28 pm ---
--- Quote from: Biplab on January 23, 2010, 03:21:44 pm ---What I mean is we should commit ourselves on releasing a new build at a timely interval.
--- End quote ---
I can't do all of that because I am not producing packages for any other OS than Windows and I simply don't have the time. And I don't see any of us being able to do that alone. So it must be a collaborate work (as always). Hence on co-coordinator that knows what to do can track and collect everything needed whenever it's time for a release. If anyone of us is willing to do that step forward. If its a team member I don't mind.
--- End quote ---
Agreed, it's a lot of work to do.
Due to lack of time I also can't commit on taking care of entire release process. However I can do a part of it (e.g., coordinating the release process by collecting and publishing binary or even more if needed). We need to discuss this in details on who should be responsible for which part of the process.
But before that we all need to agree on one thing - that is we'll be releasing within a reasonable period of time (say within 2-3 months). We can definitely sort out things thereafter.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version