[CREATE] Release Timetable

Jon Phillips jon at rejon.org
Thu Oct 13 15:11:32 PDT 2005


On Thu, 2005-10-13 at 23:21 +0200, Craig Bradney wrote:
> On Thursday 13 October 2005 22:52, you wrote:
> > On Wed, 2005-10-12 at 01:37 +0200, Craig Bradney wrote:
> > > Is there a timeframe for the first release of a package?
> >
> > I just put the roadmap up on the site's wiki so that we could do a more
> > regular press release of the status of the project (since we are not
> > really releasing any source). However, maybe we should release versions
> > of the specs we define as a package. That would be a novel idea, right?
> >
> > http://create.freedesktop.org/wiki/
> >
> > > I've just built Krita 1.4.2 and I'd like those colour palettes( erm,
> > > sets, swatches.. ugh).. and either we copy them over to Scribus 1.3.2cvs
> > > at some point, or will there be a release of a compiled set of
> > > palettes/brushes etc in the near future?
> > 
> > Right, lets do this for the 0.01 release. Or, should we use this
> > numbering scheme: 0.1.0. I think I would like to try this scheme as we
> > can climb versions faster.
> 
> 0.1.0 for sure. Despite a lot of people being aware of the version number 
> doesnt matter, the syndrome of anything not actually reaching a 1.0 release 
> exists.
> 
> > > What support do you need in terms of packaging?
> >
> > I guess we need to invent a good way (or even better learn a better
> > strategy for packaging our content).
> >
> > You know, the more I think about it, we should put out a package with
> > all of our content with a Makefile to install to the standard location
> > we talked about:
> >
> > /usr/share/XXXXX (media ;)
> >
> > That really makes sense...
> >
> > What do you all think?
> 
> Scons? Those who know python might jump into this quickly. It looks fairly 
> simple to someone who doesnt know much python. Then again, a simple Makefile 
> isnt too bad either, as long as you avoid autotools. :)

Yeah, does anyone want to build a Makefile to pull together our specs
(please beat me to it). I don't see any reason for using autotools, as
we are not really building cross-platform code, bur rather shared media
and standards.

Maybe we should have:

/usr/share/XXXX/standards or

/usr/share/XXXX/specs or

/usr/share/XXXX/docs

This would be the place for us to ship our specs. along with the other
shared content. Thoughts?

Do we even have anything to put in our repository? We currently have CVS
setup, but I filed a bug just now to get SVN setup:

https://bugs.freedesktop.org/show_bug.cgi?id=4775


<brainstorm>

What I think is ideal is this. Specs written in the wiki and then we run
a command to pull them into a readable format for release. And then, any
shared content is contained in our SVN repository.

We need to talk about what content that would be thought.

</brainstorm>

-- 
Jon Phillips

San Francisco, CA
USA PH 510.499.0894
jon at rejon.org
http://www.rejon.org

MSN, AIM, Yahoo Chat: kidproto
Jabber Chat: rejon at gristle.org
IRC: rejon at irc.freenode.net

Inkscape (http://inkscape.org)
Open Clip Art Library (www.openclipart.org)



More information about the CREATE mailing list