Agenda
------
0. Preliminaries, 5 mins

1. v4.4 status, issues and questions  

2. The status of Normative Types work and the status of the Normative Types standard document

3. The procedure to make changes to normative documents [1] of the EPICS V4 WG

[0]
 http://epics-pvdata.sourceforge.net/home.html#usefulinfo
[1]
 http://en.wikipedia.org/wiki/Normative#Standards_documents

Minutes:

-----------

PRESENT: AJ, MK, MS, GW

SCRIBE: GW

CHAIR: GW

********

NEW TOPIC: v4.4 status, issues and questions

********

For a java module. Assuming that antecedents have been built in the maven repository prior to this sequence.

1) make sure every feature you intend for this release is committed and pushed.
2) hg flow release start 4.0
3) hg commit
4) hg push

5) Update pom.xml with correct <version>. The version must match the tag *exactly*, eg 4.0.0

6). Build and test against antecedents: mvn test

7) hg commit and push
8) hg tag 4.0.0
9) hg push

10) Wait until JARs are actually built and deployed by the Jenkins CI server

If you want to cont. development of new features (not part of this release), then:

12) hg flow develop

13) Update pom.xml with updated version <version>++ - SNAPSHOT

14) hg commit and push

If you then  have to make a change to the release

15) hg flow release 4.0   [no “start”] and continue as above from 2.

--16) Update pom.xml with updated version <version>++ - SNAPSHOT

--17) hg commit and push

Say you’re developing pvAccessJava

it depends on pvDataJava

so, you must:

hg pull “pvDataJava release/4.0” in order to test your pvAccessJava against the release branch of pvDataJava.

MK:

2) hg flow release start 4.0
3) hg commit
4) hg push

MS:

fresh:

hg clone “pvDataJava”

hg flow release 4.0

then build pvAccessJava against the locally checked out pvDataJava.

For C++

-----------

For a C++ module. Assuming that antecedents have been built in the maven repository prior to this sequence.

1) make sure every feature you intend for this release is committed and pushed.
2) hg flow release start 4.0

3) Build and test against antecedents (check out the correct versions using hg clone -r <tag>)

    Eg to test against their release branch

    hg clone “pvDataJava”

    hg flow release 4.0

    test against
4) hg commit
5) hg push

6) hg commit and push
7) hg tag 4.0.0
8) hg push

If you want to cont. development of new features (not part of this release), then:

10) hg flow develop

AI on Marty: will create release for pvDataJava,

AI on Greg: Talk to Bob about release schedule and what can go in it.