[Opendnssec-develop] How to handle trunk until 1.0.0?

[Rickard Bellgrim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> I think that anything that can't be fixed by some text in the
> KNOWN_ISSUES
> file means that we need an RC4.
>
> The image I had in my mind was that when 1.0.0 is released we branch;
> then
> bug fixes go into both branches and new features go into trunk only.
> Then,
> maybe when the KNOWN_ISSUES file is empty, we can release 1.0.1...
> Branching now just means that there is some merging to be done sooner
> (if
> RC3 doesn't become 1.0).

So what I am hearing is the we are leaning toward to branch when 1.0.0 is released and for now only write text to KNOWN_ISSUES. If the problem is major, then we need to do a RC4 (and other commits are then allowed before we do RC4).

// Rickard

-----BEGIN PGP SIGNATURE-----
Version: 9.8.3 (Build 4028)
Charset: utf-8

wsBVAwUBS17B9+CjgaNTdVjaAQgIEAf/XHaJh67SUH9OELY7cBUfHYPgjplyu3qf
yEeNrfDIbFLSsckQZETvl+LCjM6yMY/BroZMF0Mazr8hLgCTSiSWYIqSO5e+GeMt
ZgsVhVO4DmdV2qOL5zXAq6gVLkYO7s8WocJidRasA+S2lhYSUc1BamojMeNod3P7
VUJDfXa+mB+XDLB0rlQZwt0llVoiDLbhFGrjjacmXqgMkPDk2ZLCqymPeG4JnF2K
ld8z1FpCh8WqRgrhMlMOv8H3iVUGwv0wHpmIdQxXRZglXsawehy3NtifwTTr1gZU
5/PPfK6JK9Ws3UFmIlGzIk9h+1VnnP1CW/kYLuEw2E0K4nhnqviJcQ==
=SFub
-----END PGP SIGNATURE-----


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20100126/e40681ea/attachment.htm>