[Vectorlinux-devel] Slack Builds and VL - my suggestions

[Tony B. <tb...@gm...>]

Sorry if this has already been decided upon but I haven't been made aware o=
f
it so here goes.

I have been looking at these as I'm sure some or all of you have as well.

I think we can work with these to build our base from source and then expan=
d
on them in the future.

There were a few of us on irc last night chatting about it.

This is how I think we should move forward with this:

1 - as a group, decide on all the packages for both std vl and soho before
we start
2 - 1 person designated to build the bare minimum base(a/ap/d/l/k source
trees) - probably either myself or Uel or anyone that wants to take
ownership of this task - all base build scripts need to be corrected for
arch,flags,etc
3 - once the base is built, each developer is given a source tree or trees
and they work on those on top of the base(vlbase.tgz).eg. kde,xap,etc - all
packages must be built on a virgin base except for soho - 2 groups are
needed here - std and soho and there will be some duplication as std and
soho should be treated as separate distros - all build scripts need to
corrected for arch,flags,etc
4 - we need to come up with SlackBuilds for the packages we include that
aren't in slack and split this up depending on how many pkgs there are
5 - upload all the built packages to the respective trees and each of us
install them for testing.
6 - once testing is completed, we package these up for the cd into
vl-base.tgz,vl-std.tgz, and vl-soho.tgz - all X and related packages should
reside in vl-std.tgz and vl-soho.tgz so that SOHO can be KDE only and have
all packages built for it using kde as a dep.
7 - release beta std and soho at the same time
8 - set a beta test schedule of 2 weeks
9 - fix and release rc
10 - set an rc test schedule of 2 weeks and repeat 9 and 10 until stable.
11 - release final std and soho at the same time.
12 - designate a dev for each versions - std and soho - whose primary
responsibility will be security patching
13 - start working on extra packages for the repo
14 - once there is a large repo of apps available, start the next cycle at
step 1

Let me know what you all think.  Having this process more organized and
coordinated will allow us to work quicker and more efficiently giving us
more time to create the extra app repo that is needed to take VL to the nex=
t
level. That way when Robert becomes rich from VL, he will share with all of
us - lol.

Regards,
Tony