You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Josh Thompson <jo...@ncsu.edu> on 2012/07/23 17:23:26 UTC
branch for bug fix release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd like to branch from the 2.3 release to prepare for a bug fix release,
allowing for 2.4 features to be checked in to trunk. It would make cutting
2.3.1 much easier because we wouldn't need to worry about pulling parts out or
testing that new (smallish) features are stable enough to be in a release.
However, this requires us to apply any bug fixes we make to trunk and to the
branch. Are others okay with having a branch? I'd suggest that anything that
is actually a bug be filed in JIRA as such, and that those are the only things
we'd check in to the branch. We wouldn't need to be completely strict on
this. If there was a small feature that would be really helpful to have that
can be tested well enough, that could be added too if people want it.
Thoughts?
Josh
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAlANbG4ACgkQV/LQcNdtPQNhggCeKWXI52pMnU0z/68BlYjHY1/n
IT4An0b14Eo6aAWIXi8XiHFGV6SBQ+Ah
=s3Ns
-----END PGP SIGNATURE-----
Re: branch for bug fix release
Posted by Aaron Peeler <fa...@ncsu.edu>.
Sounds good.
-A
On Mon, Jul 23, 2012 at 12:04 PM, Mark Gardner <mk...@vt.edu> wrote:
> I like the idea.
>
> Mark
>
> On Mon, Jul 23, 2012 at 11:23 AM, Josh Thompson <jo...@ncsu.edu> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I'd like to branch from the 2.3 release to prepare for a bug fix release,
>> allowing for 2.4 features to be checked in to trunk. It would make cutting
>> 2.3.1 much easier because we wouldn't need to worry about pulling parts out or
>> testing that new (smallish) features are stable enough to be in a release.
>> However, this requires us to apply any bug fixes we make to trunk and to the
>> branch. Are others okay with having a branch? I'd suggest that anything that
>> is actually a bug be filed in JIRA as such, and that those are the only things
>> we'd check in to the branch. We wouldn't need to be completely strict on
>> this. If there was a small feature that would be really helpful to have that
>> can be tested well enough, that could be added too if people want it.
>>
>> Thoughts?
>>
>> Josh
>> - --
>> - -------------------------------
>> Josh Thompson
>> VCL Developer
>> North Carolina State University
>>
>> my GPG/PGP key can be found at pgp.mit.edu
>>
>> All electronic mail messages in connection with State business which
>> are sent to or received by this account are subject to the NC Public
>> Records Law and may be disclosed to third parties.
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.17 (GNU/Linux)
>>
>> iEYEARECAAYFAlANbG4ACgkQV/LQcNdtPQNhggCeKWXI52pMnU0z/68BlYjHY1/n
>> IT4An0b14Eo6aAWIXi8XiHFGV6SBQ+Ah
>> =s3Ns
>> -----END PGP SIGNATURE-----
>>
>
>
>
> --
> Mark Gardner
> --
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
Re: branch for bug fix release
Posted by Mark Gardner <mk...@vt.edu>.
I like the idea.
Mark
On Mon, Jul 23, 2012 at 11:23 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'd like to branch from the 2.3 release to prepare for a bug fix release,
> allowing for 2.4 features to be checked in to trunk. It would make cutting
> 2.3.1 much easier because we wouldn't need to worry about pulling parts out or
> testing that new (smallish) features are stable enough to be in a release.
> However, this requires us to apply any bug fixes we make to trunk and to the
> branch. Are others okay with having a branch? I'd suggest that anything that
> is actually a bug be filed in JIRA as such, and that those are the only things
> we'd check in to the branch. We wouldn't need to be completely strict on
> this. If there was a small feature that would be really helpful to have that
> can be tested well enough, that could be added too if people want it.
>
> Thoughts?
>
> Josh
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
>
> iEYEARECAAYFAlANbG4ACgkQV/LQcNdtPQNhggCeKWXI52pMnU0z/68BlYjHY1/n
> IT4An0b14Eo6aAWIXi8XiHFGV6SBQ+Ah
> =s3Ns
> -----END PGP SIGNATURE-----
>
--
Mark Gardner
--
Re: branch for bug fix release
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I created the following branch:
https://svn.apache.org/repos/asf/vcl/branches/vcl-2.3-bugfixes
for maintaining any bug fixes in preparation for a 2.3.1 release in a few
months. The only way I know to manage both trunk and a branch is to manually
apply any bug related changes to both places.
Josh
On Monday, July 23, 2012 11:23:26 AM I wrote:
> I'd like to branch from the 2.3 release to prepare for a bug fix release,
> allowing for 2.4 features to be checked in to trunk. It would make cutting
> 2.3.1 much easier because we wouldn't need to worry about pulling parts
> out or testing that new (smallish) features are stable enough to be in a
> release. However, this requires us to apply any bug fixes we make to trunk
> and to the branch. Are others okay with having a branch? I'd suggest that
> anything that is actually a bug be filed in JIRA as such, and that those
> are the only things we'd check in to the branch. We wouldn't need to be
> completely strict on this. If there was a small feature that would be
> really helpful to have that can be tested well enough, that could be added
> too if people want it.
> Thoughts?
>
> Josh
- --
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAlAOy3UACgkQV/LQcNdtPQNagwCePbyzNkIrA6yTDnD+IUr2lTza
ezcAn0J/clHka6vMI+Ke5IHBlUm9jNXp
=Jdm8
-----END PGP SIGNATURE-----
Re: branch for bug fix release
Posted by Kevan Miller <ke...@gmail.com>.
On Jul 23, 2012, at 11:23 AM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'd like to branch from the 2.3 release to prepare for a bug fix release,
> allowing for 2.4 features to be checked in to trunk. It would make cutting
> 2.3.1 much easier because we wouldn't need to worry about pulling parts out or
> testing that new (smallish) features are stable enough to be in a release.
> However, this requires us to apply any bug fixes we make to trunk and to the
> branch. Are others okay with having a branch? I'd suggest that anything that
> is actually a bug be filed in JIRA as such, and that those are the only things
> we'd check in to the branch. We wouldn't need to be completely strict on
> this. If there was a small feature that would be really helpful to have that
> can be tested well enough, that could be added too if people want it.
>
> Thoughts?
Sounds reasonable to me.
--kevan