User forums > General (but related to Code::Blocks)

8.03 release?

<< < (2/10) > >>

zabzonk:
I'd just like to add a thought on the "official release" debate. I use the nightlies with no problems, but I also recommend CB to newbies very frequently on StackOverflow. and it's hard to explain to a newbie there all the steps they have to go through to get something reasonably up to date, and that will actually work. The result must be that a lot of fledgling C++ programmers are put off using CB and go elsewhere, to the eventual detriment of the community. An official release, or perhaps an "on-demand" installer would be very helpful to these people.

MortenMacFly:

--- Quote from: zabzonk on January 23, 2010, 11:01:08 am ---An official release, or perhaps an "on-demand" installer would be very helpful to these people.

--- End quote ---
What about simply renaming "nightlies" to "releases"?

zabzonk:

--- Quote ---What about simply renaming "nightlies" to "releases"?

--- End quote ---

Well, the nightly is just one part of the problem, there's MinGW, the documentation etc. as well. Getting a working setup isn't too hard, but a lot of these people are not techno sophisticates. Thinking about it, I may have  a go at writing a StackOverflow question  & answer that describes all the steps, for Windows at least.

MortenMacFly:
My general opinion on that topic:

If one is willing to start a project as an "official" release provider, step forward. I think it can be quite "easy", skills required are:
- you need at least to be able to compile wxWidgets and C::B yourself using the official sources and build tools
- you need to be able to update / run NSIS on Windows to create the installer
- you need to be able to provide packages for linus (e.g. deb) -> forum people may help here

For the setup I can imagine:
- we candidate a certain nightly for an official release
- after a few more nights (hehe) if no true show-stopper occur we agree that this is a new release candidate
- all packaging is done (including setting up a new version number)
- releases are officially provided to the C::B dev team for testing (basically "installing")
- releases are delivered to a C::B admin and will be propagated through our server

We could agree on doing that at round-about every quarter or half of a year. I'd propose the latter which means two times i the year the volunteer needs to get into action.

So... Who is willing and has the skills and time to do that?
Keep in mind: This should *not* be a short term support, but rather a long term support.

oBFusCATed:

--- Quote from: MortenMacFly on January 23, 2010, 02:02:30 pm ---If one is willing to start a project as an "official" release provider, step forward. I think it can be quite "easy", skills required are:
1 - you need at least to be able to compile wxWidgets and C::B yourself using the official sources and build tools
2 - you need to be able to update / run NSIS on Windows to create the installer
3 - you need to be able to provide packages for linus (e.g. deb) -> forum people may help here

--- End quote ---

1. Why one needs to compile anything, killerbot does that well for the nightlies and we can use the binaries from there?
2. I can update the installer from time to time, when a plugin/file is added, but I can't provide the resulting executable because my windows has viruses and I don't care to remove them.
3. Why would we care about the distros? If we have a release, that is easy to build, fetch and so on. They will build/update their packages.
4. On windows, will we bundle a compiler? Which one mingw or TDM?

Navigation

[0] Message Index

[#] Next page

[*] Previous page