You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Benson Margulies <bi...@gmail.com> on 2010/10/15 16:36:24 UTC
A new release? Can I help?
Hello forrest dev:
Java 1.5 is somewhat scarce on MacOSX and recent ubuntu. Is there any
way I could help push out a release of the trunk, which (from the
email archive) seems to be 1.6-friendly?
--benson margulies
Re: A new release? Can I help?
Posted by David Crossley <cr...@apache.org>.
Benson Margulies wrote:
> Gav and David,
>
> Forgive me.
I hope that replies are coming across as constructive
and not defensive.
Over time i have tried to encourage anyone who comes
along to go the extra step.
I do need to balance between encouraging comments
and being real about the sleepy under-staffed
situation at Forrest.
In the past i put in a lot of extra volunteer time.
Now i can only assist.
> I don't know either why so many people assume that there's
> nobody home at Forrest, and so just advertise the 1.5/1.6 problem, but
> after the third or fourth I just assumed that the project was mighty
> sleepy. Thus 'residual'.
It *is* sleepy. See our past board reports.
As noted, some set of committers do attend to
queries on our mail lists. So i really have no
explanation why people don't (in general) come
here to ask or to help.
Some committers are still attentive and
have gradually worked on the holdups.
My gut feeling is that it is so close, that
one more concerted push would get it to a state
that an RM can step forward.
> Obviously, I can't be an RM, I'm not a
> committer. I'll follow David's breadcrumbs soon.
:-) "breadcrumbs" ... nice one. I admit that
as part of my OSS technique.
For Forrest i reckon that our release process would
be easier for someone who is familiar with Forrest.
As noted, it gets a bit convoluted. We ship the
current set of docs with the release. And we have
a large set of packaged supporting products.
-David
Re: A new release? Can I help?
Posted by Benson Margulies <bi...@gmail.com>.
Gav and David,
Forgive me. I don't know either why so many people assume that there's
nobody home at Forrest, and so just advertise the 1.5/1.6 problem, but
after the third or fourth I just assumed that the project was mighty
sleepy. Thus 'residual'. Obviously, I can't be an RM, I'm not a
committer. I'll follow David's breadcrumbs soon.
On Sat, Oct 16, 2010 at 9:16 PM, David Crossley <cr...@apache.org> wrote:
> Benson Margulies wrote:
>> OK, I now understand about jing.
>>
>> My motivations here are these: a bunch of foundation project use
>> forrest; everyone has to update their branding; the Java 1.6 issue
>> gums people up. Given the workaround, a release is not so urgent as I
>> expected it to be.
>
> Yesterday's addition of an FAQ, beyond what was already
> in the mail archives and tracker, will let people know
> that they can get on with their existing versions.
> I am surpised that we do not see people coming
> here to ask about that issue.
>
> We still do need to release ASAP. We know that.
>
>> Still, I'm willing to poke at some of the issues below, but it would
>> be nice to know that there are a few residual PMC members here who
>> could actually RM the release (and vote for it).
>
> The dev archives show that there are a number of
> people here. We won't know the answer to your question
> until it happens. As usual the catalyst is for someone
> to muster the energy to be RM. The most recent VOTE on
> our dev list showed that people are still aware.
>
> -David
>
Re: A new release? Can I help?
Posted by David Crossley <cr...@apache.org>.
Benson Margulies wrote:
> OK, I now understand about jing.
>
> My motivations here are these: a bunch of foundation project use
> forrest; everyone has to update their branding; the Java 1.6 issue
> gums people up. Given the workaround, a release is not so urgent as I
> expected it to be.
Yesterday's addition of an FAQ, beyond what was already
in the mail archives and tracker, will let people know
that they can get on with their existing versions.
I am surpised that we do not see people coming
here to ask about that issue.
We still do need to release ASAP. We know that.
> Still, I'm willing to poke at some of the issues below, but it would
> be nice to know that there are a few residual PMC members here who
> could actually RM the release (and vote for it).
The dev archives show that there are a number of
people here. We won't know the answer to your question
until it happens. As usual the catalyst is for someone
to muster the energy to be RM. The most recent VOTE on
our dev list showed that people are still aware.
-David
RE: A new release? Can I help?
Posted by "Gav..." <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Benson Margulies [mailto:bimargulies@gmail.com]
> Sent: Sunday, 17 October 2010 4:55 AM
> To: dev@forrest.apache.org
> Subject: Re: A new release? Can I help?
>
> OK, I now understand about jing.
>
> My motivations here are these: a bunch of foundation project use
> forrest; everyone has to update their branding; the Java 1.6 issue
> gums people up. Given the workaround, a release is not so urgent as I
> expected it to be.
>
> Still, I'm willing to poke at some of the issues below, but it would
> be nice to know that there are a few residual PMC members here who
> could actually RM the release (and vote for it).
Residual PMC members? In what way?
Not having a release for 3 years doesn’t mean the PMC has gone away.
Gav...
>
> On Fri, Oct 15, 2010 at 10:07 PM, David Crossley <cr...@apache.org>
> wrote:
> > Benson Margulies wrote:
> >> Hello forrest dev:
> >>
> >> Java 1.5 is somewhat scarce on MacOSX and recent ubuntu. Is there
> any
> >> way I could help push out a release of the trunk, ...
> >
> > Thanks so much Benson. I don't have much time
> > but will try to help.
> >
> > Some quick response notes:
> >
> > * Yes please do help.
> >
> > * There has been some discussion about what needs
> > to be finalised. Some people have made individual
> > spurts of progress. As Forrest is moving slowly, please
> > see further back in archives. Some things were partially
> > dealt with and may need follow through.
> >
> > * Review issue tracker.
> > http://forrest.apache.org/issues.html#filters
> > The main filter is "FOR-roadmap-dev".
> >
> > * Review some outstanding patches. It would be
> > a shame not to include some more contributions
> > and we need to encourage our contributors.
> >
> > The review will encourage our committers to
> > apply it. Speaking for myself i don't have enough
> > time to investigate the following suggested ones.
> >
> > Glancing through the list i reckon that FOR-1203
> > and FOR-752 are the only likely candidates.
> > The others are either in plugins, which can be
> > handled at any time after the core release,
> > or need more work. IMO we should focus elsewhere
> > at this late stage.
> >
> > * I have made some progress at classifying the
> > licenses of our various supporting products.
> > We complicate things because we bundle these
> > products with our release.
> >
> > Next task is to ensure that we meet all of
> > their conditions, e.g. perhaps pass on NOTICES.
> >
> > * We have the release process at:
> > http://forrest.apache.org/procedures/release/How_to_release.html
> >
> > * Another useful resource is "Project tasks"
> > http://forrest.apache.org/tasks.html
> >
> > * I suggest that you install the "Forrestbar"
> > http://forrest.apache.org/tools/forrestbar.html
> > It is a great benefit for directed quick search/access
> > of our project resources.
> >
> > Thanks again for anything that you can manage
> > to assist with.
> >
> > ----oOo----
> >
> >> ... which (from the
> >> email archive) seems to be 1.6-friendly?
> >
> > Please note that Forrest does not require Java 6.
> > Let us know if the following issue does not address
> > what you are seeing.
> >
> > I was very concerned when i searched the net to see
> > that people do not realise the simple workaround.
> >
> > Today i added a new FAQ:
> > http://forrest.apache.org/faq.html#oldjing
> >
> > -David
> >
Re: A new release? Can I help?
Posted by Benson Margulies <bi...@gmail.com>.
OK, I now understand about jing.
My motivations here are these: a bunch of foundation project use
forrest; everyone has to update their branding; the Java 1.6 issue
gums people up. Given the workaround, a release is not so urgent as I
expected it to be.
Still, I'm willing to poke at some of the issues below, but it would
be nice to know that there are a few residual PMC members here who
could actually RM the release (and vote for it).
On Fri, Oct 15, 2010 at 10:07 PM, David Crossley <cr...@apache.org> wrote:
> Benson Margulies wrote:
>> Hello forrest dev:
>>
>> Java 1.5 is somewhat scarce on MacOSX and recent ubuntu. Is there any
>> way I could help push out a release of the trunk, ...
>
> Thanks so much Benson. I don't have much time
> but will try to help.
>
> Some quick response notes:
>
> * Yes please do help.
>
> * There has been some discussion about what needs
> to be finalised. Some people have made individual
> spurts of progress. As Forrest is moving slowly, please
> see further back in archives. Some things were partially
> dealt with and may need follow through.
>
> * Review issue tracker.
> http://forrest.apache.org/issues.html#filters
> The main filter is "FOR-roadmap-dev".
>
> * Review some outstanding patches. It would be
> a shame not to include some more contributions
> and we need to encourage our contributors.
>
> The review will encourage our committers to
> apply it. Speaking for myself i don't have enough
> time to investigate the following suggested ones.
>
> Glancing through the list i reckon that FOR-1203
> and FOR-752 are the only likely candidates.
> The others are either in plugins, which can be
> handled at any time after the core release,
> or need more work. IMO we should focus elsewhere
> at this late stage.
>
> * I have made some progress at classifying the
> licenses of our various supporting products.
> We complicate things because we bundle these
> products with our release.
>
> Next task is to ensure that we meet all of
> their conditions, e.g. perhaps pass on NOTICES.
>
> * We have the release process at:
> http://forrest.apache.org/procedures/release/How_to_release.html
>
> * Another useful resource is "Project tasks"
> http://forrest.apache.org/tasks.html
>
> * I suggest that you install the "Forrestbar"
> http://forrest.apache.org/tools/forrestbar.html
> It is a great benefit for directed quick search/access
> of our project resources.
>
> Thanks again for anything that you can manage
> to assist with.
>
> ----oOo----
>
>> ... which (from the
>> email archive) seems to be 1.6-friendly?
>
> Please note that Forrest does not require Java 6.
> Let us know if the following issue does not address
> what you are seeing.
>
> I was very concerned when i searched the net to see
> that people do not realise the simple workaround.
>
> Today i added a new FAQ:
> http://forrest.apache.org/faq.html#oldjing
>
> -David
>
Re: A new release? Can I help?
Posted by Benson Margulies <bi...@gmail.com>.
To clarify one point:
If you unpack 0.8 and try to run it on Java 1.6, it fails. If you
build 0.9-dev, it works. There's no concept of 'requiring Java 6' in
the conversation.
On Fri, Oct 15, 2010 at 10:07 PM, David Crossley <cr...@apache.org> wrote:
> Benson Margulies wrote:
>> Hello forrest dev:
>>
>> Java 1.5 is somewhat scarce on MacOSX and recent ubuntu. Is there any
>> way I could help push out a release of the trunk, ...
>
> Thanks so much Benson. I don't have much time
> but will try to help.
>
> Some quick response notes:
>
> * Yes please do help.
>
> * There has been some discussion about what needs
> to be finalised. Some people have made individual
> spurts of progress. As Forrest is moving slowly, please
> see further back in archives. Some things were partially
> dealt with and may need follow through.
>
> * Review issue tracker.
> http://forrest.apache.org/issues.html#filters
> The main filter is "FOR-roadmap-dev".
>
> * Review some outstanding patches. It would be
> a shame not to include some more contributions
> and we need to encourage our contributors.
>
> The review will encourage our committers to
> apply it. Speaking for myself i don't have enough
> time to investigate the following suggested ones.
>
> Glancing through the list i reckon that FOR-1203
> and FOR-752 are the only likely candidates.
> The others are either in plugins, which can be
> handled at any time after the core release,
> or need more work. IMO we should focus elsewhere
> at this late stage.
>
> * I have made some progress at classifying the
> licenses of our various supporting products.
> We complicate things because we bundle these
> products with our release.
>
> Next task is to ensure that we meet all of
> their conditions, e.g. perhaps pass on NOTICES.
>
> * We have the release process at:
> http://forrest.apache.org/procedures/release/How_to_release.html
>
> * Another useful resource is "Project tasks"
> http://forrest.apache.org/tasks.html
>
> * I suggest that you install the "Forrestbar"
> http://forrest.apache.org/tools/forrestbar.html
> It is a great benefit for directed quick search/access
> of our project resources.
>
> Thanks again for anything that you can manage
> to assist with.
>
> ----oOo----
>
>> ... which (from the
>> email archive) seems to be 1.6-friendly?
>
> Please note that Forrest does not require Java 6.
> Let us know if the following issue does not address
> what you are seeing.
>
> I was very concerned when i searched the net to see
> that people do not realise the simple workaround.
>
> Today i added a new FAQ:
> http://forrest.apache.org/faq.html#oldjing
>
> -David
>
Re: A new release? Can I help?
Posted by David Crossley <cr...@apache.org>.
Benson Margulies wrote:
> Hello forrest dev:
>
> Java 1.5 is somewhat scarce on MacOSX and recent ubuntu. Is there any
> way I could help push out a release of the trunk, ...
Thanks so much Benson. I don't have much time
but will try to help.
Some quick response notes:
* Yes please do help.
* There has been some discussion about what needs
to be finalised. Some people have made individual
spurts of progress. As Forrest is moving slowly, please
see further back in archives. Some things were partially
dealt with and may need follow through.
* Review issue tracker.
http://forrest.apache.org/issues.html#filters
The main filter is "FOR-roadmap-dev".
* Review some outstanding patches. It would be
a shame not to include some more contributions
and we need to encourage our contributors.
The review will encourage our committers to
apply it. Speaking for myself i don't have enough
time to investigate the following suggested ones.
Glancing through the list i reckon that FOR-1203
and FOR-752 are the only likely candidates.
The others are either in plugins, which can be
handled at any time after the core release,
or need more work. IMO we should focus elsewhere
at this late stage.
* I have made some progress at classifying the
licenses of our various supporting products.
We complicate things because we bundle these
products with our release.
Next task is to ensure that we meet all of
their conditions, e.g. perhaps pass on NOTICES.
* We have the release process at:
http://forrest.apache.org/procedures/release/How_to_release.html
* Another useful resource is "Project tasks"
http://forrest.apache.org/tasks.html
* I suggest that you install the "Forrestbar"
http://forrest.apache.org/tools/forrestbar.html
It is a great benefit for directed quick search/access
of our project resources.
Thanks again for anything that you can manage
to assist with.
----oOo----
> ... which (from the
> email archive) seems to be 1.6-friendly?
Please note that Forrest does not require Java 6.
Let us know if the following issue does not address
what you are seeing.
I was very concerned when i searched the net to see
that people do not realise the simple workaround.
Today i added a new FAQ:
http://forrest.apache.org/faq.html#oldjing
-David