[ooo-build] ooo-build release proposal and tag OOO_BUILD_3_2_98_0 in git repositories

[Petr Mladek]

Hi,

you might have noticed the tag OOO_BUILD_3_2_98_0 in ooo-build git
repositories. It is not official. It is just playground for testing the
upcoming release.

As we started to move ooo-build diffs to from ooo-build/patches to the
related git sources, we will need:

	+ tag the other git repositories as well together with ooo-build
        + download all the tagged sources if you want to build the
          released version


My plan is the following:

	+ tag all repositories with the same tag, e.g. OOO_BUILD_3_3_0_1
	+ repack the sources during download to get better named
          tarballs, e.g. ooo-build-3.3.0.1-writer.tar.bz2

The tarball will have the structure that is usual in other opensource
projects:

       + ooo-build-3.3.0.1-writer
		- starmath
			- inc
			- prj
			- ...
		- sw
			- inc
			- prj
			- ...

You could enforce another source version using the configure switch
--with-source-version. This way you would be able to create
"non-offical" and reasonable version, e.g. 3.3.0.1.3 from the tag
DEBIAN_OOO_BUILD_3_3_0_1_3.

The right tarballs will be created automatically when calling
ooo-build/download.

Alternatively, you could use the new helper tool
"ooo-build/bin/ooo-pack-sources" to create the tarballs from the cloned
git repositories.

Also "ooo-build/bin/ooo-pack-sources" and cloned repos are the preferred
way to create tarballs for test build from non-tagged sources.

------

BTW: I though about to create piece-specific tags, e.g.
ooo-build-3.3.0.1-writer. Then you would be able to download 
the right tarball directly from cgit.

Though, I prefer the same tag for all repos because:

    + advantages:
        + easy tagging (could it be easy with some many repos; what
          about changelog?)
        + easy search through all repositories (sounds very important)
        + universal solution to support distro specific tags
    + disadvantage:
        + need renaming/repacking after download from cgit (download
          script can do this easily)
        + against the idea of releasing the pieces independently (do we
          want it?, not realistic within next few years; would need
          another development model)

-------

Any better ideas?


-- 
Best Regards,

Petr Mladek
software developer
---------------------------------------------------------------------  
SUSE LINUX, s. r. o.                        e-mail: pmladek at suse.cz
Lihovarská 1060/12                          tel: +420 284 028 952
190 00 Prague 9                             fax: +420 284 028 951
Czech Republic                              http://www.suse.cz/