2014-12-25 10:53 GMT+01:00 Martin Landa <landa.martin@gmail.com>:
recently I entered GRASS team on Launchpad. Since I am completely new
to this system I have some questions. I found two "projects":
1) Stable [1]
[...]
2) Development [2]
I would propose change to this projects:
* stable will contain the latest release of GRASS7, now it will be 7.0.0beta4
* stable will contain daily builds of grass70-addons against latest
grass70 package
* devel will contain daily builds of grass70 (rel svn branch) and
daily builds of grass71 (trunk)
* devel will contain daily builds of grass70-addons and grass71-addons packagesw
2014-12-31 11:42 GMT+01:00 Martin Landa <landa.martin@gmail.com>:
* stable will contain the latest release of GRASS7, now it will be 7.0.0beta4
currently we have recipe to build relbr7 [1] which points to base
branch SVN [2]. To build package for beta4 I need to create a new
recipe and register a new base branch which points to svn tagged
branch [3], is it right? Any comments from our Launchpad gurus are
highly welcome:-)
2014-12-31 11:52 GMT+01:00 Martin Landa <landa.martin@gmail.com>:
currently we have recipe to build relbr7 [1] which points to base
branch SVN [2]. To build package for beta4 I need to create a new
recipe and register a new base branch which points to svn tagged
branch [3], is it right? Any comments from our Launchpad gurus are
highly welcome:-)
any idea? Currently we have 7.0 series [1] which points to
releasebranch_70 [2]. Based on that I will set up daily builds for
grass-devel. The next step is to add grass70 package to grass-stable
which will be built on request based on 7.0.0beta4, RC1, 7.0.0... Any
hints how to set it up?
2015-01-01 12:25 GMT+01:00 Martin Landa <landa.martin@gmail.com>:
grass-devel. The next step is to add grass70 package to grass-stable
which will be built on request based on 7.0.0beta4, RC1, 7.0.0... Any
hints how to set it up?
I tried to create a new branch which points 7.0.0beta4 [1], based on
that I can create a recipe. But it's not apparently a good way. Is it
possible to create recipe which points to given tarball [2]? Thanks
for clarification. Martin
2014-12-25 10:53 GMT+01:00 Martin Landa <landa.martin@gmail.com>:
recently I entered GRASS team on Launchpad. Since I am completely new to
this system I have some questions. I found two "projects":
1) Stable [1]
[...]
2) Development [2]
I would propose change to this projects:
* stable will contain the latest release of GRASS7, now it will be
7.0.0beta4 * stable will contain daily builds of grass70-addons against
latest grass70 package
Agree, with little modification of your wording:
* stable will contain the latest official release of GRASS7 staring from
7.0.0beta4
* stable will contain daily builds of of addons build on top of latest
official release of GRASS7
* devel will contain daily builds of grass70 (rel svn branch) and daily
builds of grass71 (trunk) * devel will contain daily builds of
grass70-addons and grass71-addons packagesw
- From my point of view, devel should contain daily builds of latest development
versions which now means 7.1.
On 2 January 2015 at 12:01, Ivan Mincik <ivan.mincik@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/31/2014 11:42 AM, Martin Landa wrote:
Hi,
Hi,
* stable will contain the latest release of GRASS7, now it will be
7.0.0beta4 * stable will contain daily builds of grass70-addons against
latest grass70 package
Agree, with little modification of your wording:
* stable will contain the latest official release of GRASS7 staring from
7.0.0beta4
* stable will contain daily builds of of addons build on top of latest
official release of GRASS7
+1
* devel will contain daily builds of grass70 (rel svn branch) and daily
builds of grass71 (trunk) * devel will contain daily builds of
grass70-addons and grass71-addons packagesw
- From my point of view, devel should contain daily builds of latest development
versions which now means 7.1.
I'd prefer to have also grass70 rel svn branch so people can test
easily if bug are fixed...