Couple of things missing:

 - Gary Gregory joined the PMC
 - FileUpload 1.2.1 was released

Another point, perhaps not relevant to the report - although we did
one m1 release (Pool 1.4) that included OSGi metadata - I doubt I will
do that manually again, so probably releases will only include OSGi
metadata if we use m2 as the primary build tool for releases. Do we
want to make using m2 a commons-wide policy? All but two components
(jelly and attributes) have m2 builds, so IMO it would be a good idea.

Niall

On Wed, Mar 12, 2008 at 10:39 AM, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> Anything I missed or got wrong? Maybe I missed new PMC members as
>  usual? :-)
>
>  Henry, did I cover the Incubator idea correctly? Feel free to change
>  directly in
>
>   https://svn.apache.org/repos/private/pmc/commons/reports/board
>
>  ...or let me know.
>
>  cheers
>
>  --
>  Apache Commons Board Report, March 2008
>
>  General
>  =======
>
>    o Activity
>
>      The past few months have been quite busy. A couple of releases
>  (see below)
>      have gone out. Based on http://markmail.org/ user activity is
>  slowly
>      declining while activity on the development list has significantly
>      increased at the beginning of the year. It's slowly declining
>  again.
>
>      Question of dormancy have been raised for 'commons vfs' and
>  'commons
>      launcher'.
>
>    o Re-release of old source distributions
>
>      This has been brought to the board's attention before. For the
>  users
>      convenience we would like to re-package old source releases and
>  provide
>      them also as source jars. This of course affects releases that
>  have been
>      made under ASL 1.1. While new releases have to be ASL 2.0 the
>  current
>      opinion is that (as long as nothing is changed during the
>  process) this
>      "re-packaging" does not classify as a new release. So we can
>  still provide
>      the new artifact under ASL 1.1. Basically it would have to
>  adhere to the
>      rules when the orignal release has been made.
>
>      No action has been taking yet. I would be great to get the board's
>      agreement on the PMC's notion.
>
>    o Commons Sandbox Incubator
>
>      While the Commons Sandbox works quite straight forward for ASF
>  internal
>      use. The question is what to do with external component level code
>      donations that may or may not been already covered by CLA.
>  Building a
>      community around a single component inside the normal Incubator
>  might
>      be tough. The idea has been brought up to work with Labs or the
>  Incubator
>      to find a solution to this.
>
>    o Removal of Cobertura reports (as the resulting reports may GPL)
>
>      Cobertura is a code coverage plugin for maven. It's been used
>  through the
>      ASF to generate reports that are part of the website. As at
>  least parts
>      of the generated site is covered by the GPL we decided not to
>  use it
>      anymore. Otherwise we cannot ship the website for a release.
>
>    o Support for OSGi
>
>      New Commons releases will now include the metadata that is
>  required to be
>      used inside OSGi out of the box.
>
>    o We got two new components into the Commons sandbox
>
>      - monitoring
>
>        http://wiki.apache.org/commons/Monitoring
>
>      - commons build plugin
>
>        Which got promoted to proper pretty much straight away for the
>        infrastructure and build improvements (see below)
>
>        http://mail-archives.apache.org/mod_mbox/commons-dev/
>  200802.mbox/%
>  [EMAIL PROTECTED]
>
>
>
>  Releases
>  ========
>
>    o Released
>      - commons SCXML 0.7              http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200712.mbox/%
>  [EMAIL PROTECTED]
>      - commons pool 1.4               http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200801.mbox/%
>  [EMAIL PROTECTED]
>      - commons sandbox parent POM 3   http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200801.mbox/%
>  [EMAIL PROTECTED]
>      - commons IO 1.4                 http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200801.mbox/%
>  [EMAIL PROTECTED]
>      - commons fileupload 1.2.1       http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200802.mbox/%
>  [EMAIL PROTECTED]
>      - commons math 1.2               http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200802.mbox/%
>  [EMAIL PROTECTED]
>      - commons build plugin 1.0       http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200802.mbox/%
>  [EMAIL PROTECTED]
>      - commons proxy 1.0              http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200802.mbox/%
>  [EMAIL PROTECTED]
>      - commons parent POM 6           http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200801.mbox/%
>  [EMAIL PROTECTED]
>      - commons parent POM 7           http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200801.mbox/%
>  [EMAIL PROTECTED]
>      - commons parent POM 8           http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200803.mbox/%
>  [EMAIL PROTECTED]
>      - commons sandbox parent POM 4   http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200803.mbox/%
>  [EMAIL PROTECTED]
>      - commons parent POM 9           http://mail-archives.apache.org/
>  mod_mbox/commons-dev/200803.mbox/%
>  [EMAIL PROTECTED]
>
>  Infrastructure
>  ==============
>
>    o The maven based release process has been discussed and improved.
>    o For some components missing/broken redirects from jakarta have
>  been fixed.
>    o Old bugzilla entries have been removed and we are 100% jira now.
>  We hope
>      to get redirects in place so people will not hit broken links
>  but get to
>      correct jira issue instead.
>
>      http://mail-archives.apache.org/mod_mbox/commons-dev/200803.mbox/
>  [EMAIL PROTECTED]
>
>  Community
>  =========
>
>    o No new committers
>    o No new PMC members
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to