You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2014/01/28 04:43:54 UTC
Re: svn commit: r1561925 - /jackrabbit/oak/tags/jackrabbit-oak-core-0.15.2/
Hi,
On Mon, Jan 27, 2014 at 9:08 PM, <tr...@apache.org> wrote:
> creating tag for oak-core 0.15.2 with modified manifest entries
Are we releasing 0.15.2?
BR,
Jukka Zitting
Re: svn commit: r1561925 - /jackrabbit/oak/tags/jackrabbit-oak-core-0.15.2/
Posted by Tobias Bocanegra <tr...@apache.org>.
On Tue, Jan 28, 2014 at 11:32 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Tue, Jan 28, 2014 at 2:20 PM, Tobias Bocanegra <tr...@apache.org> wrote:
>> as i mentioned before. it's not a branch nor a tag of an official
>> release, but merely a place to record that I intended to use a 0.15.2
>> version of oak-core.
>
> I think it would be clearer if you moved it from tags/ to branches/,
> as all the other tags correspond to official releases.
right. I'll do that. thanks.
regards, toby
Re: svn commit: r1561925 - /jackrabbit/oak/tags/jackrabbit-oak-core-0.15.2/
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, Jan 28, 2014 at 2:20 PM, Tobias Bocanegra <tr...@apache.org> wrote:
> as i mentioned before. it's not a branch nor a tag of an official
> release, but merely a place to record that I intended to use a 0.15.2
> version of oak-core.
I think it would be clearer if you moved it from tags/ to branches/,
as all the other tags correspond to official releases.
BR,
Jukka Zitting
Re: svn commit: r1561925 - /jackrabbit/oak/tags/jackrabbit-oak-core-0.15.2/
Posted by Tobias Bocanegra <tr...@apache.org>.
Hi,
On Tue, Jan 28, 2014 at 1:11 AM, Alex Parvulescu
<al...@gmail.com> wrote:
> Hi,
>
> Shouldn't these changes go into trunk directly? I only see then on the new
> branch.
no, they are in trunk. I added them here:
https://svn.apache.org/viewvc?view=revision&revision=1560563
> Second, I did not see any kind of discussion/announcement related to this
> new branch. We create releases every 2 weeks, couldn't this have waited a
> few days?
as i mentioned before. it's not a branch nor a tag of an official
release, but merely a place to record that I intended to use a 0.15.2
version of oak-core. I could have done it in my private fork, but
didn't. As soon as 0.16 is released, I delete the tag again.
regards, toby
> best,
> alex
>
>
>
>
> On Tue, Jan 28, 2014 at 6:26 AM, Tobias Bocanegra <tr...@apache.org> wrote:
>
>> Hi,
>>
>> > On Mon, Jan 27, 2014 at 9:08 PM, <tr...@apache.org> wrote:
>> >> creating tag for oak-core 0.15.2 with modified manifest entries
>> >
>> > Are we releasing 0.15.2?
>>
>> No. I just needed an updated oak-core jar that contained a slightly
>> different MANIFEST.MF for exported packages that I forgot to include
>> in the official 0.15 release. And I thought it's best if I record this
>> change as non-released oak tag. I don't think we ever need to release
>> 0.15.2++ officially. but if we do, we need to create a 0.15 branch
>> anyways and then release 0.15.4.
>>
>> The alternative would have been to create a release my own fork...but
>> this would have not been as transparent, in case we really need to
>> release 0.15.x.
>>
>> regards, toby
>>
>> >
>> > BR,
>> >
>> > Jukka Zitting
>>
Re: svn commit: r1561925 - /jackrabbit/oak/tags/jackrabbit-oak-core-0.15.2/
Posted by Alex Parvulescu <al...@gmail.com>.
Hi,
Shouldn't these changes go into trunk directly? I only see then on the new
branch.
Second, I did not see any kind of discussion/announcement related to this
new branch. We create releases every 2 weeks, couldn't this have waited a
few days?
best,
alex
On Tue, Jan 28, 2014 at 6:26 AM, Tobias Bocanegra <tr...@apache.org> wrote:
> Hi,
>
> > On Mon, Jan 27, 2014 at 9:08 PM, <tr...@apache.org> wrote:
> >> creating tag for oak-core 0.15.2 with modified manifest entries
> >
> > Are we releasing 0.15.2?
>
> No. I just needed an updated oak-core jar that contained a slightly
> different MANIFEST.MF for exported packages that I forgot to include
> in the official 0.15 release. And I thought it's best if I record this
> change as non-released oak tag. I don't think we ever need to release
> 0.15.2++ officially. but if we do, we need to create a 0.15 branch
> anyways and then release 0.15.4.
>
> The alternative would have been to create a release my own fork...but
> this would have not been as transparent, in case we really need to
> release 0.15.x.
>
> regards, toby
>
> >
> > BR,
> >
> > Jukka Zitting
>
Re: svn commit: r1561925 - /jackrabbit/oak/tags/jackrabbit-oak-core-0.15.2/
Posted by Tobias Bocanegra <tr...@apache.org>.
Hi,
> On Mon, Jan 27, 2014 at 9:08 PM, <tr...@apache.org> wrote:
>> creating tag for oak-core 0.15.2 with modified manifest entries
>
> Are we releasing 0.15.2?
No. I just needed an updated oak-core jar that contained a slightly
different MANIFEST.MF for exported packages that I forgot to include
in the official 0.15 release. And I thought it's best if I record this
change as non-released oak tag. I don't think we ever need to release
0.15.2++ officially. but if we do, we need to create a 0.15 branch
anyways and then release 0.15.4.
The alternative would have been to create a release my own fork...but
this would have not been as transparent, in case we really need to
release 0.15.x.
regards, toby
>
> BR,
>
> Jukka Zitting