Shift 0.6 (1.0?)


Recommended Posts

This topic is to better organize our next release (0.6 or 1.0, I don't exactly know..) This is the team's place to basically debate, post, show, or rant about developing the next version. I think it would be best to post updates as we go along for organization.

Now I ask, do we make a dedicated 0.6 (or 1.0) topic on the regular Shift forums for people to post ideas (not problems, as we're going with a new base)?

And, Shift 0.6 (1.0) development by the Dev Team (Simon, Bulio, and I) will begin shortly after January 1st. Our release will be fast, and we should set up a few meetings and dates, and post them in here also. Organization is the key! :)

Link to comment
Share on other sites

I've posted too much recently! When are we releasing Shift 0.6? My guesstimate that would get us some time, and make January would be January 27. What do you guys think?

Link to comment
Share on other sites

I think 1.0 should wait until we have more than just graphics. Once we get a respository with some custom Neowin-branded software, then we should really just take our time and slowly move towards 1.0.

Now for release schedules, do we follow a "its ready when its ready" or a constant (ex. 6 month cycle) development pace?

Link to comment
Share on other sites

^ I think that we can slowly move toward 1.0 as Bulio says. However, I'd like to kick out 0.6 by the end of January, if that is not rushing it to much. We'll have a newer frame and an installer that works. This way we can have it tested by the masses and see how it works. The, if all goes well, we could set up a six month cycle.

Thoughts?

Link to comment
Share on other sites

Cool - what tools are you using to modify that?

Crimson will have to pipe in here. I suspect that we will use Max's coding skills to add scripts, GTK theming engines, and such. I'm sure we'll hear more in a bit.

Link to comment
Share on other sites

So Who is doing what and when will it be done? Bump bump**

We probably need a roll call from everyone to see where we stand. Please let us know what you have or are prepared to do at this time. Crimson, you may need to contact everyone individually either with IM or PM in order to see where we are.

Thanks, guys!

Link to comment
Share on other sites

I will be prepared to work on Shift tomorrow after homework, just tell me what we need done. Historically, I've done mainly Gnome work, but if you want me moved to something else...

And there's *potential* for a snow day on Monday, but there was also potential for one last Tuesday that didn't happen. You know what'll happen if I have a snow day, though, and it will involve Shift.

Link to comment
Share on other sites

I will be prepared to work on Shift tomorrow after homework, just tell me what we need done. Historically, I've done mainly Gnome work, but if you want me moved to something else...

And there's *potential* for a snow day on Monday, but there was also potential for one last Tuesday that didn't happen. You know what'll happen if I have a snow day, though, and it will involve Shift.

Working on Gnome will be be fine. We need to polish it, add themes, and branding. Thanks so much!

Link to comment
Share on other sites

Well I do think that getting the Wiki moving a bit would help. Perhaps if we have the lists of programs that will be included by default on the various versions of Shift, then I and others could write a bit on the Wiki about each one, so it doesn't all seem so alien for new users of Shift.

BTW, I am back fully on broadband from 24 January so will be able to do lots at the weekend and beyond.

Link to comment
Share on other sites

Quick response to kinetix63: We're using Reconstructor and the Ubuntu Customization Kit to essentially give us something to start with, then doing the rest in the terminal. It's essentially split 50/50 between graphical utilities and the CLI (with chroot, obviously).

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.