Once PRs are reviewed and approved, commits pushed to github will be
built automatically when github is checked for changes (once every 8
hours).
Jobs are here, for the 4.3.x & master branch.
On Mon, Apr 11, 2016 at 5:26 AM, Max Rydahl Andersen
<manderse(a)redhat.com> wrote:
On 8 Apr 2016, at 8:34, Daniel Dekany wrote:
> Thank you very much! To be perfectly clear, I didn't come here to
> complain and force JBoss employees to do this. I'm asking if there's a
> way to change the overall process somehow. Perhaps not, but, who
> knows...
There is - we have an updatesite for freemarker site that builds every
night, so you can releases/fixes from it more or less immediately.
To get more content in, we need more content in PR's to the repos and if
someone
wants to step up to review and test PR's let us know.
As you notice if we come aware of something going stale we do react - to
avoid it going
stale repeatedly we need someone to have time and skills to push
content.
If it was something else you had in mind let me know. In any case, we
are pretty open
on what happens with freemarker tooling as long as it keeps (within
reason) being compatible with
multiple freemarker versions so it can be used in real projects that end
up having wide
range of freemarker content.
/max
>
>
> Friday, April 8, 2016, 12:00:19 AM, Alexey Kazakov wrote:
>
>> Sorry for such long delays.
>> I pushed the 4-month old PR to the master. We are currently very busy
>> preparing JBoss Tools 4.3.1 release (should happen in two weeks) but
>> then we will find some time to review the other two PRs.
>>
>> Thanks for your contributions!
>>
>> On 04/07/2016 05:39 PM, Daniel Dekany wrote:
>>> I'm a contributor at the FreeMarker project, and would like to help
>>> maintaining JBoss Tools / FreeMarker IDE
>>> (org.jboss.ide.eclipse.freemarker). The problem I'm facing is that
>>> pull requests get merged with too big delay. For example, I have a
>>> few
>>> simple pull requests waiting for 4 months now, because of the
>>> limited
>>> resources available for reviewing them (as I was told). I wonder if
>>> I
>>> can help improving this situation somehow.
>>>
>>> If the above can be addressed, then I guess I could specify the
>>> nightly build update site URL to the users, so that they aren't
>>> affected by the release cycle of JBoss Tools. After all, FreeMarker
>>> IDE is technically quite independent of it.
>>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> --
> Thanks,
> Daniel Dekany
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio