incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "April2012" by AlexHarui
Date Thu, 05 Apr 2012 22:34:22 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "April2012" page has been changed by AlexHarui:
http://wiki.apache.org/incubator/April2012?action=diff&rev1=50&rev2=51

  Are there any recommendations for how incubation could run more smoothly
  for you?
  
-   Our mentors are great. However,  Apache internals are starting to 
-   become an problem.  We submitted the software grant and code on Friday
-   PM, but the secretary was unable to record the software grant before
-   the weekend.  That meant that Infra couldn't import the code since they
-   can only do that on weekends, and that delayed the project by a whole
-   week.  Having distributed separate SVN repositories would make weeknight
-   imports possible and maybe not tax a single database as much.  Large
-   projects like Flex have tons of files.
+   Our mentors are great. We are wondering if Apache has considered giving
+   large projects like Flex their own SVN and JIRA servers. Recently, we pushed
+   really hard to get a software grant signed (An Adobe VP even came in
+   to sign it while he was taking time off to move to a new house) in order to try to
+   make the weekend deadline for getting code imported into SVN.  We are in
+   a hurry because we have seen signs we are losing momentum (mailing list
+   traffic is much lower) and a key Flex conference is coming up on April 15.
+   Being able to announce that new code was in SVN would be a good boost and
+   good timing. 
  
+   We submitted a software grant and code on Friday afternoon, but were 
+   too late to have the secretary record the software grant and that meant 
+   that Infra couldn't import the code since they only do that on weekends, 
+   and so we are now waiting for the next weekend.  Having our own separate 
+   SVN repository would make weeknight imports possible and maybe not tax 
+   a single database as much.  Large projects like Flex have tons of files.
+ 
-   The same holds true for the bug database as well.  We have been waiting
+   The same holds true for the bug database as well.  We submitted the
-   for the bug database since Feb 1.  A gating concern is that our import
-   of 30000 bugs might take down the main JIRA instance.  Having distributed
-   JIRA instances would scale better.
+   JIRA import file on Feb 1.  Infra has been unable to get the import to
+   succeed (it worked on a test instance on my computer) and has had to file
+   a bug with Atlassian (JIRA's maker).  We asked about using the SOAP
+   interface to import bugs but Infra is concerned that some problem in
+   that process would screw up JIRA for everyone and/or cause performance
+   issues.  Having our own JIRA instance would allow us to try alternate 
+   means of getting around the JIRA issue.  A SOAP import utility exists and 
+   was used to successfully import all 30,000 issues into a test instance
+   but there is risk of having some other issue show up when we add that many
+   issues to an existing database.
  
  Signed off by mentor: bdelacretaz (who doesn't fully agree with the "Apache internals are
starting to become a problem" part, will discuss on flex-dev)
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message