You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bval.apache.org by Albert Lee <al...@gmail.com> on 2013/04/09 15:36:22 UTC
Request to create a branch of 0.4-incubating as a maintenance release.
Hello,
My company uses a specific revision of 0.4-incubating in our product and I
would like to create a branch of this release from this particular revision
for our maintenance work. I am proposing to follow the model used by
OpenJPA:
* create a release in
svn.apache.org/repos/asf/bval/branches/0.4-incubatingthat branched off
from a particular revision in bval/ctags/0.4
* this release will be owned and maintained by the "release manager" of
this branch.
Any objection?
--
Albert Lee.
Re: Request to create a branch of 0.4-incubating as a maintenance release.
Posted by Albert Lee <al...@gmail.com>.
Since there is no objection, I'll move forward to create the 0.4.1 branch.
Thanks
Albert Lee.
On Tue, Apr 9, 2013 at 10:35 AM, Albert Lee <al...@gmail.com> wrote:
> Matt,
>
> Thanks for your quick initial thought on this matter.
>
> In OpenJPA (see http://openjpa.apache.org/release-management.html),
> interested parties are permitted to create a branch for specialization and
> managed by an assigned release manager. This allows:
>
> * all improvements in all branches transparent to the community
> * easy recreation of any branches in place, since all the repositories.
> infrastructure are readily available for build and experimentation
> * interested parties to use and extract specialized branches for open
> usage.
>
> I can understand your POV not getting the repository proliferate
> uncontrollably complex, that's the reason I would like to get agreement (or
> permission) to have the branch created. The storage space for each
> additional branch for BVal is very minimum, and "justifies" the advantages
> this approach would bring to the community. OpenJPA has used this process
> since its inception and has been working out very nicely for multiple
> parties.
>
> Thanks again for your considerations.
>
> Albert Lee.
>
>
> On Tue, Apr 9, 2013 at 9:29 AM, Matt Benson <gu...@gmail.com> wrote:
>
>> Hi, Albert. I'm not familiar with the OpenJPA community; I'd be
>> interested, in the interest of understanding the request, to know more
>> about what they do over there and in what context. I'm not sure that,
>> from
>> my POV, it makes sense for the BVal PMC to play host to a particular
>> company's fork. I wonder if it might be more appropriate for your company
>> to fork https://github.com/apache/bval on Github and revert whatever
>> commits you don't need from the 0.4 tag.
>>
>> With apologies for having a negative initial reaction,
>> Matt
>>
>>
>> On Tue, Apr 9, 2013 at 8:36 AM, Albert Lee <al...@gmail.com> wrote:
>>
>> > Hello,
>> >
>> > My company uses a specific revision of 0.4-incubating in our product
>> and I
>> > would like to create a branch of this release from this particular
>> revision
>> > for our maintenance work. I am proposing to follow the model used by
>> > OpenJPA:
>> >
>> > * create a release in
>> > svn.apache.org/repos/asf/bval/branches/0.4-incubatingthat branched off
>> > from a particular revision in bval/ctags/0.4
>> > * this release will be owned and maintained by the "release manager" of
>> > this branch.
>> >
>> > Any objection?
>> > --
>> > Albert Lee.
>> >
>>
>
>
>
> --
> Albert Lee.
>
--
Albert Lee.
Re: Request to create a branch of 0.4-incubating as a maintenance release.
Posted by Albert Lee <al...@gmail.com>.
Matt,
Thanks for your quick initial thought on this matter.
In OpenJPA (see http://openjpa.apache.org/release-management.html),
interested parties are permitted to create a branch for specialization and
managed by an assigned release manager. This allows:
* all improvements in all branches transparent to the community
* easy recreation of any branches in place, since all the repositories.
infrastructure are readily available for build and experimentation
* interested parties to use and extract specialized branches for open usage.
I can understand your POV not getting the repository proliferate
uncontrollably complex, that's the reason I would like to get agreement (or
permission) to have the branch created. The storage space for each
additional branch for BVal is very minimum, and "justifies" the advantages
this approach would bring to the community. OpenJPA has used this process
since its inception and has been working out very nicely for multiple
parties.
Thanks again for your considerations.
Albert Lee.
On Tue, Apr 9, 2013 at 9:29 AM, Matt Benson <gu...@gmail.com> wrote:
> Hi, Albert. I'm not familiar with the OpenJPA community; I'd be
> interested, in the interest of understanding the request, to know more
> about what they do over there and in what context. I'm not sure that, from
> my POV, it makes sense for the BVal PMC to play host to a particular
> company's fork. I wonder if it might be more appropriate for your company
> to fork https://github.com/apache/bval on Github and revert whatever
> commits you don't need from the 0.4 tag.
>
> With apologies for having a negative initial reaction,
> Matt
>
>
> On Tue, Apr 9, 2013 at 8:36 AM, Albert Lee <al...@gmail.com> wrote:
>
> > Hello,
> >
> > My company uses a specific revision of 0.4-incubating in our product and
> I
> > would like to create a branch of this release from this particular
> revision
> > for our maintenance work. I am proposing to follow the model used by
> > OpenJPA:
> >
> > * create a release in
> > svn.apache.org/repos/asf/bval/branches/0.4-incubatingthat branched off
> > from a particular revision in bval/ctags/0.4
> > * this release will be owned and maintained by the "release manager" of
> > this branch.
> >
> > Any objection?
> > --
> > Albert Lee.
> >
>
--
Albert Lee.
Re: Request to create a branch of 0.4-incubating as a maintenance release.
Posted by Matt Benson <gu...@gmail.com>.
Hi, Albert. I'm not familiar with the OpenJPA community; I'd be
interested, in the interest of understanding the request, to know more
about what they do over there and in what context. I'm not sure that, from
my POV, it makes sense for the BVal PMC to play host to a particular
company's fork. I wonder if it might be more appropriate for your company
to fork https://github.com/apache/bval on Github and revert whatever
commits you don't need from the 0.4 tag.
With apologies for having a negative initial reaction,
Matt
On Tue, Apr 9, 2013 at 8:36 AM, Albert Lee <al...@gmail.com> wrote:
> Hello,
>
> My company uses a specific revision of 0.4-incubating in our product and I
> would like to create a branch of this release from this particular revision
> for our maintenance work. I am proposing to follow the model used by
> OpenJPA:
>
> * create a release in
> svn.apache.org/repos/asf/bval/branches/0.4-incubatingthat branched off
> from a particular revision in bval/ctags/0.4
> * this release will be owned and maintained by the "release manager" of
> this branch.
>
> Any objection?
> --
> Albert Lee.
>