Hi, On Tue, Jan 28, 2014 at 1:11 AM, Alex Parvulescu <[email protected]> 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 <[email protected]> wrote: > >> Hi, >> >> > On Mon, Jan 27, 2014 at 9:08 PM, <[email protected]> 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 >>
